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

Advertising does not start with S140 6.1.0, same hex run without issue with S140 6.0.0

Hi,

I am working for Adafruit on the bootloader for the upcoming feather nRF52840. Currently testing using the nrf52840DK pc10056. Everything is OK with S140 6.0.0 . Today I tried to upgrade the SD to 6.1.0 but the BLE won't start ( advertising cannot be discovered ). The very same code/hex is running fine with S140 6.0.0. I have tried to change settings here and there but couldn't figure out how. This is weird since 6.1.0 is supposed to be binary compatible with 6.0.0, maybe I am doing something wrong but could get away with 6.0.0 ???

I am really appreciated if you guys could help to shed some light, the code repo is here: 

https://github.com/adafruit/Adafruit_nRF52_Bootloader 

you should compile and flash it with 

make BOARD=pca10056 all flash

https://github.com/hathach/nrf52_6.1.0_test

The code is very minial, all contains in a single main.c file, it only advertise and does not do any other thing. except blinky led1, and turn on led2 if there is an error with sd-* call

github.com/.../main.c

You can compile and flash with 

make all flash

To flash S140 6.1.0

make sd610

to flash S140 v 6.0.0

make sd600

If I flashed S140 6.0.0 first and run above command, it will show up as "AdaDFU", but if S140 6.1.0 is flashed nothing ~.~

I attached the compressed hex file for your convenience.

Update: I create a seperated repo with minimal amount of code that can demonstrate  S140 v6.1.0 is not binary compatible with S140 v6.0.0

bootloader.hex.zip

Parents
  • Hi,

    Thank you for the updates, and for the example for reproducing.

    I have been using nRF Connect for desktop for testing. Have you done the same?

    It turns out there are compatibility issues between the current release of nRF Connect for desktop and s140 v6.1.0, due to a known bug/limitation with the SoftDevice used for the connectivity firmware (s132 v3.0.1). The behavior that I see, both when testing SDK examples and when using the minimal example that you provided, seems to be consistent with what to expect given this compatibility issue. We are working on a fix for nRF Connect and the connectivity firmware.

    Do you see similar issues when using other tools for connecting to your device, such as nRF Connect for mobile?

    Regards,
    Terje

  • Thank you for looking into the issue, I am just using nrfconnect app on android & iOS. Both cannot detect advertising with the minimal code above.

  • Hi,

    Thank you for the clarification.

    I can confirm the behavior, and the SoftDevice team is looking into the issue. Unfortunately we have not figured out what causes this yet, but we will continue investigating after the weekend. I will keep you updated.

    Regards,
    Terje

Reply Children
Related