| commit | 13ac3d556c8cae37807801b64c289a3e9bfde359 | |
| author | Paul Fertser <fercerpav@gmail.com> | |
| Sat, 14 Mar 2015 05:15:12 +0000 (14 08:15 +0300) | ||
| committer | Paul Fertser <fercerpav@gmail.com> | |
| Tue, 14 Apr 2015 11:44:55 +0000 (14 12:44 +0100) | ||
| tree | 54347c012ba01d9d20caad2afd4b4fa0fb9a5d8d | treesnapshot (tar.gz zip) |
| parent | eaa6d8f8392cec3fdef2fafab9af06ab627de445 | commitdiff |
target/cortex_a: emit a clear error message when dbgbase can't be detected
In some cases (the most obvious are TI's SoCs) ROM table lacks entries
for the cores, so OpenOCD has no way to determine what debug base to
use. Due to an error fixed in ec9ccaa28849 it wasn't handled properly,
and OpenOCD would continue to try using dbgbase = 0, which happened to
work for e.g. AM437x.
This patch adds a clear indication to the user that to access such a
target, dbgbase must be set manually in the config.
Reported by Felipe Balbi on IRC.
Change-Id: Id8533e708f44b76550eb8b659564f5f45717c298
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Reviewed-on: http://openocd.zylin.com/2603
Tested-by: jenkins
In some cases (the most obvious are TI's SoCs) ROM table lacks entries
for the cores, so OpenOCD has no way to determine what debug base to
use. Due to an error fixed in ec9ccaa28849 it wasn't handled properly,
and OpenOCD would continue to try using dbgbase = 0, which happened to
work for e.g. AM437x.
This patch adds a clear indication to the user that to access such a
target, dbgbase must be set manually in the config.
Reported by Felipe Balbi on IRC.
Change-Id: Id8533e708f44b76550eb8b659564f5f45717c298
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Reviewed-on: http://openocd.zylin.com/2603
Tested-by: jenkins
| src/target/cortex_a.c | diffblobblamehistory |