sdk9.0 bootloader settings?

[manhattan]

what does the mean of the statements the red line marked  on  above picture ? In my product ,i want to combine the softdevice,application and bootloader into one hex,and burn this all_in_one hex to nrf51822 chip with the tool jlink ,this method is ok? 

[Ole Bauck]

Hi,

It means that the default bootloader in the SDK does not know that there is a valid application on the chip and will not branch to the application. You can however change this with one line of code such that you can flash the bootloader, SoftDevice and application at once using e.g. jlink. See this post for how.

Ole

[manhattan]

Thank you ! The other question i got! In the site [https://devzone.nordicsemi.com/questi...] , i found in order to get the combination hex file of bootloader, SoftDevice and application , i need combined the "bootloader_settings.hex",so my problem is how can i create own " bootloader_settings.hex" file? PS: sdk 9.0 +nrf51822 QFAC +s110 v8.0 + keil MDK +IROM:0x3c000 it's size is 0x3c00+IRAM1:0x20002000,it's size 0x1f80+IRAM2:0x20003f80,it's size 0x80 no init

[Ole Bauck]

The link is invalid. You don't have to combine the hex files if you want to flash them using the programmer/debugger. You can flash the SoftDevice first, then the bootloader and then the application. Was this what you asked about?

[manhattan]

Thank you for your help to solve my question. I had solved this problem. For bootloader example of sdk 9.0, once i change the code :

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

to

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

the bootloader_settings.hex is not needed which i found in the invalid link [https://devzone.nordicsemi.com/questi...] . NOW,I have successfuly combined the bootloader.hex, SoftDevice.hex and application.hex into one hex and everything is ok.