Summary: | flash block_boundaries should round the offset, not the absolute address | ||
---|---|---|---|
Product: | gdb | Reporter: | Jim Paris <jim> |
Component: | gdb | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | NEW --- | ||
Severity: | normal | CC: | sekiriki |
Priority: | P2 | ||
Version: | 7.7 | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Attachments: | Fixes #17518, that happens when the start address of the mem region is not on the boundary of its blocksize |
Description
Jim Paris
2014-10-28 21:45:08 UTC
Created attachment 8142 [details] Fixes #17518, that happens when the start address of the mem region is not on the boundary of its blocksize I'm facing on the same kind of the bug, for some processor which have memory region whose start address is not on the boundary of its block size. For instance, MB9AF156NA MCU has SA3 whose block size is 48k and its start address is 16k, that is not on the boundary of 48k. (see http://www.spansion.com/downloads/MB9AB40N_MN706-00019-E.pdf) In this case, GDB issues vFrashErace packet with start = 0 and length = 48k. To correct this, address should be offset to its start address before rounding to block size, and restore original offset after that. |