SDK17.0 BEHAVING UNEVEN IN DIFFERENT PC .

[NANDHU]

HI,

•        we created an application on SDK "nRF5_SDK_17.0.0_9d13099"  .The example code used to develop the  application is "ble_app_hids_mouse". 
•        we developed the application code successfully and its working fine with our  device.
•        I developed the application code by using segger IDE (version :- 4.10a) in a windows os.

ISSUES

• After i developed the application code i zipped the SDK and shared it to my colleague . He unzipped the SDK and opened our application code in his mac os system.
• He is also using segger IDE but the version was different . He build the code successfully and flashed the code to our device but now the device is not working with exactly same code .
• Why the device is behaving uneven when we flashed the same code from two different system (with mac os and windows os )?
• Please help me to find out this issue as soon as possible.

[NANDHU]

Jared,

 I can't able to do the test now ,i already told you that system which showing the issue was not with me .

System is with my colleague and he is working from home due to corona and the Jlink debug tool is with me .

So if there is any delay issue i will close this case and open a new case when he is available.

[Edvin]

Hello Nandhu,

Jared left for vacation, so I took over this case. 

Jared made some good points in his last reply. Something is probably different in the environment when your colleague is testing. It may be the computer's BLE behaving differently from yours, it may be some differences in the build environment. However, you need to check what function that returned 0x02. If it was indeed ble_bas_battery_level_update() you need to check which function inside there that returned this value. Also, if it was one of the softdevice calls, which indicates that you are trying to send a notification, but the softdevice is not enabled yet, you need to find out why the battery_level_update() was called when the softdevice is not enabled. Is this an app_timer callback?

If yes, perhaps the timer is started before you are connected, for some reason. I can't check this, because we don't have your source code. 

Best regards,

Edvin