Helpful ReplyHot!Update a bootloader from application (bootloader the bootloader itself)

Page: < 12 Showing page 2 of 2
Author
Oliver
Starting Member
  • Total Posts : 37
  • Reward points : 0
  • Joined: 2010/10/14 07:42:12
  • Location: 0
  • Status: offline
Re: Update a bootloader from application (bootloader the bootloader itself) 2019/03/26 13:22:06 (permalink)
0
Update: I got it working, but only for one cycle.
Means: I program the bootloader with the ICD, bootloader the main app and update the bootloader over the main app. After a power cycle, the new bootloader version is active and still booting into the main appication (nice!).
Issue: From now on, no flash access works anymore. Neither from main app nor from the bootloader itself. It seems, the flash erase function fails already (finishing after milliseconds). Can something during flash of bootloader happen, what makes future flash access fail? Can anything be locked?
 
Cheers,
 Oliver
#21
Oliver
Starting Member
  • Total Posts : 37
  • Reward points : 0
  • Joined: 2010/10/14 07:42:12
  • Location: 0
  • Status: offline
Re: Update a bootloader from application (bootloader the bootloader itself) 2019/03/27 04:41:34 (permalink)
0
Finally I got it workinggrin. I had to restrict the flash erase/write to following areas (like mentioned by user aschen in a previous post):
 
[9FC0_0000 - 9FC0_1FFF](BFM) and [9D00_0000 - 9D00_AFFF](BOOTLOADER-APP)
 
Before I only restricted area for config words [0x9FC0_2FF0 - 0x9FC0_2FF0] from being overwritten. But this was not sufficient. There seems to be more in the hex file, which corrupted (whatever) section in the memory. Explicitly only allow the two above mentioned regions and it works!
 
I would like to thank all of you, but especially aschen, for the great support on this topic!
 
Cheers,
 Oliver
post edited by Oliver - 2019/03/28 01:44:57
#22
Page: < 12 Showing page 2 of 2
Jump to:
© 2019 APG vNext Commercial Version 4.5