diff options
author | Marek Vasut <marek.vasut@gmail.com> | 2010-10-31 05:24:36 +0100 |
---|---|---|
committer | Marek Vasut <marek.vasut@gmail.com> | 2010-11-05 11:25:57 +0100 |
commit | 0649fb2f6c7e1bea138769ecc2ec8dc17ae98044 (patch) | |
tree | afe135375d0a333d53618bf67cd2fb6f13b1b389 /src/target/arm_adi_v5.h | |
parent | 9e3d43cfe75df7c4f6797d630576f1a02428b218 (diff) |
ADIv5: Introduce function to detect ROM Table location
This patch adds function called "dap_detect_debug_base()", which should be
called to get location of the ROM Table. By walking ROM Table, it's possible to
discover the location of DAP.
Sadly, some CPUs misreport this value, therefore I had to introduce an fixup
table, which will be used in case such CPU is detected.
Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
Diffstat (limited to 'src/target/arm_adi_v5.h')
-rw-r--r-- | src/target/arm_adi_v5.h | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/target/arm_adi_v5.h b/src/target/arm_adi_v5.h index 92469eb4..27a2f2f8 100644 --- a/src/target/arm_adi_v5.h +++ b/src/target/arm_adi_v5.h @@ -178,7 +178,6 @@ struct adiv5_dap uint32_t memaccess_tck; /* Size of TAR autoincrement block, ARM ADI Specification requires at least 10 bits */ uint32_t tar_autoincr_block; - }; /** @@ -380,6 +379,9 @@ int mem_ap_write_buf_u32(struct adiv5_dap *swjdp, /* Initialisation of the debug system, power domains and registers */ int ahbap_debugport_init(struct adiv5_dap *swjdp); +/* Probe the AP for ROM Table location */ +int dap_get_debugbase(struct adiv5_dap *dap, int apsel, + uint32_t *dbgbase, uint32_t *apid); struct target; |