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

S210 Bootloader

I have a blank nrf51422 that I have successfully loaded with the latest S210 softdevice and working application. However, I do not see the bootloader region occupied when I open NRFgo studio. Am I to assume the bootloader is there? If not can someone point me to where I can get it? I've been searching the forums and have not been successful. I'm trying to make the device DFU. Many Thanks,

Parents
  • No bootloader is present, it must be added from e.g.:

    nordic's nRF51_SDK_v7.2.0_cf547b5.zip\ examples\dfu\experimental_ant_bootloader

    Tested, works together with thisisant's OTA_Updater_v1.1.zip


    Edit 11.5.:

    I'm sure your IRAM1 start address is wrong, because is outside of 32KB range.

    My settings:

    IROM1: start 0x3B800, size 0x4800

    IRAM1: start 0x20002800, size 0x1800 (16KB RAM only, QFAA device)

    Do not forget to set valid ANT-fs network key instead of zeros too.

    When the bootloader is started for the first time (no app valid flag), app must be transferred through OTA DFU. If done successfully, another app OTA DFU can be performed and an old app stays in device until successfull upload. Starting of dual-bank bootloader doesn't overwrite an original. Only updating of softdevice does this job.


    Edit 22.5.

    I was wrong - no special setting is necessary to run app with ANT bootloader from SDK 7.2.0 without OTA DFU:

    1. nrfjprog --recover
    2. nrfjprog --dfu --verify --programs s210_nrf51422_4.0.1_softdevice.hex
    3. nrfjprog --verify --program ANT_S210_app.hex
    4. nrfjprog --verify --program ANT_S210_bootloader.hex

    My settings for nRF51422 QFAA (16KB RAM, 256KB FLASH) is attached:

    image description

    Keil bootloader settings area for ANT bootloader before OTA DFU process:

    image description

    Updated area after OTA DFU:

    image description

  • I am having the same trouble with the ANT+ bootloader. To take it one step farther, once the application is OK to run, holding down button 1 and hitting the reset on the nRF51DK (which should put it into bootloader mode) causes the system to halt in the bootloader. I have narrowed it down to the SOFTDEVICE_HANDLER_INIT() call that is hanging if the button is pushed.

Reply
  • I am having the same trouble with the ANT+ bootloader. To take it one step farther, once the application is OK to run, holding down button 1 and hitting the reset on the nRF51DK (which should put it into bootloader mode) causes the system to halt in the bootloader. I have narrowed it down to the SOFTDEVICE_HANDLER_INIT() call that is hanging if the button is pushed.

Children
No Data
Related