Device is always in bootloader mode

RE: Device is always in bootloader mode

Khandker Mahmudur Rahman — Sun, 30 Mar 2014 10:56:52 GMT

excellent solution.. worked for me :D

RE: Device is always in bootloader mode

FormerMember — Tue, 04 Feb 2014 10:09:39 GMT

Hello aa67, Did you remember to flash the softDevice? Does the application work fine without the bootloader?

RE: Device is always in bootloader mode

mira67 — Fri, 24 Jan 2014 20:15:01 GMT

I followed this procedure:

change the setting for bootloader
merger bootloader and application
flash use nRFgo studio

But the application is not running, seems the bootloader is not working properly, any ideas? Thanks

RE: Device is always in bootloader mode

FormerMember — Fri, 29 Nov 2013 07:53:53 GMT

As already mentioned above: "The SoftDevice, DFU, and the application can be merged into one hex-file. Remember to preset the "valid application" flag in the bootloader (DFU)."

RE: Device is always in bootloader mode

John — Fri, 29 Nov 2013 02:10:22 GMT

I do as you said and then follow: 1、mergehex.exe -m s110_nrf51822_5.2.1_softdevice.hex bootloader.hex -o app_ota.hex 2、Program app_ota.hex by using nrfjprog 3、Program app_ota.hex by using nrfjprog This can be done successfully.I wonder whether I can use the mergehex.exe to mergehex the three files(softdevice\ bootloader\application) as one file so that I just need to program only once?

Could you have any other good idear for make products and improve the efficiency.Thanks.

Who can give me the advice?Thanks

RE: Device is always in bootloader mode

John — Thu, 28 Nov 2013 08:45:51 GMT

Could you have any other good idear for make products and improve the efficiency.Thanks.

Look forward to your reply.Thanks

RE: Device is always in bootloader mode

Bastiaan — Tue, 26 Nov 2013 21:21:33 GMT

Actually I'm setting it. How can I save it so the bootloader loads my app

RE: Device is always in bootloader mode

Guest — Tue, 26 Nov 2013 21:21:33 GMT

Actually I'm setting it. How can I save it so the bootloader loads my app

RE: Device is always in bootloader mode

Guest — Tue, 26 Nov 2013 21:11:48 GMT

How do you set and save the valid application flag?

RE: Device is always in bootloader mode

Bastiaan — Tue, 26 Nov 2013 21:11:48 GMT

How do you set and save the valid application flag?

RE: Device is always in bootloader mode

FormerMember — Tue, 26 Nov 2013 15:31:45 GMT

The SoftDevice, DFU, and the application can be merged into one hex-file. Remember to preset the "valid application" flag in the bootloader (DFU).

RE: Device is always in bootloader mode

FormerMember — Tue, 26 Nov 2013 15:25:09 GMT

Yes, the softdevice can be included in the mergehex.

RE: Device is always in bootloader mode

Bastiaan — Tue, 26 Nov 2013 11:11:52 GMT

For a production build, should we also include the softdevice in the mergehex?

RE: Device is always in bootloader mode

Guest — Tue, 26 Nov 2013 11:11:52 GMT

For a production build, should we also include the softdevice in the mergehex?

RE: Device is always in bootloader mode

Bastiaan — Thu, 21 Nov 2013 07:47:08 GMT

Hi Kristin Thanks for your reply , I was struggling on this issue for several days but still couldn't understand what the problem really was. Thanks for your post Regards Hariprasad

RE: Device is always in bootloader mode

Guest — Thu, 21 Nov 2013 07:47:08 GMT

Hi Kristin Thanks for your reply , I was struggling on this issue for several days but still couldn't understand what the problem really was. Thanks for your post Regards Hariprasad

RE: Device is always in bootloader mode

FormerMember — Tue, 19 Nov 2013 14:20:55 GMT

Instead of using nRFgo Studio, you can program the chip using nrfjprog.exe from cmd, using the following command: nrfjprog.exe --program app_ota.hex --reset

RE: Device is always in bootloader mode

Guest — Mon, 18 Nov 2013 14:42:52 GMT

Thanks for the response. Changing the bootloader did solve the problem that a DFU update is required.

I also tried your points 2 and 3. When i tried to program the merged hex file with nRFgo Studio the following error occurs: Running application C:/Temp/nrf51Studio/nrfjprog.exe --snr XXXXXXXXX --program myimage.hex --reset ERROR: Attempted to write to UICR page while programming application..

RE: Device is always in bootloader mode

Bastiaan — Mon, 18 Nov 2013 14:42:52 GMT

Thanks for the response. Changing the bootloader did solve the problem that a DFU update is required.

RE: Device is always in bootloader mode

FormerMember — Mon, 18 Nov 2013 14:04:08 GMT

Hello,

It is possible to program both the bootloader and the application at the same time. It can be done by following the procedure below: Note that this is provided as is.

1) In the bootloader, the flag for valid application has to be set. By doing so the application will by default start running. In bootloader_util_arm.c change:

uint8_t  m_boot_settings[CODE_PAGE_SIZE] __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used)) ;

uint8_t  m_boot_settings[CODE_PAGE_SIZE] __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used)) = {BANK_VALID_APP};

2) Merge the bootloader hex-file and the application hex-file into one hex-file using the following command (ble_app_proximity used as an example): mergehex.exe -m ble_app_proximity.hex bootloader.hex -o app_ota.hex

3) The app_ota.hex (the merged hex-file) can be programmed onto the chip using nRFgo Studio.

Best regards, Kristin

RE: Device is always in bootloader mode

Adrian Eggenberger — Sat, 16 Nov 2013 14:58:34 GMT

Hi, I understand why it's necessairy to do a update over DFU. This sets the "application valid" token and the bootloader may boot into the application.

What about production environments? The produced devices will have a bootloader and an application on it. Both sould be programmed over JTAG. How to avoid this behavior in these circumstances?

Regards Adrian

RE: Device is always in bootloader mode

Ole Morten — Fri, 15 Nov 2013 13:50:49 GMT

This is available on the download tab on the kits on our regular web-site, as it has always been. The latest version, that includes DFU support is 3.5.0: x64: https://www.nordicsemi.com/eng/content/download/19422/311904/file/mastercontrolpanel.3.5.0.8226.x64.msi x86: https://www.nordicsemi.com/eng/content/download/19421/311889/file/mastercontrolpanel.3.5.0.8226.x86.msi

RE: Device is always in bootloader mode

balaji — Fri, 15 Nov 2013 13:36:10 GMT

Thanks for your reply prasad, please provide the link for latest master control panel.

RE: Device is always in bootloader mode

Prasad — Fri, 15 Nov 2013 12:29:15 GMT

Hi Balaji

I also faced the same issue while using command prompt for device firmware update. So I downloaded latest master control panel with API for DFU so that you can easily update the firmware.

Regards Prasad

RE: Device is always in bootloader mode

FormerMember — Fri, 25 Oct 2013 12:19:04 GMT

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