Magnus Lundin wrote:
> Dirk Behme wrote:
>> 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
> Hard to say, but it is quite clear that we are talking to a Debug Access
> Port. We cannot talk to the memory bus get sticky errors from the DP in
> the expected places, we read reasonable values from the ID and the
> ROMADRESS register. The value returned from CSW should not be 0x0,
> perhaps the AP is turned off, there is a DEVICEEN bit in the CSW
> register and from looking through the OPAP manual it seems that there
> are security setting that can turn DAP access on and off.
>
> Could you try the version in head and check both AP 0 and AP 1.
-- cut --
> version
Open On-Chip Debugger 1.0 (2009-04-29-20:38) svn:1570
> 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 apsel 0
ap 0 selected, identification register 0x14770001
> dap info 0
ap identification register 0x14770001
Type is mem-ap AHB
ap debugbase 0xffffffff
No ROM table present
> dap apsel 1
ap 1 selected, identification register 0x04770002
> dap info 1
ap identification register 0x04770002
Type is mem-ap APB
ap debugbase 0x80000000
ROM table in legacy format
CID3 0xb1, CID2 0x5, CID1 0x10, CID0, 0xd
MEMTYPE system memory not present. Dedicated debug bus
ROMTABLE[0x0] = 0xd4010003
Component base address 0x54010000, pid4 0x4, start
address 0x54010000
Component cid1 0x90, class is CoreSight component
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd
PID3 0x10, PID2 0x2b, PID1 0xb9, PID0, 0x21
ROMTABLE[0x4] = 0xd4011003
Component base address 0x54011000, pid4 0x4, start
address 0x54011000
Component cid1 0x90, class is CoreSight component
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd
PID3 0x10, PID2 0x2b, PID1 0xbc, PID0, 0x8
ROMTABLE[0x8] = 0xd4012003
Component base address 0x54012000, pid4 0x0, start
address 0x54012000
Component cid1 0x90, class is CoreSight component
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd
PID3 0x0, PID2 0x9, PID1 0x71, PID0, 0x13
ROMTABLE[0xc] = 0xd4013002
Component not present
ROMTABLE[0x10] = 0xd4019003
Component base address 0x54019000, pid4 0x4, start
address 0x54019000
Component cid1 0x90, class is CoreSight component
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd
PID3 0x0, PID2 0x1b, PID1 0xb9, PID0, 0x12
ROMTABLE[0x14] = 0xd401b003
Component base address 0x5401b000, pid4 0x4, start
address 0x5401b000
Component cid1 0x90, class is CoreSight component
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd
PID3 0x0, PID2 0xb, PID1 0xb9, PID0, 0x7
ROMTABLE[0x18] = 0xd401d003
Component base address 0x5401d000, pid4 0x0, start
address 0x5401d000
Component cid1 0xf0, class is Non standard layout
CID3 0xb1, CID2 0x5, CID1 0xf0, CID0, 0xd
PID3 0x0, PID2 0x9, PID1 0x73, PID0, 0x43
ROMTABLE[0x1c] = 0xd4500003
Component base address 0x54500000, pid4 0x0, start
address 0x54500000
Component cid1 0x90, class is CoreSight component
CID3 0xb1, CID2 0x5, CID1 0x90, CID0, 0xd
PID3 0x0, PID2 0x19, PID1 0x71, PID0, 0x20
ROMTABLE[0x20] = 0x0
End of ROM table
> dap apsel 2
ap 2 selected, identification register 0x14760010
> dap info 2
ap identification register 0x14760010
Type is jtag-ap
ap debugbase 0x00000000
No ROM table present
> dap apsel 3
ap 3 selected, identification register 0x00000000
> dap info 3
ap identification register 0x00000000
No AP found at this apsel 0x3
No ROM table present
>
-- cut --
Best regards
Dirk
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
