[Eduard]

Thank you for your help!

I also asked for support from Segger and they noticed right away that I was using two different addresses from the same memory sector. For STM32H743II processor the first memory sector is from 0x08000000 to 0x08020000 which means that my bootloader (0x08000000) and application (0x08008000) were both in the same memory sector. For erase, the smallest unit is always one sector, so when erasing the first sector to program my application the bootloader was erased as well.

I modified my application to start at 0x08020000 and everything seems to be working perfectly.

Thanks again for your support!

[Eduard]

Hi Johanan,

We are not using two different linker scripts because very often we have to interrupt a tool, program a development version for testing and then program the old stable version back and continue the operation. We want to minimize the interruption time so programming the bootloader would be an additional step that we want to avoid if possible.

[Eduard]

Thank you for your help.

I followed your instructions and found that the “load” command erases the entire memory. I used the “x/10x 0x<ADDRESS>” command before and after the “load” command. After the “load” command, the bootloader address is erased. I am going to check with Segger support to see if they can help me.

Also, what do you mean by checking the FLASH protection bits? Can you give me some more details please?

 

[Author]

Posts