How to ressurect bricked Sheeva after flashing uboot

Discussion about U-Boot and the kernel.

How to ressurect bricked Sheeva after flashing uboot

Postby Ocye » Fri Nov 13, 2015 10:14 pm

After flashing a newer u-boot my Sheeva has become very quiet.

$this->bbcode_second_pass_code('', 'usb start
ext2load usb 0:1 0x0800000 u-boot.kwb
nand erase 0x0 0x60000
nand write 0x0800000 0x0 0x60000
')
u-boot.kwb is from https://people.debian.org/~tbm/u-boot/2 ... heevaplug/

Now I don't get any response

$this->bbcode_second_pass_code('', 'sudo cu -s 115200 -l /dev/ttyUSB0
Connected.
')
This remains uninterruptable (ctrl+c) until sheeva is powered off.

Next idea was to use openocd, compiled freshly from git

$this->bbcode_second_pass_code('', '../src/openocd -f board/sheevaplug.cfg
Open On-Chip Debugger 0.10.0-dev-00107-ge4848fe (2015-11-13-22:57)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
adapter speed: 2000 kHz
dcc downloads are enabled
Warn : use 'feroceon.cpu' as target identifier, not '0'
sheevaplug_load_uboot
adapter speed: 100 kHz
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: no device found
Error: unable to open ftdi device with vid 9e88, pid 9e8f, description 'SheevaPlug JTAGKey FT2232D B' and serial '*'
')
Adding the parameter -c "adapter_khz 100" has no effect.

The device is still recognized
$this->bbcode_second_pass_code('', 'lsusb
...
Bus 002 Device 013: ID 9e88:9e8f Marvell Semiconductor, Inc. Plug Computer Basic [SheevaPlug]')

Any idea what to do now?
Ocye
 
Posts: 7
Joined: Sun Nov 08, 2015 12:06 am

Re: How to ressurect bricked Sheeva after flashing uboot

Postby summers » Sun Nov 15, 2015 11:41 am

On the sheva, can you connect to the UART? Thats where you'll see the first output, e.g.from uboot.

If sheeva has just been updated to new uboot (like nsa325), then need to find out how the new uboot has been configured. What the new uboot for nsa325 does - and probably all kirkwood devices, is look in /boot/uEnv.txt for variables to set in uboot. So for the nsa325 needed to make sure it pointed to the new root device "root=PARTUUID=94a2dc27-01" (for me - you would need to change your device).

Of course this all assumed you can acess the file system on the device.
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: How to ressurect bricked Sheeva after flashing uboot

Postby Ocye » Sun Nov 15, 2015 11:54 am

As I wrote, serial connection returns "connected" but nothing more. After this it hangs completely.
Ocye
 
Posts: 7
Joined: Sun Nov 08, 2015 12:06 am

Re: How to ressurect bricked Sheeva after flashing uboot

Postby summers » Mon Nov 16, 2015 6:46 pm

Eik nothing from the uart - then that means you've gone beyond the limit of where I have been. Means that uboot isn't showning almost any sign of life (at least thats how I read it).

Yes mean JTAG is next port of call, which explain you using openocd. Alas I've never had to use JTAG myself, it should enable you to rewrite the flash - but yes help from someone with experience here helps. JTAG is fairly low level as much as I know, so if you JTAG into the propocessor, you'll need to bring up the processor enough to be able to talk to the flash.

So sorry, not much I can say to help ...
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm


Return to U-Boot/Kernel

Who is online

Users browsing this forum: No registered users and 7 guests