Welcome! Log In Create A New Profile

Advanced

my Pogoplug v4 dead after Nand flash

Posted by iptester 
my Pogoplug v4 dead after Nand flash
October 19, 2014 09:59AM
Hi all,
I bricked my seconde Pogo v4 ( I don't remember how that happen ) and my big problem is when I tried to revert back the stock firmware to mtd0 with serial/UART and tftp I did something wrong and now the pogoplug light wont turn on and I see no boot info on Putty with serial connexion ( just black screen) but at least I see the RJ45 light blinking ( but no ip adress on my router dhcp) and the cpu heat as normal, the last thing I did is :
tftpboot 0x800000 mtd0
nand erase 0x0 0x80000
nand write 0x800000 0x0 0x80000
then I hard rebooted the pogo and it wont come back, I think something happend to the nand flash.
note: I have another pogoplug v4 working on archlinux on a sata hdd .
Do you thing my pogoplug is dead or is there a chance to give it another life ?
Re: my Pogoplug v4 dead after Nand flash
October 19, 2014 03:47PM
There is hope!

You can unbrick the Pogo V4 with UART booting:

- Download the latest Pogo V4 u-boot and kwboot from this thread:
http://forum.doozan.com/read.php?3,12381

- Start kwboot on a different Linux box
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07.tld-1.pogo_v4.mtd0.kwb -p
- Power up the Pogo V4
- Within 1-2 seconds (but not too soon), Control-C to abort kwboot, and recall the command, execute kwboot again.
- Repeatedly recall the command and run kwboot until handshake successfully

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



Edited 1 time(s). Last edit at 10/19/2014 03:48PM by bodhi.
Re: my Pogoplug v4 dead after Nand flash
October 20, 2014 10:40PM
Hi Bodhi and thank you for your quick response.
Unfortunately it does'nt work for me after too many tries, here is my setup :
I use my working pogoplug v4 with arch on a sata hdd and I download your latest Pogo V4 u-boot and kwboot .
I SSH from Putty on Windows laptop.
[root@alarm kwboot-tool]# uname -s -r
Linux 3.1.10-33-ARCH
[root@alarm kwboot-tool]#  file `which kwboot`
/usr/bin/kwboot: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.27, BuildID[sha1]=eb43a5ac6cb667e8443b5bdcd60ac7f159260d2c, stripped

I use a profilic serial cable ( already tested on my working pogo).
[root@alarm kwboot-tool]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and here are my steps :
1 - I run the kwboot and it start spining slowly :
[root@alarm kwboot-tool]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target.../

2- I turn on my bircked pogo 4 and after 2-3-4-5 seconde nothing happen then I Ctrl+c
3- I turn off my bricked pogo 4

and I repeat the whole steps at least 15 times without result ( always Sending boot message. Please reboot the target.../ ) and somtimes I wait more than 2 minutes but nothing happen.
Re: my Pogoplug v4 dead after Nand flash
October 21, 2014 12:08AM
iptester,

Quote

> 3- I turn off my bricked pogo 4
This is wrong. Don't turn off the Pogo V4.

Here is the sequence again:

Run kwboot
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p

2- turn on the bricked Pogo v4 and after 1-2 seconds (nothing will happen).

3. Then Ctrl+C. Use the up arrow to recall the kwboot command, hit enter.

Keep doing step 3 as many times as you can until the handshake occurs. When the handshake occurs, kwboot will start sending the u-boot image. Eventually, you will see the u-boot banner. When the count down starts, hit any key to interrupt it. Unbricked!

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



Edited 1 time(s). Last edit at 10/21/2014 12:28AM by bodhi.
Re: my Pogoplug v4 dead after Nand flash
October 21, 2014 07:21PM
Hi,

ok, so I tried and tried more than 100 times and no handshake occurs.
may be I could try with a different kwboot version or a different pogo 4 u-boot ?
Re: my Pogoplug v4 dead after Nand flash
October 22, 2014 12:30AM
iptester Wrote:
-------------------------------------------------------
> Hi,
>
> ok, so I tried and tried more than 100 times and
> no handshake occurs.
> may be I could try with a different kwboot version
> or a different pogo 4 u-boot ?

Please post what you see when you attempt UART booting. Do you see any error message after you ctrl-C, up arrow, re-execute kwboot? If you can, post the log from the first kwboot command until about the 10th time.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: my Pogoplug v4 dead after Nand flash
October 22, 2014 11:03AM
I see no error msg and what I noticed is that once I run kwboot it start spining slowly (like one move every half second).
I believe you mean by log this :
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target.../^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...-^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...\^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...\^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target.../^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target.../^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...|^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...\^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...-^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target.../^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...-^C
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target.../^C

Re: my Pogoplug v4 dead after Nand flash
October 22, 2014 12:09PM
iptester,

Bad news! It did not even try to handshake. The 2nd and later execution should spit out error messages.

Check your serial connection, perhaps try it on the other Pogo V4 if you have that one's serial port header ready.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: my Pogoplug v4 dead after Nand flash
October 22, 2014 12:25PM
Alright bodhi,

I will keep trying, I have only 2 pogo v4 and I use my working one to run kwboot, I'm gonna run kwboot from a Ubuntu laptop on my working pogo v4 to test my serial cable and I will see If respond.

just a last question is there a JTAG possibility on pogo v4.

I thank you very much for your help,
Re: my Pogoplug v4 dead after Nand flash
October 22, 2014 04:52PM
iptester Wrote:
-------------------------------------------------------
> Alright bodhi,
>
> I will keep trying, I have only 2 pogo v4 and I
> use my working one to run kwboot, I'm gonna run
> kwboot from a Ubuntu laptop on my working pogo v4
> to test my serial cable and I will see If
> respond.
>
> just a last question is there a JTAG possibility
> on pogo v4.
>
> I thank you very much for your help,

Yes. I dont have the link, but recall some users here or at Arch site did get JTAG it working. Keep trying UART, though. I dont recall any one with PogoV4 has reported UART not working? (I could be wrong).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: my Pogoplug v4 dead after Nand flash
October 22, 2014 10:01PM
Quote
bodhi
Check your serial connection,
you are right . my serial soldering was bad and now it works, but what's next ?
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...|
Sending boot image...
  0 % [+++++++++++++++++xmodem: Bad message
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...|
Sending boot image...
  0 % [+++++++++++++++++xmodem: Bad message
[root@alarm doozan]# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  8 % [......................................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 13 % [......................................................................]
 15 % [......................................................................]
 17 % [......................................................................]
 18 % [......................................................................]
 20 % [......................................................................]
 22 % [......................................................................]
 23 % [......................................................................]
 25 % [......................................................................]
 27 % [......................................................................]
 29 % [......................................................................]
 30 % [......................................................................]
 32 % [......................................................................]
 34 % [......................................................................]
 35 % [......................................................................]
 37 % [......................................................................]
 39 % [......^C
[root@alarm doozan]#

then I tried this:
Quote
bodhi
2. Another thing worth to try is to create a Debian rootfs. Download my rootfs and extract it to a fresh USB (formatted with Ext3):
http://forum.doozan.com/read.php?2,12096

Boot with this Debian rootfs, and see how it goes.

and I plugged the USB on the bricked pogo and reboot it but still no light comes on.
I think I miss something cause I dont know how to gain access to the bricked pogo.
Re: my Pogoplug v4 dead after Nand flash
October 23, 2014 12:45AM
iptester,

Congrats! you have unbricked it. Wait ….

> 39 % [......^C
> [root@alarm doozan]#

Did it complete loading? did you enter the Control-C here ? I hope you did :)

Try again and let it boot until the u-boot banner appears and the countdown starts. Then interrupt the count down. At u-boot prompt, get the listing of the evironments:
printenv

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: my Pogoplug v4 dead after Nand flash
October 23, 2014 09:38AM
Voila chef :
Pogov4> printenv
arcNumber=3960
baudrate=115200
bootargs_root=root=/dev/mtdblock2 ro
bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) \
$(bootargs_root); bootm 0x800000
bootdelay=5
console=console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:05:ee:d9
if_netconsole=ping $serverip
ipaddr=192.168.1.98
machid=F78
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
preboot=run if_netconsole start_netconsole
serverip=192.168.1.99
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_rootfstype=ext3

Environment size: 694/131068 bytes
Pogov4> mmc rescan

MMC rescan: current device # 0 initialized OK
Pogov4> mtdparts
mtdids not defined, no default present

I agree it does not look as a good env but I dont want to set some bad thing and brike it again; I would like to boot Debian or Arch from an Sd card.



Edited 3 time(s). Last edit at 10/23/2014 02:37PM by iptester.
U-Boot default envs script
October 23, 2014 03:51PM
iptester,

Excellent! to set a good default envs set, you can either type them in one by one, or use my default envs script uboot.2014.07-tld-1.environment.scrip.

Dowload the attached script binary in this post and follow the instruction to execute it:
http://forum.doozan.com/read.php?3,18105,18124#msg-18124

And download the latest rootfs if you have not already done so, put it on either a USB drive or SD card and boot with it:
http://forum.doozan.com/read.php?2,12096

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: my Pogoplug v4 dead after Nand flash
October 24, 2014 02:36PM
Thank you very much bodhi, with your help my Pogo v4 is back to life and now I know very well how to unbrick it if that happen again.
I am very grateful.
:)
Seong O
Re: my Pogoplug v4 dead after Nand flash
October 19, 2016 08:46PM
Dear Bodhi,

As I got similar problem with my Pogo series V4, I connected with USB-serial and tried like above.

But I got result like next,

root@ubuntu:/home/tmp# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-1.pogo_v4.mtd0.kwb –p
Sending boot message. Please reboot the target...|
Sending boot image...
0 % [+++++++++++++++++xmodem: Bad message

Now, what should I do?
What would you recommend?

Sincerely Seong O
Re: my Pogoplug v4 dead after Nand flash
October 19, 2016 09:01PM
Seong O Wrote:
-------------------------------------------------------
> Dear Bodhi,
>
> As I got similar problem with my Pogo series V4, I
> connected with USB-serial and tried like above.
>
> But I got result like next,
>
> root@ubuntu:/home/tmp# ./kwboot -t -B 115200
> /dev/ttyUSB0 -b
> uboot.2016.05-tld-1.pogo_v4.mtd0.kwb –p
> Sending boot message. Please reboot the
> target...|
> Sending boot image...
> 0 % [+++++++++++++++++xmodem: Bad message
>
> Now, what should I do?
> What would you recommend?
>
> Sincerely Seong O

Seong,

This is a quirk with PogoV4. When you see that xmodem bad message, just use the up arrow to recall the kwboot command and execute it again. Repeat this several times, eventually the hanshake will occur.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Seong O
Re: my Pogoplug v4 dead after Nand flash
October 19, 2016 11:47PM
Thanks for this immediate reply!

I'll try more!

Thanks again.^^
Scales11
Re: my Pogoplug v4 dead after Nand flash
December 11, 2016 11:20AM
Just wanted to post a thank you, these steps worked for me too!

I struggled with this for a while only to realize that I had flipped the TX and RX lines.

:)
Re: my Pogoplug v4 dead after Nand flash
December 22, 2016 03:20AM
Hi Bodhi,

i have problem after revert back to original, currently i bricked my Pogo v4 (led no blinking, only lan led working).
I try with tis below steps:

root@test-VirtualBox:/home/test/pogo/kwboot-tool# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  ...
  99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0
Pogov4> mtdparts

device nand0 <orion_nand>, # parts = 5
 #: name                size            offset          mask_flags
 0: u-boot              0x00200000      0x00000000      0
 1: uImage              0x00300000      0x00200000      0
 2: uImage2             0x00300000      0x00500000      0
 3: failsafe            0x00800000      0x00800000      0
 4: root                0x07000000      0x01000000      0

active partition: nand0,2 - (uImage2) 0x00300000 @ 0x00500000

defaults:
mtdids  : none
mtdparts: none
Pogov4> usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Pogov4> ext2load usb 0:1 0x800000 /mtd0
2162688 bytes read in 151 ms (13.7 MiB/s)
Pogov4> nand erase 0x0 0x200000

NAND erase: device 0 offset 0x0, size 0x200000
Erasing at 0x1e0000 -- 100% complete.
OK
Pogov4> nand write 0x800000 0x0 0x200000

NAND write: device 0 offset 0x0, size 0x200000
 2097152 bytes written: OK
Pogov4> reset
resetting ...

and after this nothing happened, what i'm doing wrong ?
Re: my Pogoplug v4 dead after Nand flash
December 22, 2016 04:43PM
rafek Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> i have problem after revert back to original,
> currently i bricked my Pogo v4 (led no blinking,
> only lan led working).
> I try with tis below steps:
>
>
> root@test-VirtualBox:/home/test/pogo/kwboot-tool#
> ./kwboot -t -B 115200 /dev/ttyUSB0 -b
> uboot.2016.05-tld-1.pogo_v4.mtd0.kwb -p
> Sending boot message. Please reboot the
> target...\
> Sending boot image...
>   0 %
> [.................................................
> .....................]
>   ...
>   99 % [....................................]
> [Type Ctrl-\ + c to quit]
> 
> 
> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47
> -0700)
> Pogoplug V4
> 
> SoC:   Kirkwood 88F6192_A1
> DRAM:  128 MiB
> WARNING: Caches not enabled
> NAND:  128 MiB
> MMC:   kwsdio: 0
> *** Warning - bad CRC, using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> Hit any key to stop autoboot:  0
> Pogov4> mtdparts
> 
> device nand0 <orion_nand>, # parts = 5
>  #: name                size            offset    
>      mask_flags
>  0: u-boot              0x00200000      0x00000000
>      0
>  1: uImage              0x00300000      0x00200000
>      0
>  2: uImage2             0x00300000      0x00500000
>      0
>  3: failsafe            0x00800000      0x00800000
>      0
>  4: root                0x07000000      0x01000000
>      0
> 
> active partition: nand0,2 - (uImage2) 0x00300000 @
> 0x00500000
> 
> defaults:
> mtdids  : none
> mtdparts: none
> Pogov4> usb start
> starting USB...
> USB0:   USB EHCI 1.00
> scanning bus 0 for devices... 2 USB Device(s)
> found
>        scanning usb for storage devices... 1
> Storage Device(s) found
> Pogov4> ext2load usb 0:1 0x800000 /mtd0
> 2162688 bytes read in 151 ms (13.7 MiB/s)
> Pogov4> nand erase 0x0 0x200000
> 
> NAND erase: device 0 offset 0x0, size 0x200000
> Erasing at 0x1e0000 -- 100% complete.
> OK
> Pogov4> nand write 0x800000 0x0 0x200000
> 
> NAND write: device 0 offset 0x0, size 0x200000
>  2097152 bytes written: OK
> Pogov4> reset
> resetting ...
> 
> 
>
>
> and after this nothing happened, what i'm doing
> wrong ?

Possibly your mtd0 file is not good.

The easy way to recover is to boot in to Debian and fix it inside. Create the Debian 4.4 rootfs on USB following instruction in this thread:
http://forum.doozan.com/read.php?2,12096

Scroll down to section:
Quote

Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.


and boot into Debian, examine the mtd0 (if you really want to go back to stock). It might have not been saved correctly.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: my Pogoplug v4 dead after Nand flash
December 22, 2016 05:30PM
Dear bodhi,

thank You for reply.
I use mtd0 file from this post http://forum.doozan.com/read.php?3,16789,16789#msg-16789 and link http://bit.ly/189BnB6.
I would actually restore the Pogo to action (not necessary to original),
I very much appreciate your commitment and I will be very grateful for any clues.
Re: my Pogoplug v4 dead after Nand flash
December 22, 2016 06:48PM
rafek,

> I would actually restore the Pogo to action (not
> necessary to original),

Ok then you should be able to boot the Debian 4.4 rootfs. After you've create it on USB, come back for instruction further about how to adjust u-boot envs to boot it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: my Pogoplug v4 dead after Nand flash
December 23, 2016 03:52AM
I prepared SD card (set fs as ext3) with commands:

root@test-VirtualBox:~# mount /dev/sdb1 /media/sdb1
root@test-VirtualBox:~# cd /media/sdb1/
root@test-VirtualBox:/media/sdb1# tar -xjf /home/test/pogo/Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@test-VirtualBox:/home/test/pogo/2# cd /media/sdb1/boot
root@test-VirtualBox:/media/sdb1/boot# cp -a zImage-4.4.0-kirkwood-tld-1  zImage.fdt
root@test-VirtualBox:/media/sdb1/boot# cat dts/kirkwood-pogoplug_v4.dtb >> zImage.fdt
root@test-VirtualBox:/media/sdb1/boot# mv uImage uImage.orig
root@test-VirtualBox:/media/sdb1/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt  uImage
Image Name:   Linux-4.4.0-kirkwood-tld-1
Created:      Fri Dec 23 10:45:17 2016
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3165078 Bytes = 3090.90 kB = 3.02 MB
Load Address: 00008000
Entry Point:  00008000
root@test-VirtualBox:/media/sdb1/boot# sync
root@test-VirtualBox:/media/sdb1/boot# sync

what should be bext ?
Re: my Pogoplug v4 dead after Nand flash
December 23, 2016 05:14AM
rafek,

Since you kwboot with the new u-boot:
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
*** Warning - bad CRC, using default environment

This CRC error meant u-boot will use the internal envs. And the internal envs are set up to boot with USB by default. That's why I said above
The easy way to recover is to boot in to Debian and fix it inside. Create the Debian 4.4 rootfs on USB following instruction in this thread: 
http://forum.doozan.com/read.php?2,12096

If you do exactly as you did above, using USB flash drive, then you can boot the box with kwboot all the way into Debian.

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



Edited 1 time(s). Last edit at 12/23/2016 05:16AM by bodhi.
Re: my Pogoplug v4 dead after Nand flash
December 23, 2016 08:10AM
I try recovery but now i can boot only with kwboot and get this output:

root@test-VirtualBox:/home/test/pogo/kwboot-tool# ./kwboot -t -B 115200 /dev/ttyUSB5 -b uboot.2016.05-tld-1.pogo_v4.mtd0.kwb -p
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  ...
 99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0
*** ERROR: `ethaddr' not set
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Pogov4>

Re: my Pogoplug v4 dead after Nand flash
December 23, 2016 09:55AM
I load original mtd0 and now i can run Pogo from USB, but only when i load kwboot (through serial console). When i reboot Pogo nothing happened. Please look at log.
Attachments:
open | download - putty_pogo.txt (28.9 KB)
Re: my Pogoplug v4 dead after Nand flash
December 24, 2016 02:39AM
rafek Wrote:
-------------------------------------------------------
> I load original mtd0 and now i can run Pogo from
> USB, but only when i load kwboot (through serial
> console). When i reboot Pogo nothing happened.
> Please look at log.

Your log showed you've successfully booted into Debian using kwboot. The next step is to install the new u-boot, and keep this Debian 4.4 rootfs as your system.

kwboot only loads the new u-boot image into RAM to run it. You have to install it to NAND to keep it permanently.

Afer you installed new u-boot, and before rebooting. Look at uImage that you have appended DTB to. New u-boot default envs load the DTB separately. So you will need to restore the uImage that you have saved previously:
cd /boot
mv uImage.orig uImage

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



Edited 1 time(s). Last edit at 12/24/2016 02:44AM by bodhi.
Re: my Pogoplug v4 dead after Nand flash
December 24, 2016 03:30PM
You made my day :)
Currently i have working Pogo with booting from USB, last thing is moving OS to SD card.
Is any chance for fast path for this ?
Re: my Pogoplug v4 dead after Nand flash
December 24, 2016 03:48PM
rafek Wrote:
-------------------------------------------------------
> You made my day :)
> Currently i have working Pogo with booting from
> USB, last thing is moving OS to SD card.
> Is any chance for fast path for this ?

Shutdown, bring the USB drive to another Linux box, log in as root (sudo won't work). Format the SD card exactly as you did for the USB drive (single Ext3 or Ext4 partition, label rootfs).

cd /media/SD
time cp -aR /media/USB/* . 
sync

Now SD card will boot automatically (no change in u-boot envs needed).

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

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: