Hello Dialog,
We are working to create an end to end IoT system, it is having two hardware modules one is Edge Node and another is a gateway. At the edge node, we were using DA14585 SoC integrated with an IMU sensor and at the gateway, we are using the bluetooth+cellular supported module.
With the help of Pro Dev board, Da14585 daughter card and IMU sensor breakout board(I2c connection), we have tested the edge node by writing a code in SDK 6.0.4, it worked fine, the data is successfully reached to the gateway and from there to the cloud. But when we upgrading our code to newer SDK from 6.0.6 and above the same was not happening. The exact problem we are facing is when the gateway is sending a read command to the edge node for the data packet, the edge node is responding with the empty packet. But with SDK 6.0.4, whenever the gateway requesting a read command the edge node is responding with the expected data packet.
We have compared all latest SDK with the SDK 6.0.4, the updated details are multiple custom database implementation, wherein the SDK 6.0.4 there is only one custom database was defined but in above SDK 6.0.4 the custom database was entirely changed. Will that creating a problem for us?
We have tried by uploading fresh ble_app_peripherial code without changing anything inside the code for reading the existing ADC value (counter increment value )with the gateway, again with the SDK 6.0.4 we are able to get incremented counter data at the gateway but the same thing was not happening with the SDK 6.0.6 and above SDK versions.
Please help me with this.
Thank you
D.Vishnu
Hi vishnuatdialog,
Could you please run the default ble_app_peripheral example, as it is in the latest SDK, in debug mode? You mentioned that when using the SDK6.0.4 the example is fully function, but when using the SDK6.0.6 or SDK6.0.10, could you please clarify which the problem is? Does the firmware get stuck somewhere? Or does your firmware end up in a hardfault? Does the DA14585 advertising? Please, try to run in in debug mode and hot attach the debugger. Also, try to get a sniffer log as well, this might help us in order to understand what gets wrong.
Thanks, PM_Dialog