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]

Hi Uri, 

The MBR is needed for the bootloader to operate. If your application started from address 0, you would need to move it to MBR_SIZE (0x1000). You can refer to our blinky example made for MBR compatibility \examples\peripheral\blinky\pca10040\mbr. 

[Dinkin Uri]

Hi, thank you for your help. I moved main application to address 1000h and it runs. I work with nrf52805, when I enable timer0 it application jumps to address that is unknown. Should I do something with vector table, move it to the same address (0x1000)? I make blinking with led and it works fine, but timer raise interrupt and program entering to address 0x2A0

[Hung Bui]

Could you explain what exactly you did when you moved main application to address 0x1000h ? 

Usually what you need to do is to configure the start flash address  FLASH_START in the linker to the address 0x1000. This will also move the vector table to 0x1000

[Dinkin Uri]

I create project CortexM4 for device nrf52805. In main I create output gpio and timer0 with 500 ms frequency. Run it and it run great. Now I go to project and put linker_section_placements_segments="FLASH RX 0x00001000 0x00029000;RAM RWX 0x20000000 0x00006000" and run. What I see it does not run, it just stopped in address 0x2A0

[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]

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?