Large * .bin bootloader output file

RE: Large * .bin bootloader output file

Proton — Wed, 25 Nov 2020 08:57:57 GMT

It's fine! Thank you so much for your time! It is working!!!
If someone suddenly comes to this thread with the same problem, you will still need to add
ret_val = sd_softdevice_vector_table_base_set (BOOTLOADER_START_ADDR);
VERIFY_SUCCESS (ret_val);
Good luck to all!

RE: Large * .bin bootloader output file

Vidar Berg — Wed, 25 Nov 2020 07:51:12 GMT

It is optional to store the addresses inside the MBR at 0xff8 and 0xffc, so you may skip this step.

The SVC_Handler is in your bootloader, so the bootloader is definitely starting. The problem is that this interrupt should have been forwarded to the Softdevice, not the bootloader. To fix this you need to call nrf_dfu_mbr_init_sd() before making any SD API calls.

RE: Large * .bin bootloader output file

Proton — Tue, 24 Nov 2020 22:30:56 GMT

Yes, it is written there, but the bootloader does not start.
These addresses are empty, is that how they should be?

RE: Large * .bin bootloader output file

Vidar Berg — Tue, 24 Nov 2020 08:57:45 GMT

Hi,

Sorry, I'm not sure I understand what the issue is. I quickly tested the project you uploaded and the start addresses stored in UICR @ 0x10001014 does match the start address of your bootloader.

RE: Large * .bin bootloader output file

Proton — Mon, 23 Nov 2020 13:21:41 GMT

If in SES - Project Options - Linker I change from
FLASH RX 0x0 0x80000;RAM RWX 0x20000000 0x10000;uicr_bootloader_start_address RX 0x10001014 0x4;bootloader_settings_page RX 0x0007F000 0x1000;uicr_mbr_params_page RX 0x10001018 0x4;mbr_params_page RX 0x0007E000 0x1000
on
FLASH RX 0x0 0x80000; RAM RWX 0x20000000 0x10000;
then everything is recorded correctly, but the bootloader does not start

RE: Large * .bin bootloader output file

Proton — Mon, 23 Nov 2020 13:08:23 GMT

Sorry, I understand that.
At the moment I have 2 problems:
1. The actual address of the bootloader is always greater than the one I write (by 0x7000).
2. Overwritten softdevice

RE: Large * .bin bootloader output file

Vidar Berg — Mon, 23 Nov 2020 09:43:42 GMT

Did you have a specific problem in mind? I don't have time to do a full review of your implementation, so I need to know what to look for.

RE: Large * .bin bootloader output file

Proton — Sun, 22 Nov 2020 22:48:24 GMT

Hello!
Are there any results? I really hope to get any advice from you!

RE: Large * .bin bootloader output file

Proton — Thu, 19 Nov 2020 14:39:51 GMT

Yes indeed. If we make an example of a Nordic loader as the output format * .bin, the same situation. I thought this was the problem on which Softdevice overwrites the MBR, which now seems questionable.

May I ask you to see my example of the simplest bootloader? The project should be placed in nrf5sdk16 \ examples \ ble_peripheral \
devzone.nordicsemi.com/.../7573.Bootloader.zip

RE: Large * .bin bootloader output file

Vidar Berg — Thu, 19 Nov 2020 11:54:21 GMT

Hello,

[quote user=""]Then I get the size of * .bin file 261 745 KB. Clearly a memory error.[/quote]

This is as expected. *.bin files don't have any address records like intelhex files, so byte padding is needed to get address offsets. And there is a lot of padding needed when you have a start address in FLASH and end address in the UICR's memory range (0x10001018 = 262 148 kB).