Connection drops

谢谢你的快速回复！

I2C has nothing to do with the issue, since so far I even do not issue any I2C command to the module. Also, it has no slave connected to it. The only module pins I use are P0_5 and P0_6 to connect it to external USB-UART converter.

我使用无附带版SDK 6.380.10.4，使用免费版本的Keil v5.27.1.0，并在File User_at_Command.h中的命令中注释了一些命令（见附加），以使Codeless_Stand_Alone映像带到32K限制下。在您的建议之后，我在Segger J-Link调试器下调试中运行它。在启动代码后，我给它at + sleep = 0命令，模块响应OK和+唤醒下一行。然后我使用赛普拉斯综合工具以及他们的加密狗作为中央设备连接到微小模块。建立连接后，模块用+连接（在Teraterm中）响应，我可以在Cysmart中探索其使用用作BLE扫描仪工具的服务和属性。此时一切正常正常工作，我可以看到手册中概述的模块的特性。然后我在连接模式下留下模块空转，这是从Teraterm发出的命令，也没有从Cysmart上的蓝牙的命令。CA之后，连接被删除。我以前描述的3分钟。调试器不会向我展示Anyhing可疑，绝对没有NMI，实际上它没有显示任何内容，只需运行模块代码。 The TeraTerm reports +READY and CySmart reports connection drop.

如果您用Cysmart没有意识到，我通过建立一个与一对531微小模块建立蓝牙连接来执行相同的实验。其中一个运行预编译的图像（哪一个无关紧要），其他模块运行我的编译图像。3分钟后发生相同的连接下降。但是，如果两个模块都运行预编译的DataPump或独立图像（通过预编译的我意味着在SmartBond Flash程序员中提供的图像）工具，则没有经历任何连接下降。但是，一旦将其中一个调制装载了预先编译的独立安装两个，就会发生连接下降。因此，预编译的Set-Two Image和SDK源代码有问题。

我只写了关于I2C的，因为我需要这个选项。到目前为止，我甚至没有尝试如何工作，因此问题绝对与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.

Yes, after dropping the 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.

从这些日志中，它遵循，在某个时间（2-3min）da14531后，停止响应连接事件无缘无故。所以，对话框 - 你为什么不修复你的软件。这种行为绝对是一个错误。通过编译和加载所提供的源代码，您可以轻松地说服自己分为两个模块或DEV板。

好,对话框,我决定听从你的建议添加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.

I ran it in a debugger again, the screenshot is attached. The code does not stuck anywhere, it just resets the module and the main() function starts over. You will see it on the screenshot which shows where the debugger stopped after dropping the connection. So, the module is ready to establish a new one, and this works if I keep running it. But the new connection is also dropped after ~3 minutes. Again, I do not communicate with the module after establishing a connection - just leave it idling. It looks to me like a Watchdog behavior.

我不使用任何(外部)flash,裸模ule connected to CP2104 USB converter, see the attached image, and am not sure how the device boots internally. I just compiled Codeless software (v6.380.10.4) image for codeless_531_set_two_standalone without any changes and loaded it into my two modules via SWD interface. So, it boots according to the algorithm in your software. And it works the same on each of the modules - drops connection after 3 min of inactivity.

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

Added later (IMPORTANT):I just noticed that if I issue the ATI command to the module running under debugger, the response isCodeLess DA14531 v_6.380.10.4and this matches the SDK version that I use. However, if I now reboot the module with the debugger disconnected, the response to the ATI command becomesCodeLess DA14531 v_6.380.9.10（?? !!!）也许这是错误行为的原因？

好的，这几天我了解到，如果一个程序从Keil中的模块（在Degug模式下）和对话框中的对话框智能闪存程序员，那么结果是不同的。即，使用闪存程序员闪烁我的编译代码后，它显示正确的固件图像版本DA14531 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 theAdded latersection of my post above is resolved. However, the module still drops the connection after 3 minutes. Am I the only one who experiences that?

Dialog team: if the connection is not dropping for you, could you please send me the HEX image forDodeless_531_set_two_standalone.hex.that works fine for you?

Dear Dialog Team! I have provided above already two BLE captures collected by different capturing software and hardware. One of them is collected by Cypress CySmart tool and their dongle CY5677 and the other one by Silicon Labs Network Analyser. Attached is yet another most detailed capture collected by Nordic Semiconductor BLE dongle PCA10031 and their Sniffer 3.0 software that works in tandem with Wireshark (v3.2.5). The attached capture involves two devices (my Galaxy S8 phone running SmartConsole and DA14531 module with MAC 48:23:35:00:07:AA) and it can be opened with Wireshark. In each of these cases I left the connection idling after establishing it. These are my all BLE sniffer tools.

我在我的妻子的另一个Galaxy S8手机上复制了连接丢失问题，在我的较旧的Galaxy S5手机上，至少有3个我用作主人的其他非电话BLE设备。DA14531模块只是停止响应主连接事件并重置自身（我不确定第一个）。同样，只有在将Defeless_531_Standalone_set_two映像加载到模块中时，才会遇到这一点。与其他两个可用的预编译图像（Deceless_531_DataDump和Dodeless_531_Standalone）连接似乎工作正常，即3分钟后没有连接掉落，除非我从提供的源代码上编译它们。在后一种情况下，无论我编译哪个图像都会出现下降。

The pre-compiled images that I used are the ones provided by Dialog SmartBond Flash Programmer. I asked you above to send me the image that you are using for testing. Please do it. Also, please try my attached hex on your hardware.

Thank you. I am looking forward for the issues to be resolved.

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