[Bug remote/17484] New: Flashing blocks 'erased' loaded after 'regular'

[Bug remote/17484] New: Flashing blocks 'erased' loaded after 'regular'

[forum at emblocks dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17484

            Bug ID: 17484
           Summary: Flashing blocks 'erased' loaded after 'regular'
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: forum at emblocks dot org

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.