Hi Magnus,
Magnus Lundin wrote:
> That looks very interesting.
>
> Here is a new patch against head that should give very much information.
> It is tested on a STM32 CortexM3.
> Looking at the code you can se how I think we must read the ROMTABLE
> information structure.
>
> The command syntax is now
>
> >dap info n
>
> >dap select n
You tried to test with this if I will read the patch, no? ;)
It seems to be
> dap apsel n
instead.
> If there are no problems found I will commit to head.
The output on OMAP3 BeagleBoard:
-- 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 apsel 0
ap 0 selected, identification register 0x14770001
> dap info 0
ap debugbase 0xffffffff
ap identification register 0x14770001
No ROM table present
> dap apsel 1
ap 1 selected, identification register 0x04770002
> dap info 1
ap debugbase 0x80000000
ap identification register 0x04770002
No ROM table present
> dap apsel 2
ap 2 selected, identification register 0x14760010
> dap info 2
ap debugbase 0x00000000
ap identification register 0x14760010
No ROM table present
> dap apsel 3
ap 3 selected, identification register 0x00000000
> dap info 3
ap debugbase 0x00000000
ap identification register 0x00000000
No ROM table present
> dap apsel 4
ap 4 selected, identification register 0x00000000
> dap info 4
ap debugbase 0x00000000
ap identification register 0x00000000
No ROM table present
> dap apsel 5
ap 5 selected, identification register 0x00000000
> dap info 5
ap debugbase 0x00000000
ap identification register 0x00000000
No ROM table present
>
-- cut --
Best regards
Dirk
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
