Connection drops

Thanks for the prompt response!

I2C与此问题无关，因为到目前为止，我甚至不会向模块发出任何I2C命令。此外，它没有连接到它。我使用的唯一模块引脚是P0_5和P0_6，将其连接到外部USB-UART转换器。

I use Codeless SDK 6.380.10.4 with a free version of Keil v5.27.1.0 and commented out some AT commands in file user_at_command.h (see attached) to bring the codeless_stand_alone image under 32K limit. Following your advise I ran it in debug under Segger J-Link debugger. Right after starting the code I give to it AT+SLEEP=0 command, the module responded with OK and +AWAKE on the next line. Then I use Cypress CySmart tool along with their dongle as a central device to connect to the TINY module. Upon establishing the connection the module responded with +CONNECTED (in TeraTerm) and I can explore its services and attributes in CySmart used as BLE scanner tool. At this point everything works fine as expected - I can see the module's characteristics outlined in the manuals. Then I leave the module idling in the connection mode, that is issue no commands from TeraTerm and also no command over Bluetooth from CySmart. The connection is dropped after ca. 3 min as I described before. The debugger does not show me anyhing suspicious, definitely no NMI, actually it does not show anything, just runs the module code. The TeraTerm reports +READY and CySmart reports connection drop.

If you unaware with CySmart, I did the same experiment by establishing a Bluetooth connection with a pair of 531 TINY modules. One of them runs pre-compiled image (does not matter which one), the other modules runs my compiled image. The same connection drop happens after 3 min. However, if both modules run pre-compiled datapump or standalone images (by pre-compiled I mean the images provided in SmartBond Flash Programmer) tool, then no connection drop is experienced. But once one of the moduled is loaded with pre-compiled standlone set two, the connection drop happens. So, something is wrong with pre-compiled set-two image and with the SDK source code.

I wrote about I2C only because I need that option. So far I even did not try how it works, so the problem is definitely not related to I2C.

Here you go. The attached archive has a photo of my hardware (just DA14531 module and CP2104 USB-UART) and the BLE events Log. The Log shows that the 531 issued connection timeout 3 minutes after connection establishment (the last 3 records). I do not use SLEEP mode.

是的，掉落后connection the DA device starts advertizing again. You are right: the Link supervision is expired because DA14531 stopped responding to connection events.

I created a special app by using Silicon Labs Simplicity Studio and their Thunderboard Sense 2 board as Central that just connects to DA14531 and does nothing after that while keeping the connection active. In the attached archive there are two images provided by Simplicity Studio Network Analyzer. On those images the device 90:FD:9F:7B:86:16 is my Central and DA:E4:D9:A6:F6:E9 is DA14531. On image named Connection_parameters you can see that DA14531 requested to set Connection latency 5 and Supervision Timeout 1250ms, which were accepted by the client (see Events Detail window). Then on image Log2 you see that DA14531 works according to the Connection Latency by not responding to 5 consequtive connection intervals in series. But after 138sec in this case it was a longer series of not responded packets which caused Superivision timeout at Central. I also see this reason (Error 0x208) on Tera-Term output from my central device on the 3rd image.

从这些日志,它遵循that after some time (2-3min) DA14531 stops responding to connection events for no reason. So, Dialog - why don't you just fix your software. Such behavior is definitely a bug. You can easily convince yourself in that by compiling and loading your provided source code into two modules or dev boards.

好,对话框,我决定听从你的建议添加ing several break points in user_on_disconnect() function in file user_codeless.c. It turns out that your provided code does not go into this function after connection is dropped. Further investigation showed that the module resets itself after dropping a connection and if one adds a breakpoint in main(), the code stops there. So, I believe you need to create a ticket for your software development group. If you want me to do it, please give me instructions.

我再次在调试器中运行它，附加了屏幕截图。代码不会卡在任何地方，它只重置模块，主（）函数开始续。您将在屏幕截图上看到它，显示调试器在删除连接后停止的位置。因此，模块已准备好建立一个新的，而且如果我继续运行它。但是在〜3分钟后，新的连接也会掉落。同样，我没有在建立连接后与模块通信 - 只是让它怠速。它看起来像看门狗行为一样。

我不使用任何（外部）闪光灯，只需连接到CP2104 USB转换器的裸模块，请参阅附图，并且不确定设备如何在内部启动。我刚刚编译了无附加的软件（V6.380.10.4）图像，用于无附加_531_SET_TWO_STANTalone，无需任何更改，并通过SWD接口将其加载到我的两个模块中。因此，它根据软件中的算法靴子。并且它在每个模块上都适用 - 在不活动3分钟后下降连接。

The same connection drop behavior is observed by using SmartConsole app on Android (Samsung Galaxy S8) as client. Any ideas what else to check?

稍后添加(IMPORTANT):我刚刚注意到，如果我向在调试器下运行的模块发出ATI命令，则响应是CodeLess DA14531 v_6.380.10.4这与我使用的SDK版本匹配。但是，如果我现在用调试器断开连接重启模块，则对ATI命令的响应变为CodeLess DA14531 v_6.380.9.10(??!!!) Maybe this is the reason for the misbehavior?

好的，这几天我了解到了if one programs the module from within Keil (in degug mode) and externally with Dialog SmartBond Flash programmer, then the results are different. Namely, after flashing my compiled code with the Flash programmer it shows the right firmware image versionDA14531 v_6.380.10.4no matter how you boot it (I mean during the debug session in Keil and also with JLink debugger disconnected). So, the mismatch between the firmware images outlined in the稍后添加section of my post above is resolved. However, the module still drops the connection after 3 minutes. Am I the only one who experiences that?

对话团队：如果连接没有放弃你，请你能给我发六角映像吗？codeless_531_set_two_standalone.hex这对你有钱吗？

亲爱的对话团队！我已经提供了由不同捕获软件和硬件收集的两个BLE捕获。其中一个由赛普拉斯综合组织和他们的加密狗CY577和另一个由Silicon Labs网络分析仪收集。附加是北欧半导体BLE加密狗PCA10031收集的另一个更详细的捕获，以及它们与Wireshark（V3.2.5）串联工作的嗅探器3.0软件。附加的捕获涉及两个设备（我的Galaxy S8手机运行SmartConsole和DA14531模块，带Mac 48：23：35：00：07：AA），可以使用Wireshark打开。在这些情况下，我在建立它后留下了连接空闲。这些是我的所有BLE嗅探工具。

我有replicated the connection drop issue on another another Galaxy S8 phone of my wife, on my older Galaxy S5 phone, and with at least 3 other non-phone BLE devices that I use as a master. DA14531 module just stopps responding on Master connection events and resets itself (I am not sure what comes first, though). Again, I experience this only if I load codeless_531_standalone_set_two image into the module. Connection with other two available pre-compiled images (codeless_531_datadump and codeless_531_standalone) seems working fine, i.e. without connection drops after 3 minutes, unless I compile them myself from the provided source. In the latter case connection drops appear no matter which image I compile.

我使用的预编译图像是由对话框智能闪存程序员提供的图像。我问你上面给我发给我用于测试的图像。请做到。此外，请在您的硬件上尝试附加的十六进制。

谢谢你。我期待着解决的问题。

Thank you, Dialog Team. This issue is resolved. Waiting for resolving the I2C issues...