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

Device is always in bootloader mode

Hi,

My device is always in bootloader mode, even if i flash the sample heart rate application it is not entering into the application. Actually, before it was working fine, i know that, if there is no valid application in the code region 1 the device should always in dfu mode, but after flashing a valid application like ble_app_hrs and ble_app_proximity, the device should enter into the application. I also checked this with the same device before, it was working fine, but now it is not working, So can anyone guess the source of the problem.

Regards, Balaji

bootloader_error.png

Parents
  • FormerMember
    0 FormerMember

    Hello,

    Did you remember to flash the application, ble_app_hrs or ble_app_proximity, using DFU? If the application is flashed in Keil, the chip will not know that a valid application is flashed to chip, and therefore not leave the DFU mode. That is why the application has to be flashed using DFU. This post shows the steps for flashing an application using DFU.

    Regards, Kristin

  • FormerMember
    0 FormerMember in reply to FormerMember

    When writing an application to the chip using the bootloader, it will write a flag to flash to mark the application as valid after having received the complete image. If you flash an application using Keil, this flag will not be written, and hence the application not started, even though it might be actually be valid.

    How to set up the command line enviroment is explained in C:\Keil\ARM\Device\Nordic\nrf51822\Board\nrf6310\device_firmware_updates\experimental\ble_dfu_send_hex\readme.txt

Reply
  • FormerMember
    0 FormerMember in reply to FormerMember

    When writing an application to the chip using the bootloader, it will write a flag to flash to mark the application as valid after having received the complete image. If you flash an application using Keil, this flag will not be written, and hence the application not started, even though it might be actually be valid.

    How to set up the command line enviroment is explained in C:\Keil\ARM\Device\Nordic\nrf51822\Board\nrf6310\device_firmware_updates\experimental\ble_dfu_send_hex\readme.txt

Children
No Data
Related