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

Replacing bootloader through nrfjprog - Error: Single: Invalid Bank

I am trying to upload a bootloader to an nRF52832 chip. (This chip is on the ruuvitag and is programmed through their developer board).

I got the bootloader working on the DK but when I tried to upload it to the Ruuvitag I get the log output: Error: Single: Invalid Bank Info: Error code - sd_ble_cfg_set: 0x00000000

The ruuvitag comes with a bootloader based on SDK 12 and SD 3. I am using SDK 13 and SD 4. I am programming using nrfjprog and compiling with GCC.

I suspect that the issue is because of some settings related to the original bootloader that gets confused when loaded with the SDK 13 bootloader, but I am really stuck.

Parents
  • Hey Hung, The command I used was: nrfjprog --eraseall -f nrf52 The output I get is: Erasing user available code and UICR flash areas. Applying system reset.

    I built the bootloader using gcc and a makefile. I was using soft devices v4 (I think that answers your question)

    The reason I thought that perhaps the previous bootloader was an issue was that there is the master boot record which keeps track of bootloaders loaded onto the board and I wasn't sure if this was erased with all the other flash memory. In addition to this, when I programmed the chip on the DK the bootloader worked, but when I tried to load it onto the chip on the Ruuvi it didn't. One difference I could think of between them was that the Ruuvi already had a bootloader on it.

Reply
  • Hey Hung, The command I used was: nrfjprog --eraseall -f nrf52 The output I get is: Erasing user available code and UICR flash areas. Applying system reset.

    I built the bootloader using gcc and a makefile. I was using soft devices v4 (I think that answers your question)

    The reason I thought that perhaps the previous bootloader was an issue was that there is the master boot record which keeps track of bootloaders loaded onto the board and I wasn't sure if this was erased with all the other flash memory. In addition to this, when I programmed the chip on the DK the bootloader worked, but when I tried to load it onto the chip on the Ruuvi it didn't. One difference I could think of between them was that the Ruuvi already had a bootloader on it.

Children
No Data
Related