[Bug gdb/17518] flash block_boundaries should round the offset, not the absolute address

["sekiriki at gmail dot com" <sourceware-bugzilla@sourceware.org>]

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

Seki, Tsutomu <sekiriki at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sekiriki at gmail dot com

--- Comment #1 from Seki, Tsutomu <sekiriki at gmail dot com> ---
Created attachment 8142
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8142&action=edit
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.

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