Application updated over the air doesn't start properly

RE: Application updated over the air doesn't start properly

Hung Bui — Fri, 22 Dec 2017 08:40:58 GMT

I'm sorry that I don't have much experience with mbed-os. The mbed team should be at best position to help you. One thing you can do is to reading out the flash and compare the hex files between flash your application directly and flash your application via DFU OTA.

RE: Application updated over the air doesn't start properly

leon1d — Thu, 21 Dec 2017 17:33:46 GMT

when I build NRF51_DK, which means softdevice + application, the result .hex file contains the paplication start address as 0x0001b000 and it works fine.
Thanks for your suggestion. I created .mbedignore file as following:

mbed-os/rtos/* mbed-os/features/FEATURE_CLIENT/* mbed-os/features/FEATURE_COMMON_PAL/* mbed-os/features/FEATURE_UVISOR/* mbed-os/features/frameworks/* mbed-os/features/net/* mbed-os/features/netsocket/* mbed-os/features/storage/* mbed-os/events/*

then rebuilt my application as NRF51_DK_OTA target and updated it OTA and it works! As far I understood we have only one thread this way and no events. Is that right?

RE: Application updated over the air doesn't start properly

Hung Bui — Thu, 21 Dec 2017 15:17:22 GMT

Have you tried to change the start address to 0x0001b000 and flash softdevice + application ?

Could you check what happens inside wait() ? If you make a very simple application of blinking an LED (no wait()) should it work properly after OTA ?

RE: Application updated over the air doesn't start properly

leon1d — Thu, 21 Dec 2017 12:31:53 GMT

@Hung Bui Yes, NRF51_DK target: software + application (no bootloader) works fine. That is why I suspect that NRF51_DK_OTA target doesn't have proper softdevice initialization during start of the application.

RE: Application updated over the air doesn't start properly

Hung Bui — Thu, 21 Dec 2017 11:36:47 GMT

I'm not very familiar with mbed (you should post your question on mbed forum as well). But did the mbed firmware work if you flash it directly (softdevice + application, no bootloader) ? Strange to see that the start address is 0x1C000. On the ld file for S110 it was correct.

It's normal to be in wait() most likely it put the CPU to sleep and if there isn't any event, the CPU will remain in sleep mode.