U-Boot upgrade part complete, no console (eeek!)

[brettski]

Greetings fellow Pluggers! First post for me, inauspicious as it may be...

I got my sheevaplug yesterday, installed the FTDI drivers on my win7 box today and started working my way through the u-boot upgrade process (plugpbx.org>getting started>install guide)

Note: I left an empty 2GB Fat32 microSD card (with adaptor) in the SD slot, which I put in there when I unboxed yesterday. Would this have effected u-boot upgrade? 

I loaded the new u-boot image from a 4GB Fat32 format usb stick (3.4.19 image downloaded from here and renamed to 'u-boot.kwb'). Following the instructions, I did 'usb start', then 'fatload.....u-boot.kwb' and saw it load, then I've done the nand erase, nand write, and restart. That's the last time I saw the console.

So have I bricked it? (I'm guessing I have, but hoping I'm missing something simple)

Thanks, appreciate your help and the great project!

[PlugPBX Admin]

Greetings fellow Pluggers! First post for me, inauspicious as it may be...

I got my sheevaplug yesterday, installed the FTDI drivers on my win7 box today and started working my way through the u-boot upgrade process (plugpbx.org>getting started>install guide)

Note: I left an empty 2GB Fat32 microSD card (with adaptor) in the SD slot, which I put in there when I unboxed yesterday. Would this have effected u-boot upgrade? 

I loaded the new u-boot image from a 4GB Fat32 format usb stick (3.4.19 image downloaded from here and renamed to 'u-boot.kwb'). Following the instructions, I did 'usb start', then 'fatload.....u-boot.kwb' and saw it load, then I've done the nand erase, nand write, and restart. That's the last time I saw the console.

So have I bricked it? (I'm guessing I have, but hoping I'm missing something simple)

Thanks, appreciate your help and the great project!

Not to worry, you can debrick even a bad boot loader flash. Google it!  ...I know if you head over to the plugcomputer.org wiki they have a section on debricking and an app you can download which does the debricking for you.

Remember the USB interface both provides a JTAG interface (great for debricking) and a serial terminal - I know plenty who've debricked.

That being said, TFTP is a less error prone uboot flashing path, instead of using USB or SD card media - perhaps try following my video guide on flashing with TFTP instead as posted on the site? (YouTube Video)

You'll have this fixed in no time!

[brettski]

Ok, I've tried following the debricking instructions on a couple of separate occasions and still going nowhere fast.

These are the instructions I'm following: http://plugcomputer.org/plugforum/index.php?topic=3680.0 which are the most comprehensive step-by-step I could find.

More info: I get a power LED but no blue LED (boot rom). I'm using Win7 32bit. I get all the way through the debricking instructions to the "runme nand" at command line, and the script chugs away happily until it reaches openocd. It throws the status_access_violation, does a stack dump and quits.

Will keep plugging (haha!) away at this unbricking and post back with results. Square one, here I come!

[brettski]

Okay... I've given up on Win 7 path... didn't feel like I was getting anywhere, so over on Ubuntu 11.10 now and making tentative progress...

Installed the FTDI drivers and OpenOCD via Ubuntu Software Centre, and used apt-git for some of the supporting files like libusb, ftdi_eeprom and libconfuse. Not sure if I've installed just the packages I need, but I'm following at least two sets of instructions, cause everything I can find about debricking is either out of date or has multiple methods to use. Rather frustrating. Admittedly, my linux prowess is increasing... almost rank n00b.

I think I haven't bricked the SheevaPlug, cause the more I learn about it, the more I see it's built to withstand screw-ups like flashing the wrongly named boot image . JTAG provides latitude for fixing things deep down.

Getting to the question, since I'm getting stuck on openocd. I've got uboot.bin in openocd's directory, along with the sheevaplug.cfg file (have tried the original and Evan Black's updated version on pastebin). I navigate a terminal to sheevaplug-installer-v1.0/uboot/openocd directory containing the sheevaplug.cfg file, but when I run;
$ openocd -f sheevaplug.cfg -c init -c sheevaplug_reflash_uboot -c exit

I'm getting the following output:
brett@eeeBox:~/sheevaplug-installer-v1.0/uboot/openocd/config$ openocd -f sheevaplug.cfg -c init -c sheevaplug_reflash_uboot -c exit
Open On-Chip Debugger 0.5.0 (2011-08-26-10:27)
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
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
  feroceon.cpu mww address data [count]
mww ['phys'] address value [count]
Runtime Error: sheevaplug.cfg:34:
in procedure 'sheevaplug_reflash_uboot'
in procedure 'sheevaplug_init' called at file "sheevaplug.cfg", line 106
in procedure 'mww' called at file "sheevaplug.cfg", line 34

Any ideas on what I'm doing wrong?

[PlugPBX Admin]

Myself, I've never bricked a device.

I've had friends brick theirs. And they've brought it back without any issues, saying the tool was easy to use. I know they either used Windows XP, or linux as the platform to run the tools from.

My suggestion is this. Post this over on the plugcomputer.org forums.

Here we are focused on PlugPBX, whatever that is - but when you start to focus 100% on just sheevaplug stuff, go search/post in those forums as they are tightly focused on just this subject  matter. Make sure you also look over the wiki pages at plugcomputer.org as I am sure they have one or several pages dedicated to JTAG debricking... Don't give up, keep googling, keep searching. I just cant comment from my own experience here, or I would.