• State Not Answered
  • Replies 1 reply
  • Subscribers 87 subscribers
  • Views 543 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 279854
Options

nRF52810 bootloader space memory

Apolline Gruaux

Hi, 

I'm using a custom board which is currently under developpement usin nRF52810. When running DFU example for NRF52810, using secure_bootloader_ble_s112_pca10040e.hex, s112_nrf52_7.0.1_softdevice.hex and a dfu enabled version of ble_app_uart_pca10040e, if I load an application which is not a version of the initial program and this multiple times, even after recovering the device and erasing the memory I'm "stuck" in the bootloader. I try reading the memory with nrfconnect programmer and the bootloader memory space is consider as application and note bootloader, after a lot of tries I can never reprogram a dfu application (a regular one it's possible) on my pcb.

Thanks for the information you will be able to provide me, 

Apolline Gruaux

  • 0

    Hi Apolline,

    I load an application which is not a version of the initial program and this multiple times, even after recovering the device and erasing the memory I'm "stuck" in the bootloader.

    Do you load the application via DFU or via a programmer? If you do via a programmer, you also need to generate and program a new bootloader settings page. Is that what you forgot?

    If this is not the issue, can you specify in detail step by step what you programmed in which order, from when things were working until it stopped working (device stays in bootloader mode)? Also, how have you verified that the device is in bootloader mode?

    even after recovering the device and erasing the memory I'm "stuck" in the bootloader.

    If the issue is as I suggested above, then the only way to fix the issue is to program a bootloader settings page. If this is not the issue, then note that with "nrfjprog -e" you will end up with a fully empty device, exactly as it shipped from production.

    I try reading the memory with nrfconnect programmer and the bootloader memory space is consider as application and note bootloader

    You should not rely on how nRF Connect Programmer describes the memory content. It is "guessing" using a too simple approach which is sometimes more confusing than helpful.

    Einar

Related