Hello,
there was a thread about TI DaVinci processor DM365 (segger2.com/index.php?page=Thread&threadID=768), but unfortunately it is dead now. The core is arm926ej-s, so I think it should be possible to debug it with J-Link.
I tried suggested script for OMAP, but I got following messages:
Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B7D102F, found: 0x8B83E02F
CPU JTAG Id mismatch, read: 0x2E0D80BC
Display All
How should I please modify the script to make JLink usable with DM36x processor?
best regards
Jan
there was a thread about TI DaVinci processor DM365 (segger2.com/index.php?page=Thread&threadID=768), but unfortunately it is dead now. The core is arm926ej-s, so I think it should be possible to debug it with J-Link.
I tried suggested script for OMAP, but I got following messages:
Can not find ICE-Pick (IDCODE mismatch). Expected 0x0B7D102F, found: 0x8B83E02F
CPU JTAG Id mismatch, read: 0x2E0D80BC
Source Code
- SEGGER J-Link Commander V4.32 ('?' for help)SEGGER J-Link Commander V4.32 ('?' for help)
- Compiled Jul 29 2011 18:38:14
- DLL version V4.32, compiled Jul 29 2011 18:37:55
- Firmware: J-Link ARM V8 compiled Jul 26 2011 17:31:24
- Hardware: V8.00
- S/N: 58004787
- ETM support, Trace buffer size: 0KB
- VTarget = 3.287V
- Info: OMAP-L138 J-Link script
- Info: J-Link script: Init ICEPick
- Info: TotalIRLen = 6, IRPrint = 0x01
- Info: J-Link script: Could not halt CPU, Executing Reset
- Info: TotalIRLen = 7, IRPrint = 0x03
- ****** Error: Too few devices on the JTAG bus. IRPos: 6, TotalIRLen: 7
- Could not find supported CPU core on JTAG chain
- Found 2 JTAG devices, Total IRLen = 7:
- ****** Error: Too few devices on the JTAG bus. IRPos: 6, TotalIRLen: 7
- Could not find supported CPU core on JTAG chain
- Found 2 JTAG devices, Total IRLen = 7:
- J-Link>
best regards
Jan