Welcome! Log In Create A New Profile

Advanced

bricked iconnect

Posted by vinix 
bricked iconnect
October 03, 2016 05:55AM
Hello all,
I did read the manual of how to upgrade the UBoot from bodhi: 2016.05 U-Boot Kirkwood.
What i did not realized was the (B) section (shame on me!) and as of this i reboot the iconnect, without
flashing the env to 0xC0000.


The result is this:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:38:04 -0700)
Iomega iConnect

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 512 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 362496 7469056 a536a0ea-01 83
2 8192 354304 a536a0ea-02 82
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
2631368 bytes read in 363 ms (6.9 MiB/s)
** File not found /boot/uInitrd **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2-iconnect
Created: 2012-04-15 12:37:51 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2631304 Bytes = 2.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Then the iconnect just do nothing..... and the serial console won't react on keystroke.
----------

My question is now, how do i use UBoot on serial console to fix it?
The 3 Files of the default enviroment for the new UBoot I got here, as well as the old env (c).

could anyone point me in the right direction please
thank you

english is not my native language, so a lot of edits... sorry



Edited 3 time(s). Last edit at 10/03/2016 06:05AM by vinix.
Re: bricked iconnect
October 03, 2016 02:48PM
Vinix,

Do this to recover:

http://forum.doozan.com/read.php?3,30438,30439#msg-30439

The procedure above is for the Pogo E02. For iConnect you need to adjust the env for the DTB file to use iConnect DTB. Since you have serial console, You can also adjust it at serial console prompt during boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: bricked iconnect
October 03, 2016 04:14PM
Hello bodhi,
Thank you for your help, it works now!
I created a new stick with ext3 and copy over the latest debian kernel and fs.
Then I copyed the uEnv.txt as you advised.

After a reboot it worked like new.

Thank you also for all the support and work over the time!
I use also 2 dockstars and another iconnect as well as some raspis.
Unbricked allready a lot of dockstars with openocd via jtag.
Without your work (and Jeff's) and the will to share it, it would not happend.

Normaly I just read here (since many Years) but my problem forced me to get registerd and ask.

Vinix from germany
Re: bricked iconnect
October 03, 2016 06:38PM
> After a reboot it worked like new.
>
Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: