Bringing up sheeva board using guru plug jtag module

[kristizz]

Hi. In a clumsy attempt to upgrade my u-boot.bin I have left my sheevaplug without a boot loader. The SheevaPlug Development Kit - Reference Board Bring-
up document suggests using a  Lauterbach JTAG debugger to run trace32 and bring up the board. As spending £000's on a lauterbach jtag would be overkill on a plug (although it does look like a very nice debugger), I am wondering if there is anyway of bring this up with the guruplug jtag module-I can't connect through minicom.

What do we think?

[apemberton]

If you have a white sheevaplug or a black esata sheevaplug (NOT Guruplug or Dreamplug) you do not need anything more than the USB cable supplied with the kit. The JTAG lines from the processor are connected to the dual port FDTI USB to Serial chip. One of the serial ports of the FDTI 2232 IC is connected to a UART on the processor which is for console access by u-boot and kernel. The other is specially adapted to connect to the TDx lines of a JTAG port on the processor. The JTAG takes full control of the processor.

It is possible to restore a u-boot.bin (or in my case u-boot.kwb) using OpenOCD on (preferably) a Linux or 32bit Windows PC. Using 64Bit Windows 7 with OpenOCD has defeated me due to the necessary FDTI drivers. I really don't want to be bothered with Cygwin or MingW as I have a Linux PC. Incidentally I am using (very rarely) OpenOCD 0.5.0. There are suitable JTAG FDTI 2232 windows drivers available from the Globalscale site (I think). Access to the Windows device manager may be necessary to install/uninstall the standard USB/Serial driver or the special JTAG port drivers

So for a Sheevaplug, you do not need to buy expensive JTAG hardware, the Guru/Dreamplug JTAG box or proprietary software. Just the USB to mini USB cable supplied and working OpenOCD software.

[kristizz]

If you have a white sheevaplug or a black esata sheevaplug (NOT Guruplug or Dreamplug) you do not need anything more than the USB cable supplied with the kit. The JTAG lines from the processor are connected to the dual port FDTI USB to Serial chip. One of the serial ports of the FDTI 2232 IC is connected to a UART on the processor which is for console access by u-boot and kernel. The other is specially adapted to connect to the TDx lines of a JTAG port on the processor. The JTAG takes full control of the processor.

It is possible to restore a u-boot.bin (or in my case u-boot.kwb) using OpenOCD on (preferably) a Linux or 32bit Windows PC. Using 64Bit Windows 7 with OpenOCD has defeated me due to the necessary FDTI drivers. I really don't want to be bothered with Cygwin or MingW as I have a Linux PC. Incidentally I am using (very rarely) OpenOCD 0.5.0. There are suitable JTAG FDTI 2232 windows drivers available from the Globalscale site (I think). Access to the Windows device manager may be necessary to install/uninstall the standard USB/Serial driver or the special JTAG port drivers

So for a Sheevaplug, you do not need to buy expensive JTAG hardware, the Guru/Dreamplug JTAG box or proprietary software. Just the USB to mini USB cable supplied and working OpenOCD software.

Hi. Thanks for the response. The machine that I'm using to do this is running debian testing-although I have a netbook with slackware and the latest version of openocd from the git repo.

I should add that this is actually a tonido plug (essentially a sheeva minus the jtag-I got a guru plug jtag and just plugged it in to the board-it worked well with screen and minicom). I've compared what I have with the sheeva schematics and it's identical.

When I do this:

Code:

openocd -f /usr/local/lib/openocd/board/sheevaplug.cfg -c init -c sheevaplug_reflash_uboot -c exit

I get this output:

Code:

Open On-Chip Debugger 0.5.0 (2011-08-09-08:45)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
2000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
sheevaplug_load_uboot
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Error: couldn't bind to socket: Address already in use

I am doing a bit of googling to get up to speed what is happening here, but any support is welcomed!