Bug 17484 - Flashing blocks 'erased' loaded after 'regular'
Summary: Flashing blocks 'erased' loaded after 'regular'
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: remote (show other bugs)
Version: 7.8
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-14 10:14 UTC by Gerard Zagema
Modified: 2014-10-14 10:14 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Zagema 2014-10-14 10:14:37 UTC
Question:

Is there a reason why the memory content 'regular' (SRAM)  is loaded (X-packets) before the 'erased' blocks (FLASH)?

The problem is that if you have a mixed project with some flash and SRAM writing the flashloaders used on target side can overwrite the SRAM content.

E.g. ARM flash loaders 

Ok, this could be solved on target side by the GDB stub but we could also swap those two sections in GDB. It makes sense that we do first all the flashing etc after which we make the target ready for running and do the final RAM initialization.

I have swapped it and it works for me.