Latest posts of: Griffo

Show Posts
Pages: [1]

1	Hardware and U-Boot firmware / U-Boot stuff / Re: Another bricked Guruplug, uboot not loading...no serial output	on: January 31, 2012, 03:12:35 PM
I'm not sure if it will help diagnose the fault or not, but this is the output I receive when the guruplug-installer fails: Code: root@BGLaptop:/home/brad/Desktop/guruplug-installer# ./runme.sh ./openocd/uboot.bin cp: `./openocd/uboot.bin' and `openocd/uboot.bin' are the same file ** 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

2	Hardware and U-Boot firmware / U-Boot stuff / Re: Another bricked Guruplug, uboot not loading...no serial output	on: January 31, 2012, 04:27:21 AM
I had been trying to successfully rerun the guruplug installer countless times and it's finally worked again but still no serial output Code: root@BGLaptop:/home/brad/Desktop/guruplug-installer# ./runme.sh ./openocd/uboot.bin cp: `./openocd/uboot.bin' and `openocd/uboot.bin' are the same file ** 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 Warn : DBGACK set while target was in unknown state. Reset or initialize target. target state: halted target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff014c MMU: disabled, D-Cache: disabled, I-Cache: disabled 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' wrote file openocd/uboot.bin to NAND flash 0 up to offset 0x0005a000 in 56.562771s 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' wrote file openocd/uboot-env.bin to NAND flash 0 up to offset 0x00060000 in 20.127605s ** U-boot should be up and running now. Open your console ... root@BGLaptop:/home/brad/Desktop/guruplug-installer#

3	Hardware and U-Boot firmware / U-Boot stuff / Another bricked Guruplug, uboot not loading...no serial output	on: January 31, 2012, 04:10:37 AM
G'day Everyone, I've just received my new Guruplug Server from Globalscale and I've already bricked it. I also ordered and received the JTAG as I was worried I might do this. I attempted to upgrade uboot using the guruplug-installer. Everything seemed to go well until the Guruplug restarted, now it looks like Uboot doesn't load as I get no output on the serial connection. I still see /dev/ttyUSB0 and when I create the serial session I see the LEDs light up when I type but nothing from the Guruplug itself. Before this all happened, I was happily connected to the Guruplug via the JTAG in a serial session... I've spent a couple of hours now trying many different things that I found on the web including: - re-running runme.sh straight after powering on the Guruplug - Looping the runme.sh (I'd provide the link to this but I can't seem to find it now) - Disconnecting and reconnecting everything - Installing the distro's openocd (Debian Squeeze) I look forward to everyone's suggestions Cheers, Griffo

Pages: [1]