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
  • Yes, I have all of SDK 13.1's s140 headers in my project, and being compiled when I build my application. Just to be clear -- last Friday I was using s140-5.0.0.2-alpha with SDK 13.1 and BLE NUS worked. I mean, I don't have the entire comm layer debugged, but I can connect and do things. Then I found there was a new s140-6.0.0.6-alpha. I modified the .ld file to reflect the new FLASH and RAM sizes, erased my entire device, reflashed the new s140 image, recompiled, flashed the relocated application, and no BLE.

Reply
  • Yes, I have all of SDK 13.1's s140 headers in my project, and being compiled when I build my application. Just to be clear -- last Friday I was using s140-5.0.0.2-alpha with SDK 13.1 and BLE NUS worked. I mean, I don't have the entire comm layer debugged, but I can connect and do things. Then I found there was a new s140-6.0.0.6-alpha. I modified the .ld file to reflect the new FLASH and RAM sizes, erased my entire device, reflashed the new s140 image, recompiled, flashed the relocated application, and no BLE.

Children
No Data
Related