Hi,
I have seen that openOCD doesn’t support the beagleboard yet.
Do you know if it should be supported soon, if it works partially or if it will work … some day ?
By the way I have a Flyswatter Jtag (which if I understood well tends to be used by some others …)
cheers,
Maxime
I have seen that openOCD doesn't support the beagleboard yet.
Do you know if it should be supported soon, if it works partially or if it
will work ... some day ?
By the way I have a Flyswatter Jtag (which if I understood well tends to
be used by some others ....)
The last status I have heard is, that we were waiting for openOCD to
integrate proper support for inserting/removing cores from the JTAG chain
"on the fly", as it's done with the ICEPICK in the OMAP devices when the
cores are powered up/down...
This information however is some weeks old and a lot of stuff might have
changed since then - Hopefully? 
/Søren
Søren Steen Christensen wrote:
I have seen that openOCD doesn't support the beagleboard yet.
Do you know if it should be supported soon, if it works partially or if itwill work ... some day ?
By the way I have a Flyswatter Jtag (which if I understood well tends to
be used by some others ....)
The last status I have heard is, that we were “waiting” for openOCD to
integrate proper support for inserting/removing cores from the JTAG chain
"on the fly", as it's done with the ICEPICK in the OMAP devices when the
cores are powered up/down...This information however is some weeks old and a lot of stuff might have
changed since then - Hopefully?
Recent status is that OpenOCD developers need some additional info from TI for proper JTAG configuration. They like to wait with further work until they have this info. This is last status I have from January 15, 2009.
Dirk - waiting for OpenOCD & Flyswatter& Beagle, too
P.S.: CCed OpenOCD list
Hi,
I have seen that openOCD doesn't support the beagleboard yet.
Do you know if it should be supported soon, if it works partially or if it
will work ... some day ?
It's been a roller coaster on flat land but
BeagleBoardOpenOCD - eLinux.org describe the status pretty well.
before I finally discovered that the 64 bits version of libftd2xx
was broken. Next week I will get my BeagleBoard back (that might or
might not have a broken JTAG) so I will pick it up again.
By the way I have a Flyswatter Jtag (which if I understood well tends to be
used by some others ....)
Indeed, did you also get the Adapter kit?
greetings
Hi,
I have seen that openOCD doesn’t support the beagleboard yet.
Do you know if it should be supported soon, if it works partially or if it
will work … some day ?It’s been a roller coaster on flat land but
http://elinux.org/BeagleBoardOpenOCD describe the status pretty well.From my side I have lost about 1 month trying different things out
before I finally discovered that the 64 bits version of libftd2xx
was broken. Next week I will get my BeagleBoard back (that might or
might not have a broken JTAG) so I will pick it up again.By the way I have a Flyswatter Jtag (which if I understood well tends to be
used by some others …)Indeed, did you also get the Adapter kit?
I’m not sure of what this is …
This is what I have : http://www.tincantools.com/assets/Quick%20Start.pdf
cheers
MAxime
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