diff options
| author | Kevin Buettner <kevinb@redhat.com> | 2017-10-10 22:47:01 -0700 |
|---|---|---|
| committer | Kevin Buettner <kevinb@redhat.com> | 2017-10-11 00:50:29 -0700 |
| commit | d9b477e3b7388732ed5293d929ceb5fc609916fe (patch) | |
| tree | 3a3406bcaf178c3c8066f5cda1cbe223ba29d509 /gdb/ChangeLog | |
| parent | d003af558092dc521f93d16628b9ccbf434370e3 (diff) | |
| download | gdb-d9b477e3b7388732ed5293d929ceb5fc609916fe.zip gdb-d9b477e3b7388732ed5293d929ceb5fc609916fe.tar.gz gdb-d9b477e3b7388732ed5293d929ceb5fc609916fe.tar.bz2 | |
Flash memory size not aligned to address
(This patch is from Mark Rages <markrages@gmail.com>.)
The Nordic nRF52 memory map, reported from black magic probe:
Num Enb Low Addr High Addr Attrs
0 y 0x00000000 0x00080000 flash blocksize 0x1000 nocache
1 y 0x10001000 0x10001210 flash blocksize 0x210 nocache
2 y 0x20000000 0x20010000 rw nocache
The region at 0x10001000 is "UICR" and it is a section of flash that is
erased all at once.
Notice the odd size: 0x210 is the size of the region defined in the
datasheet.
But because the block size was listed as 0x210, gdb was insisting on
issuing two erase commands divisible by 0x210, starting below 0x10001000.
This patch fixes it by doing the alignment computation from the start of
the region, not from address 0.
gdb/ChangeLog:
* target-memory.c (block_boundaries): Fix for block address not
aligned on block size.
Diffstat (limited to 'gdb/ChangeLog')
| -rw-r--r-- | gdb/ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 4f9fac2..459f0ff 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2017-10-11 Mark Rages <markrages@gmail.com> + + * target-memory.c (block_boundaries): Fix for block address not + aligned on block size. + 2017-10-10 Pedro Alves <palves@redhat.com> Tom Tromey <tom@tromey.com> |