UART DFU MBR example

[Dinkin Uri]

Hi,

I'm trying to use uart dfu mbr example and when I flush boot loader via jlink I see that it write mbr hex file at address 0x0. My main application also started from address 0, should I move it to address MBR_SIZE or this mbr hex file used only for debugging.

[Hung Bui]

No, you need to edit the linker_section_placement_macros instead. 
Please have a look at the blinky mbr example located at \examples\peripheral\blinky\pca10040\mbr\ses

It's made for the nRF52832 but you just need to adjust the size of flash to match with your nRF52805

[Dinkin Uri]

Hi, I encountered in problem when I send fw image to boot loader, it is crushes after second write request, init packet sent ok, but when i start transfer fw image it boot loader is crushed. Do you know what can be a reason?

[Hung Bui]

Hi, 

Do you have any log from the bootloader and from nrfutil ? 

Have you done any modification to the bootloader ? Have you successfully tested with the stock bootloader example and managed to update for example the blinky example  ? 

[Dinkin Uri]

No I have not log from boot loader. I implemented protocol of boot loader in main processor that connected via uart with processor with boot loader. I send init packet and it is working fine, but when I start to send image boot loader crushes. I modified project to match it to 52805, because nordic does not provide boot loader for this processor, and modifications is not only for size, but I'm sure I implemented the protocol in right way. The problem in boot loader definitions. What can be a problem in boot loader writing firmware? What definitions in sdk_config.h I should to check?

[Dinkin Uri]

No I have not log from boot loader. I implemented protocol of boot loader in main processor that connected via uart with processor with boot loader. I send init packet and it is working fine, but when I start to send image boot loader crushes. I modified project to match it to 52805, because nordic does not provide boot loader for this processor, and modifications is not only for size, but I'm sure I implemented the protocol in right way. The problem in boot loader definitions. What can be a problem in boot loader writing firmware? What definitions in sdk_config.h I should to check?