Hi all,
I am a newbee to debugging,i have a hardware USB JTAG Debugger provided NGX
Technologies which has 20 pin standard JTAG Header.
But BB-XM has only 14 pins,so i used a pin-pin connection between BB-XM and
Hardware Debugger using Jumper wires between.
1.I have unused EMU0 and EMU1.
2.I have connected TDI of BB-xm to Debugger TDO and vice versa.
i started openocd by changing the tcl/target/amdm37x.cfg cortex-a to
cortex-a8 @144
when i run the command on command prompt : openocd -f
tcl/interface/ngxtech.cfg -f tcl/board/ti_beagleboard_xm.
cfg -f tcl/target/amdm37x.cfg -c init -c "reset init"
it displays the fallowing log on the console
Open On-Chip Debugger 0.7.0 (2014-01-23-19:22)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 10 kHz
Warn : dm37x.dsp: huge IR length 38
trst_only separate trst_push_pull
adapter speed: 10 kHz
Warn : dm37x.dsp: huge IR length 38
Runtime Error: embedded:startup.tcl:20: Command/target: dm37x.cpu Exists
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'target' called at file "tcl/target/amdm37x.cfg", line 144
in procedure 'ocd_bouncer'
at file "embedded:startup.tcl", line 20
am unable to step further,please help me out in this regard.
for your information:
http://shop.ngxtechnologies.com/download/Schematics/JTAG/NGX_ARM_USB_JTAG.pdf
On Saturday, December 3, 2011 8:02:40 AM UTC+5:30, Jon wrote:
>
> I have:
>
> BeagleBoard xM Rev C
> Flyswatter Rev B
> OpenOCD 0.5.0
>
> The BeagleBoard works well. I don't know about the other stuff. I get
> this output from openocd, using the ti_beagleboard_xm.cfg, and
> flyswatter.cfg files:
>
> Open On-Chip Debugger 0.5.0 (2011-12-01-19:13)
> Licensed under GNU GPL v2
> For bug reports, read
> http://openocd.berlios.de/doc/doxygen/bugs.html
> Info : only one transport option; autoselect 'jtag'
> 10 kHz
> Warn : dm37x.dsp: huge IR length 38
> trst_only separate trst_push_pull
> Info : clock speed 10 kHz
> Info : JTAG tap: dm37x.jrc tap/device found: 0x2b89102f (mfg: 0x017,
> part: 0xb891, ver: 0x2)
> Warn : JTAG tap: dm37x.jrc UNEXPECTED: 0x2b89102f (mfg: 0x017,
> part: 0xb891, ver: 0x2)
> Error: JTAG tap: dm37x.jrc expected 1 of 2: 0x1b89102f (mfg: 0x017,
> part: 0xb891, ver: 0x1)
> Error: JTAG tap: dm37x.jrc expected 2 of 2: 0x0b89102f (mfg: 0x017,
> part: 0xb891, ver: 0x0)
> Error: Trying to use configured scan chain anyway...
> Warn : Bypassing JTAG setup events due to errors
>
>
> In another window I can then "telnet localhost 4444", get an ocd prompt,
> and enter commands but nothing much happens. For instance, "reset halt"
> toggles between red leds 2 and 3. I get output that looks very similar
> to the above but adding things like:
>
> Error: target not examined yet
> Runtime Error: /usr/local/share/openocd/scripts/target/amdm37x.cfg:194:
> in procedure 'amdm37x_dbginit'
> in procedure 'cortex_a8' called at file
> "/usr/local/share/openocd/scripts/target/amdm37x.cfg", line 194
>
>
> I'm not sure what I'm looking at or what the error messages are saying.
>
> Any advice?
> Thanks,
> Jon
>
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
