Magnus Lundin wrote:
> Hi
>
> There are some problems with dap info, but it seems the results are
> useful anyway.
> Her comes my interpretation:
>> > dap info 0
>> ap debugbase 0xffffffff
>> ap identification register 0x14770001
>> No ROM table present
> This is a MEM-AP port AHB bus with no ROM table. This could be the
> access to system memory.
> Try reading , and writing memory, things like
>
> dap apsel 0
> mdw 0 16
Does this tell you anything?
-- cut --
> jtag tapenable omap3.cpu
Enabling Cortex-A8 @ OMAP3
Cortex-A8 @ OMAP3 enabled
1
> scan_chain
TapName | Enabled | IdCode Expected IrLen
IrCap IrMask Instr
---|--------------------|---------|------------|------------|------|------|------|---------
0 | omap3.cpu | Y | 0x00000000 | 0x0b6d602f | 0x04 |
0x01 | 0x00 | 0x0f
1 | omap3.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 |
0x01 | 0x0f | 0x3f
> target create omap3.cpu cortex_m3 -endian little -chain-position
omap3.cpu
> dap info 0
ap debugbase 0xffffffff
ap identification register 0x14770001
No ROM table present
> dap apsel 0
ap 0 selected, identification register 0x14770001
> mdw 0 16
invalid command name "mdw_0"
called at file "command.c", line 456
called at file "embedded:startup.tcl", line 89
called at file "embedded:startup.tcl", line 93
> mdw 0x00000000
invalid command name "mdw_0x00000000"
called at file "command.c", line 456
called at file "embedded:startup.tcl", line 89
called at file "embedded:startup.tcl", line 93
> omap3.cpu mdw 0x00000000
AHBAP Cached values: dp_select 0x0, ap_csw 0xa2000012, ap_tar 0xffffffff
SWJ-DP STICKY ERROR
Read AHBAP_CSW 0x0
Block read error address 0x0, count 0x1
Runtime error, file "command.c", line 456:
error reading target @ 0x00000000
> omap3.cpu mdw 0x00000000 16
Runtime error, file "command.c", line 456:
expected: mdw ADDR [COUNT]
>
-- cut --
?
Best regards
Dirk
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
