• State Verified Answer
  • Replies 11 replies
  • Subscribers 74 subscribers
  • Views 1891 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 249555
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Sequence for Bootloader to configure SoftDevice

Harry

Hi,

In our existing project, it has a Bootloader and MBR, but no SoftDevice. Transport is UART for DFU.

I need to port the Bootloader to work on another project that uses SoftDevice.

I read that Bootloader needs to configure SoftDevice by calling the APIs.

I have 2 questions:

1. What are the things in SoftDevice that need to be configured by the Bootloader? Or, what is the right sequence for Bootloader to initialize and configure SoftDevice?

2. In the Bootloader sct file, the start address is 0xD6000, and the size is 0x1A000. But when I checked the hex file, the address ended at 0xE7000, while according the sct file, it ends at 0xF0000. The Bootloader settings location is at 0xEF000. Should I move it to be higher than 0xF0000?

Thanks.

  • 0 in reply to Einar Thorsrud

    Ah I see, so what I missed is the Bootloader settings.

    I have 2 questions remain:

    1. How about MBR Params page? Do I need to generate it too?

    2. I saw somewhere in this forum that Bootloader need to call sd_softdevice_vector_table_base_set(). Bootloader forwarding interrupts and jumping to 0x1000, is it a new behavior? So, does it mean there is no need anymore for such init type SoftDevice API calls (i.e. sd_softdevice_vector_table_base_set)?

    Thanks a lot.

  • 0 in reply to Harry

    Hi,

    Harry said:
    1. How about MBR Params page? Do I need to generate it too?

    No. The MBR params page should not be programmed (if it contains any data, the MBR will erase it).

    Harry said:
    2. I saw somewhere in this forum that Bootloader need to call sd_softdevice_vector_table_base_set(). Bootloader forwarding interrupts and jumping to 0x1000, is it a new behavior? So, does it mean there is no need anymore for such init type SoftDevice API calls (i.e. sd_softdevice_vector_table_base_set)?

    sd_softdevice_vector_table_base_set() is still used, but not for this. The bootloader always starts "applications" at 0x1000 and does not care if it is a SoftDevice or application. As part of this, it also forwards interrupts there using nrf_dfu_mbr_irq_forward_address_set(). If the application is there, then it runs after the bootloader has branched to it. If the SoftDevice is there, it will in turn forward interrupts to the application, which always starts immediately after the SoftDevice, and will branch there.

  • 0 in reply to Einar Thorsrud

    Thank you so much.

    Btw, I generated bootloader settings using nrfutil, I entered the start address as integer (978944), it confirmed that the start address is at 0xEF000.

    But when I opened the hex file using J-Flash, it shows the start address is 0xEE000. I used nRF Connect, same thing, it occupies both 0xEE0000 and 0xEF000 (same data).

    What do I miss?

  • 0 in reply to Harry

    Hi,

    It seems my memory let me down.

    The "nrfutil settings generate" commons will populate the backup MBR settings region in the MBR params page unless the "--no-backup" option is used, and this is what you are seeing. This is correct.

  • 0 in reply to Einar Thorsrud

    Thank you so much.

    Just last thing to clarify, you mentioned:

    sd_softdevice_vector_table_base_set() is still used, but not for this. The bootloader always starts "applications" at 0x1000 and does not care if it is a SoftDevice or application. As part of this, it also forwards interrupts there using nrf_dfu_mbr_irq_forward_address_set().

    1. When sd_softdevice_vector_table+base_set() is used?

    2. Do I need to manually call nrf_dfu_mbr_irq_forward_address_set(), or Bootloader in the SDK has called it?

Related
Terms of service