我最近收到了来自 Avnet 的 Microchip/Roving Networks RN42-APL 开发套件,我能够让示例 iOS 应用程序运行并进行环回测试,一切都很好(BT 连接、验证、知道应用程序已打开)。
然而,当我将此板放置在实际电路中时,数据流向 RX-In 引脚时,RN42 甚至无法验证!
有人看过这个 MFI 芯片的功能示例吗?整个“它只是工作”并不是真的响起。在这个芯片可以发送和接收数据之前,我需要做些什么吗?
我最近收到了来自 Avnet 的 Microchip/Roving Networks RN42-APL 开发套件,我能够让示例 iOS 应用程序运行并进行环回测试,一切都很好(BT 连接、验证、知道应用程序已打开)。
然而,当我将此板放置在实际电路中时,数据流向 RX-In 引脚时,RN42 甚至无法验证!
有人看过这个 MFI 芯片的功能示例吗?整个“它只是工作”并不是真的响起。在这个芯片可以发送和接收数据之前,我需要做些什么吗?
what exactly do you mean that the RN-42-APL BT module doesn't authenticate? I used RN-42-APL + MFi 2.0c chip for iOS authentication and it works well. However the newest firmware 5.43 has still some bug related to authentication with Android system. Previously I used BT module with firmware 5.36. Engineer from Microchip told me, that previous firmware had some bugs related to authentication which requires PIN code. The newest firmware has been improved, but I found another one bug during my tests.
MFi chip must be connected with 2-wires to BT module. This chip uses I2C data transfer. I designed and constructed real device which was based on these components. Finally, this module works well with iOS, authentication mode you can change with SA,x command. Please read the manual. There are 4 options: 0, 1, 2 and 4.
So I figured out the issue (I think). It was unrelated to the firmware, but it seems that the device wouldn't authenticate if there was traffic on the UART lines before authentication had happened.
I don't know whether where this limitation comes from, nor do I really care, but if anyone runs into this, I would try shutting off UART traffic until authentication.