How to reflash the soft device without MBR

Question

Hello, 
 I'm flashing a bootloader (DFU) and then i'm flashing my application but each time i flash the application, Segger Embedded reflashes the softdevice and the MBR. As a result, it erases the address 0xFF8 and 0xFFC that contains the bootloader address and then the FDS cannot identify the right area where to write. 
 Is it possible to not upload the softdevice when i flash my bootloader or at least the MBR part ? 
 THank you in advance, 
 Best regards, 
 Aurélien

Einar Thorsrud · Accepted Answer

Hi, 
 Aurele said: I'm saying that because, then, after flashing my application by using SWD, i can see : 
 I assume these numbers are the content at the addresses (for instance MBR_BOOTLOADER_ADDR shows the content at (uint32_t*)0xFF8). Either this is not the case (you print something you did not intend to), or there is something else happening. This is in the MBR region, but these words are part of the bootloader .hex file. It can only be reset to all FF's if you have performed a page erase on the MBR page? Or never flashed the MBR? 
 I suspect you have done something odd, but not entirely sure what. could it be that you first programmed the bootloader, then programmed the SoftDevice (including MBR) using --sectorerase? If so, this would explain it. 
 If the bootloader address is not present as in this case (all FF's), the MBR will jump straight to the application instead of the bootloader. In this case, FDS will also think that the FDS pages are in the end of the flash, but those will be corrupt since it is actually the bootloader that has been flashed here (FDS requires pages to have a FDS header, alternatively empty so that it can initialize them).

How to reflash the soft device without MBR

Top Replies