.bin file of Secure bootloader is too much

[R_S]

Hi,

I am using nordic52840 development kit board. and I am using sdk17.1 for development.

I tried to create .bin for secure bootloader code inside DFU. but the file size is very large. for my case its around 261MB.

Can any one help me here that why i am getting this much size for binary.

For hex its only 141KB.

Regards

Rohit Saini

[Vidar Berg]

Hi Rohit,

Please see my answer in this thread: https://devzone.nordicsemi.com/f/nordic-q-a/47903/noload-directive-for-uicr_bootloader_start_address-and-uicr_mbr_params_page. The large file size is caused by byte padding needed to offset the UICR data that is part of the bootloader image.

Best regards,

Vidar

[R_S]

So looks like I need to remove the content related to uicr register from hex file and then creating bin file from it.

Now,

So in this case do i also need to program UICR register separately or not....?

And also to creating .bin from .hex which command need will be used....?

Regards

Rohit Saini  

[Vidar Berg]

Yes, you have to program the original bootloader hex that has the UICR data at 0x10001014 and 0x10001018. The MBR will not start the bootloader if this data is missing.

The start address is set here as you said:

And the MBR paramater page address at 0x10001018 here:

    __root uint32_t const m_uicr_mbr_params_page_address
        @ UICR_PARAM_PAGE_ADDR = NRF_MBR_PARAMS_PAGE_ADDRESS;

Regards,

Vidar

[R_S]

ok, got it.

So that means, if we don't want to include UICR in .bin file then we need to remove it from hex and create bin file. That's the only way right..?

regards

Rohit Saini

[Vidar Berg]

Yes, that correct. But you should be able to automate this process.

Regards,

Vidar

[R_S]

Thanks Vidar for your support.

[R_S]

And also if i create zip package from hex file then it will automatically remove the UICR register form the hex file and create the binary file from it. and the size of that bin file is exact the same what i required.