This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SD140 6.0.0-6-alpha BLE issues

Greetings -

I recently downloaded the latest SD140 images, 6.0.0-6-alpha, and began having issues with BLE communication.

I'm developing a custom device, based on the nRF52840, and we require both BLE and USB communication. The USB peripheral seems to be pretty much broken when the Soft Device is enabled, so I'm going to ignore that for the moment.

I recently migrated our code from the previous Soft Device, 5.0.0-5-alpha, which had working BLE (NUS and other services). When I attempted to discover and connect to the device using nRF Toolbox, I was unsuccessful. I reverted my code to the last working, pre-USB version, to remove any possible USB issues. This didn't resolve the problem. The only way to get BLE working again was to switch back to the 5.0.0-5-alpha version of the Soft Device.

Parents
  • That's what I'm saying: delete all header files from that s140 folder in your "old" SDK structure and copy there header files you find in s140_nrf52840_6.0.0-6.alpha.zip\s140_nrf52840_6.0.0-6.alpha_API\include folder. This is at least first step. If you corrected LD file memory regions then at least basic startup should be OK and if you enable UART or RTT debug logging (or at least some simple GPIO debug pulses you put there on your own) it should show that FW is alive. You cannot assume that with new SD and new API compiled in it will work with old SDK (although it might if there are minimum changes).

Reply
  • That's what I'm saying: delete all header files from that s140 folder in your "old" SDK structure and copy there header files you find in s140_nrf52840_6.0.0-6.alpha.zip\s140_nrf52840_6.0.0-6.alpha_API\include folder. This is at least first step. If you corrected LD file memory regions then at least basic startup should be OK and if you enable UART or RTT debug logging (or at least some simple GPIO debug pulses you put there on your own) it should show that FW is alive. You cannot assume that with new SD and new API compiled in it will work with old SDK (although it might if there are minimum changes).

Children
No Data
Related