New IT forum
21 June 2018, 11:59:00 pm *
Welcome, %1$s. Please login or register.

: PiHub now in stock.
 
Pages: [1] 2

Author Topic: Flashing U-Boot on Bricked Plug  (Read 22715 times)

nihilwolf

  • Newbie
  • *
  • Posts: 2
Flashing U-Boot on Bricked Plug
« on: 07 November 2010, 04:17:46 pm »

Hello!

I need some help.
I upgraded the uboot on my GuruPlug Server Plus, but it did not work, so I bricked my plug. ::)

I tried reflashing it with Guruplug-installer.tar.gz from Plug Wiki's reflashing page, but it did not work:

Output of the original openocd from the pack (0.2):
Code: [Select]
$ sudo ./runme.sh ./uboot.bin
 ****     Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Error: trying to validate configured JTAG chain anyway...
Error: unknown EmbeddedICE version (comms ctrl: 0x00000008)
Error: unexpected Feroceon EICE version signature
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: unexpected Feroceon EICE version signature
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
   
 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

I tried a newer version of openocd, and it generated a different output:
Code: [Select]
$ sudo ./runme.sh ./uboot.bin
 ****     Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.3.1 (2010-01-18-18:43)
$URL$
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
2000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
Info : clock speed 2000 kHz
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Warn : JTAG tap: feroceon.cpu       UNEXPECTED: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu  expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Warn : Unexpected idcode after end of chain: 32 0x00000007
Warn : Unexpected idcode after end of chain: 64 0x0000007f
Warn : Unexpected idcode after end of chain: 96 0x0000007f
Warn : Unexpected idcode after end of chain: 128 0x0000007f
Warn : Unexpected idcode after end of chain: 160 0x0000007f
Warn : Unexpected idcode after end of chain: 192 0x0000007f
Warn : Unexpected idcode after end of chain: 224 0x0000007f
Warn : Unexpected idcode after end of chain: 256 0x0000007f
Warn : Unexpected idcode after end of chain: 288 0x0000007f
Warn : Unexpected idcode after end of chain: 320 0x0000007f
Warn : Unexpected idcode after end of chain: 352 0x0000007f
Warn : Unexpected idcode after end of chain: 384 0x0000007f
Warn : Unexpected idcode after end of chain: 416 0x0000007f
Warn : Unexpected idcode after end of chain: 448 0x0000007f
Warn : Unexpected idcode after end of chain: 480 0x0000007f
Warn : Unexpected idcode after end of chain: 512 0x0000007f
Warn : Unexpected idcode after end of chain: 544 0x0000007f
Warn : Unexpected idcode after end of chain: 576 0x0000007f
Warn : Unexpected idcode after end of chain: 608 0x0000007f
Error: double-check your JTAG setup (interface, speed, missing TAPs, ...)
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Warn : JTAG tap: feroceon.cpu       UNEXPECTED: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu  expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Warn : Unexpected idcode after end of chain: 32 0x00000007
Warn : Unexpected idcode after end of chain: 64 0x0000007f
Warn : Unexpected idcode after end of chain: 96 0x0000007f
Warn : Unexpected idcode after end of chain: 128 0x0000007f
Warn : Unexpected idcode after end of chain: 160 0x0000007f
Warn : Unexpected idcode after end of chain: 192 0x0000007f
Warn : Unexpected idcode after end of chain: 224 0x0000007f
Warn : Unexpected idcode after end of chain: 256 0x0000007f
Warn : Unexpected idcode after end of chain: 288 0x0000007f
Warn : Unexpected idcode after end of chain: 320 0x0000007f
Warn : Unexpected idcode after end of chain: 352 0x0000007f
Warn : Unexpected idcode after end of chain: 384 0x0000007f
Warn : Unexpected idcode after end of chain: 416 0x0000007f
Warn : Unexpected idcode after end of chain: 448 0x0000007f
Warn : Unexpected idcode after end of chain: 480 0x0000007f
Warn : Unexpected idcode after end of chain: 512 0x0000007f
Warn : Unexpected idcode after end of chain: 544 0x0000007f
Warn : Unexpected idcode after end of chain: 576 0x0000007f
Warn : Unexpected idcode after end of chain: 608 0x0000007f
Error: double-check your JTAG setup (interface, speed, missing TAPs, ...)
Info : Embedded ICE version 0
Warn : target was in unknown state when halt was requested
Error: invalid mode value encountered 3
Error: cpsr contains invalid mode value - communication failure
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
   
 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

Do you have a working version of this pack, or any other idea, how can I unbrick my guruplug?

Thanks,
NW
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 662
Re: Flashing U-Boot on Bricked Plug
« Reply #1 on: 07 November 2010, 07:44:30 pm »

Timing is everything, using the original 0.2.0-in-development version of openocd..
Prepare your command line (sudo ./runme.sh ....)
Switch on the mains power to the plug and then strike the enter key (within two seconds).

With a working U-Boot I also always prepare the serial console before switching on the plug.
It is trivial to stop the countdown and hold it on the "Marvell>" prompt. With the plug in this
state it always flashes successfully, if it gets as far as booting into Linux (which messes
with the hardware) then bad things can happen during an attempted flash. Never attempt
to flash from a warm boot, always cycle the power.

As an aside, if you leave an unpowered JTAG board connected to the plug (that is you don't
have the USB lead plugged in) it can cause the plug to stall and look like it is bricked.

What output are you getting over the serial console ?

Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

nihilwolf

  • Newbie
  • *
  • Posts: 2
Re: Flashing U-Boot on Bricked Plug
« Reply #2 on: 07 November 2010, 10:12:45 pm »

Timing is everything, using the original 0.2.0-in-development version of openocd..
Prepare your command line (sudo ./runme.sh ....)
Switch on the mains power to the plug and then strike the enter key (within two seconds).

Thanks for help, it's working! :D
Logged

machekku

  • Newbie
  • *
  • Posts: 4
Re: Flashing U-Boot on Bricked Plug
« Reply #3 on: 02 January 2011, 10:26:43 pm »

Hello,
So I'm getting the same error:
Code: [Select]
****     Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Error: trying to validate configured JTAG chain anyway...
Warn : value captured during scan didn't pass the requested check:
Warn : captured: 0x00 check_value: 0x01 check_mask: 0x0F
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
   
 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

I tried running runme.sh in a loop while turning guruplug on and off again and again and it didn't work. I tried changing cables, etc, etc.

I'm using latest 64-bit Ubuntu. I read that 32-bit OS could be better. Also I read that some distributions (and release versions) work better than others.
Could people who successfully used guruplug installer tell me which OS they used?
Thank you for your help.
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Flashing U-Boot on Bricked Plug
« Reply #4 on: 03 January 2011, 11:10:10 am »

Hi,

On a bricked Guruplug the trick is to hit enter and power up the Guru at exactly the same time.

NewIT Technical

Logged
NewITJames

machekku

  • Newbie
  • *
  • Posts: 4
Re: Flashing U-Boot on Bricked Plug
« Reply #5 on: 06 January 2011, 11:23:04 pm »

Soo.... since it seems that the timing needs to be very exact, and some people (I think it was on another forum) say about it "randomly working after 500 retries", I decided to do things in a bit less random way. I have a USB-controlled power socket, so I plugged guruplug into it. Now I can more or less (it's never 100% exact without a real-time system, I guess) the delay between turning guruplug on and starting runme.sh.
If the delay is very small (less than 350ms), error message says that the device is probably not powered on.
After more than 400ms, the well know, already mentioned in this thread error log appears.
Between 350-400ms I often get this log, which looks better, but still not as good as it should:
Code: [Select]
****     Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
Should I just keep trying, or is there something wrong with my plug?

Maybe I should mention how I bricked this plug. I wanted to upgrade u-boot, I run the nand erase ... command, then I was supposed to do nand write ..., but I misspelled it (so it did nothing) and then I was sleepy enough not to notice the problem and I did reset.
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 662
Re: Flashing U-Boot on Bricked Plug
« Reply #6 on: 07 January 2011, 09:26:36 pm »

Quote
If the delay is very small (less than 350ms), error message says that the device is probably not powered on.
I get no such error message even with the plug turned off ?!?

Quote
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
This is also divergent from my system, I get
Quote
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched

As you cannot be sure of the response time for the PSU to fire up and stabilise.....

Power up the plug.
Prepare your openocd command line.
Hit the reset button on the plug swiftly followed by the enter key.
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

sandoz

  • Newbie
  • *
  • Posts: 6
Re: Flashing U-Boot on Bricked Plug
« Reply #7 on: 25 February 2011, 10:16:13 am »

i also bricked my guruplug
i don't have a linux comp here, what can i do?
Logged

NewIT_Marcus

  • Hero Member
  • *****
  • Posts: 960
Re: Flashing U-Boot on Bricked Plug
« Reply #8 on: 25 February 2011, 05:23:47 pm »

i also bricked my guruplug
i don't have a linux comp here, what can i do?

You should be able to run a host from a live CD, eg Ubuntu or Knoppix.
Logged

sandoz

  • Newbie
  • *
  • Posts: 6
Re: Flashing U-Boot on Bricked Plug
« Reply #9 on: 26 February 2011, 07:43:59 pm »

same problems here:
running livecd now, jtag gets recognized coreectly on ttyUSB0

Code: [Select]
[  559.000282] usb 6-1: USB disconnect, address 2
[  599.306093] usb 6-1: new full speed USB device using uhci_hcd and address 3
[  599.507006] usb 6-1: New USB device found, idVendor=9e88, idProduct=9e8f
[  599.507011] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  599.507014] usb 6-1: Product: SheevaPlug JTAGKey FT2232D B
[  599.507017] usb 6-1: Manufacturer: FTDI
[  599.507019] usb 6-1: SerialNumber: FTT65G3W
[  603.832534] usbcore: registered new interface driver usbserial
[  603.832551] USB Serial support registered for generic
[  603.832802] usbcore: registered new interface driver usbserial_generic
[  603.832805] usbserial: USB Serial Driver core
[  603.876655] USB Serial support registered for FTDI USB Serial Device
[  603.877034] usb 6-1: Ignoring serial port reserved for JTAG
[  603.877063] ftdi_sio 6-1:1.1: FTDI USB Serial Device converter detected
[  603.877118] usb 6-1: Detected FT2232C
[  603.877120] usb 6-1: Number of endpoints 2
[  603.877122] usb 6-1: Endpoint 1 MaxPacketSize 64
[  603.877124] usb 6-1: Endpoint 2 MaxPacketSize 64
[  603.877134] usb 6-1: Setting MaxPacketSize 64
[  603.880164] usb 6-1: FTDI USB Serial Device converter now attached to ttyUSB0
[  603.880511] usbcore: registered new interface driver ftdi_sio
[  603.880513] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[  771.909778] usb 6-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
[  785.551654] usb 6-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1

but various combinations of timings still nothing:
i also tried changing 2000 kHz too 500khz
Code: [Select]
$ sudo ./runme.sh openocd/uboot.bin
 ****     Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M

BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS

$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Error: trying to validate configured JTAG chain anyway...
Error: unknown EmbeddedICE version (comms ctrl: 0x00000008)
Error: unexpected Feroceon EICE version signature
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: unexpected Feroceon EICE version signature
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
   
 ****   openocd FAILED
 ****   Is the mini USB cable connected?



what a i doing wrong
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 662
Re: Flashing U-Boot on Bricked Plug
« Reply #10 on: 27 February 2011, 09:00:39 am »

Code: [Select]
[  771.909778] usb 6-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
[  785.551654] usb 6-1: usbfs: interface 1 claimed by ftdi_sio while 'openocd' sets config #1
This is suspicious, are you using a distro that automatically attempts to mount usb filesystems,
if you are, disable it before plugging in the JTAG.
Code: [Select]
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Read this thread again from the beginning, this is the typical 'bad timing' error (caused by communication failure, so also check the connections).
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

Maenz

  • Newbie
  • *
  • Posts: 1
Re. Flashing U-Boot on Bricked Plug
« Reply #11 on: 21 March 2011, 07:06:35 pm »

Similar problem  :(:

I accidentally bricked a GuruPlug Standard in the process of updating the uboot through a directly connected USB on the plug. The USB mulfunctioned and the existing uboot on the plug was erased. The plug is now inaccessible!

I'm a Windows user with a JTAG. I use Putty, which opens up fine but the console is no longer active and the Marlvell>... prompt is therefore gone. The only light and sign of life on the plug is green. The network interface blinks when the plug is connected to a router, however, no visible IP for the plug. Do I have to buy and run Linux or Ubuntu to unbick the plug?

Thanks for any Hands-On-Tips on how-to in Windows!

/Maenz
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 662
Re: Flashing U-Boot on Bricked Plug
« Reply #12 on: 21 March 2011, 09:20:46 pm »

No you don't have to buy Linux, it's free  :D
You need OpenOCD, it is available for windows, but is a doddle to use on Linux as it is packaged as part of Guruplug-installer.tar.gz specifically set up for flashing the Guruplug.
Google OpenOCD and Guruplug-installer.tar.gz to see your options.

EDIT: Afterthought, it may be worth downloading Guruplug-installer.tar.gz just for the OpenOCD\Guruplug configuration files (if you can't find them nicely packaged for Windows that is).
« Last Edit: 21 March 2011, 09:26:08 pm by Confusticated »
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

tkteun

  • Newbie
  • *
  • Posts: 7
Re: Flashing U-Boot on Bricked Plug
« Reply #13 on: 15 December 2011, 11:03:47 pm »

I found the solution to this problem.

I've worked with openocd before and it's normal for the processor to be in another state than running to use ocd.

So what eventually works (fool proof) is to hold the reset button while invoking runme.sh.

Code: [Select]
****     Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 2 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1078). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1030). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1044). Workaround: increase "set remotetimeout" in GDB
wrote file openocd/uboot.bin to NAND flash 0 up to offset 0x0002c000 in 48.905407s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 2 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1029). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1012). Workaround: increase "set remotetimeout" in GDB
wrote file openocd/uboot-env.bin to NAND flash 0 up to offset 0x00060000 in 35.640572s
 **** U-boot should be up and running now. Open your console ...

Be sure to let go of the reset button fast because else your 'target state' won't be halted.
Logged

mabuhay

  • Newbie
  • *
  • Posts: 27
    • myownhomeserver.ch
Re: Flashing U-Boot on Bricked Plug
« Reply #14 on: 15 May 2012, 03:01:58 pm »

Digging out this old thread...

I am also one of those which bricked the GuruPlug  ::)

So far I tried everything I found online and here in order to flash the U-Boot again, but I just can't make it work.

It seems like I get the timing right (by keeping reset pressed, then starting the installer by pressing Enter and releasing the reset right after). Thats how it looks like when I use the Guruplug-Installer:
Code: [Select]
****     Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
   
 **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug


When the timing seems not to be ok, it looks like this (also mentioned in this thread that the timing might not be right if the JTAG device does not match):
Quote
****     Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0xfc0000e3 (Manufacturer: 0x071, Part: 0xc000, Version: 0xf)
Error: JTAG tap: feroceon.cpu             got: 0xfc0000e3 (mfg: 0x071, part: 0xc000, ver: 0xf)
Error: JTAG tap: feroceon.cpu expected 1 of 1: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Error: trying to validate configured JTAG chain anyway...
Error: unknown EmbeddedICE version (comms ctrl: 0x00000008)
Error: unexpected Feroceon EICE version signature
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:
   
 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

So now, what is going wrong? When I get the right timing with reset and Enter, it stops with the error
Quote
Error: timed out while waiting for target halted
Runtime error, file "./openocd/./board/guruplug.cfg", line 24:

What else could I try? When doing the procedure from this tread http://www.newit.co.uk/forum/index.php/topic,2835.0.html I get a similar output as nihilwolf mentioned in the first post of this thread.

I am lost...

EDIT:
hmm well... I guess I did not look well enough in this forum... here is the exact same question: https://www.newit.co.uk/forum/index.php/topic,1228.0.html
I guess the only solution is then to try and try and try...


EDIT 2:
For me it was the hardware, no timing or speed problems, JUST THE HARDWARE: https://www.newit.co.uk/forum/index.php/topic,3332.0.html

« Last Edit: 17 May 2012, 05:29:55 pm by mabuhay »
Logged
My low-power homeserver with the GuruPlug Server Plus: www.myownhomeserver.ch
Pages: [1] 2
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!