Welcome! Log In Create A New Profile

Advanced

usb key not recognized on pogo E02

Posted by ringprince 
Forum List Message List New Topic
ringprince
usb key not recognized on pogo E02
March 10, 2019 10:44PM
Hi all,

I've run debian on my pogo E02 successfully sereval years. Now, my USB key died. I thus prepared a new and bigger key with the newest rootfs I found. Problem is, the pogo E02 does not like the usb key. Here is the output of the netconsole: 

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700)
Pogo E02
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=3", size 91 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 727, bad PEBs: 1, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 704, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
Error reading superblock on volume 'rootfs' errno=-22!
ubifsmount - mount UBIFS volume


Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
1 bytes read in 253 ms (0 Bytes/s)
Found bootable drive on usb 0:1
3832036 bytes read in 410 ms (8.9 MiB/s)
EHCI timed out on TD - token=0x4e008d80
EHCI timed out on TD - token=0x4e008d80
EHCI timed out on TD - token=0x4e008d80
 ** ext4fs_devread read error - block
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2019-03-10   9:13:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3831972 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK


Starting kernel ...

Your help is highly appreciated.

Best,
Andreas
Reply Quote
alexr
Re: usb key not recognized on pogo E02
March 10, 2019 11:53PM
I've found some usb keys just aren't compatible. Mostly Kingston brand usb keys. I've had no issue with Sandisk branded ones.
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
March 11, 2019 01:17AM
ringprince Wrote:
-------------------------------------------------------
> Hi all,
>
> I've run debian on my pogo E02 successfully
> sereval years. Now, my USB key died. I thus
> prepared a new and bigger key with the newest
> rootfs I found. Problem is, the pogo E02 does not
> like the usb key. Here is the output of the
> netconsole:
>
> 
> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43
> -0700)
> Pogo E02
> gcc (Debian 4.9.2-10) 4.9.2
> GNU ld (GNU Binutils for Debian) 2.25
> Hit any key to stop autoboot:  0
> starting USB...
> USB0:   USB EHCI 1.00
> scanning bus 0 for devices... 3 USB Device(s)
> found
>        scanning usb for storage devices... 1
> Storage Device(s) found
> ** File not found /rescueme **
> ** Unrecognized filesystem type **
> ubi0: attaching mtd1
> ubi0: scanning is finished
> ubi0: attached mtd1 (name "mtd=3", size 91 MiB)
> ubi0: PEB size: 131072 bytes (128 KiB), LEB size:
> 129024 bytes
> ubi0: min./max. I/O unit sizes: 2048/2048,
> sub-page size 512
> ubi0: VID header offset: 512 (aligned 512), data
> offset: 2048
> ubi0: good PEBs: 727, bad PEBs: 1, corrupted PEBs:
> 0
> ubi0: user volume: 0, internal volumes: 1, max.
> volumes count: 128
> ubi0: max/mean erase counter: 1/1, WL threshold:
> 4096, image sequence number: 0
> ubi0: available PEBs: 704, total reserved PEBs:
> 23, PEBs reserved for bad PEB handling: 19
> Error reading superblock on volume 'rootfs'
> errno=-22!
> ubifsmount - mount UBIFS volume
> 
> 
> Usage:
> ubifsmount <volume-name>
>     - mount 'volume-name' volume
> 1 bytes read in 253 ms (0 Bytes/s)
> Found bootable drive on usb 0:1
> 3832036 bytes read in 410 ms (8.9 MiB/s)
> EHCI timed out on TD - token=0x4e008d80
> EHCI timed out on TD - token=0x4e008d80
> EHCI timed out on TD - token=0x4e008d80
>  ** ext4fs_devread read error - block
> ## Booting kernel from Legacy Image at 00800000
> ...
>    Image Name:   Linux-4.12.1-kirkwood-tld-1
>    Created:      2019-03-10   9:13:58 UTC
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    3831972 Bytes = 3.7 MiB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> 
> 
> Starting kernel ...
>
>
> Your help is highly appreciated.
>
> Best,
> Andreas

Power up, Interrupt netconsole at countdown, and 

printenv
usb start

Please post the entire log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
ringprince
Re: usb key not recognized on pogo E02
March 11, 2019 02:55PM
Thanks for the fast replies!

Here are the logs: 

PogoE02> printenv

printenv
arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:53:0E
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
if_netconsole=ping $serverip
ipaddr=192.168.178.27
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.178.29
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.178.29
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2780/131068 bytes


PogoE02> usb start

usb USB0:   start
starting USB...
USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
March 11, 2019 05:24PM
It looks OK.

So now the problem is with the

Quote

EHCI timed out on TD

Like alexr mentioned above. This problem is most likely the type of the USB flash drive that was not handled well by u-boot. We have seen this for many many years here. If you switch to (my favorite brand) Sandisk, it is very likely it will show no error like this.

However, I've incorporated a permanent fix for this using rayv patch in the later version. So if you can get pass this error with a different USB flash drive, then you can update u-boot, and then mos likely it will accept most of USB flash brands.

https://forum.doozan.com/read.php?3,12381

Quote

Last Updated 28 Oct 2017
Updated 06 Dec 2017 (replace Sheevaplug with newer version 2017.07-tld-2)

I've uploaded 2017.07-tld-1 U-Boot images for Pogo E02, GoFlexNet, GoFlex Home, Dockstar, Pogo V4/Mobile, iConnect, Netgear Stora, Sheevaplug, NSA320, NSA325, NSA310S/320S, NSA310, HP-T5325, and Dreamplug.

The HP Thin Client T5325 installation procedure is different from other Kirkwood u-boots, see this thread for installation instruction and download link..

The Marvell Dreamplug box installation procedure is different from other Kirkwood u-boots, see this thread for installation instruction and download link.

New/updated in 2017.07-tld-1 version:

- Rebase u-boot code to track mainline 2017.07.
- Incorporated patch to fix "EHCI timed out on TD" error with USB drives.
- SD cards: Use the mainline version of MMC driver for Pogo V4/Mobile and Sheevaplug
- Improve internal defautl envs.
- Fixed Sheevaplug "load" command in 2017.07-tld-2 version.

Credits:
-Thanks rayvt for the EHCI timed out on TD patch ! good works.
- Thanks Rayknight for reporting bug and testing the Sheevaplug 2017.07-tld-2 u-boot .

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
ringprince
Re: usb key not recognized on pogo E02
May 04, 2019 02:13PM
I've tried 4 different USB-Keys until the last one now seems to work. Below [1] is the output from the netconsole. So, thanks for your help!

But I am now encountering a different issue. As soon the 'Starting kernel ...' message appears, the pogo disappears from my network. I do not see it in the GUI of the router, I am not able to discover via any network app: 


# ping 192.168.178.27
PING 192.168.178.27 (192.168.178.27) 56(84) bytes of data.
64 bytes from 192.168.178.27: icmp_seq=1 ttl=64 time=2.03 ms
64 bytes from 192.168.178.27: icmp_seq=2 ttl=64 time=1.89 ms
64 bytes from 192.168.178.27: icmp_seq=3 ttl=64 time=11.6 ms
64 bytes from 192.168.178.27: icmp_seq=4 ttl=64 time=8.57 ms
64 bytes from 192.168.178.27: icmp_seq=5 ttl=64 time=7.61 ms
64 bytes from 192.168.178.27: icmp_seq=6 ttl=64 time=6.97 ms
64 bytes from 192.168.178.27: icmp_seq=7 ttl=64 time=4.56 ms
64 bytes from 192.168.178.27: icmp_seq=8 ttl=64 time=3.79 ms
64 bytes from 192.168.178.27: icmp_seq=9 ttl=64 time=2007 ms
64 bytes from 192.168.178.27: icmp_seq=10 ttl=64 time=989 ms
64 bytes from 192.168.178.27: icmp_seq=11 ttl=64 time=297 ms
From 192.168.178.29 icmp_seq=34 Destination Host Unreachable
From 192.168.178.29 icmp_seq=35 Destination Host Unreachable
From 192.168.178.29 icmp_seq=36 Destination Host Unreachable
From 192.168.178.29 icmp_seq=37 Destination Host Unreachable
From 192.168.178.29 icmp_seq=38 Destination Host Unreachable
From 192.168.178.29 icmp_seq=39 Destination Host Unreachable
From 192.168.178.29 icmp_seq=40 Destination Host Unreachable
From 192.168.178.29 icmp_seq=41 Destination Host Unreachable
From 192.168.178.29 icmp_seq=42 Destination Host Unreachable



Any help on how to debug this would be highly appreciated!

Best,
Andreas



[1] 

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700)
Pogo E02                                                 
gcc (Debian 4.9.2-10) 4.9.2                     
GNU ld (GNU Binutils for Debian) 2.25    
Hit any key to stop autoboot:  0                          
starting USB...                         
USB0:   USB EHCI 1.00    
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=3", size 91 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 727, bad PEBs: 1, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 704, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
Error reading superblock on volume 'rootfs' errno=-22!
ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
1 bytes read in 308 ms (0 Bytes/s)
Found bootable drive on usb 0:1
3832036 bytes read in 547 ms (6.7 MiB/s)
7245696 bytes read in 660 ms (10.5 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Created:      2019-05-01   9:21:06 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3831972 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...



Edited 1 time(s). Last edit at 05/04/2019 02:43PM by ringprince.
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
May 04, 2019 05:30PM
Andreas,


Looks like your rootfs was not prepared correctly. Redo it using the Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 tarball, following the instruction in the release thread. And don't do Step 4. Basically, you just need to extract it and use it as is.

Quote

Updated 24 Jul 2017:

Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:

- tarball size: 188M
- install size: 488M
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

md5:
bf3d29569943875df348fb5ca03b348c
sha256:
4ed5714fdb123cdb40e973f3d0754e91cd199b75a9874018f2b5dc9cfa8ae8bb

And remember to check the hash of what you download, as always.

Installation:

Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too).

Note: all steps below must be done while logging in as root user (not sudo). If you are not the root user then don't continue, because the rootfs will not work.

1. Format a new USB drive with a single Ext3 partition, and label it rootfs. If you are running the latest U-Boot for Kirkwood then you can use Ext4.

2. Mount the drive on a Linux box. cd to top level directory and extract it. It is assuming the USB drive is mounted at /media/sdb1
cd /media/sdb1
tar -xjf Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

3. Adjust fstab (optional).

Edit /media/sdb1/etc/fstab entry for root device to match the rootfstype of your rootfstype if you use Ext4 or Ext2. However, you can keep it as is without problem in booting since the kernel will figure out which file system the rootfs was formatted.

LABEL=rootfs / ext3 noatime,errors=remount-ro 0 1

4.

Not needed.

5. Done. Take this USB rootfs to your plug and cold start. After booted into Debian, see Note1 and Note2 below. It is very important that you do Note1 steps to secure your box.


Plug in the USB rootfs, Start netconsole on the other box.

Power up, interrupt the countdown 
Hit any key to stop autoboot:  0

And 

printenv
boot

Please post the entire netconsole log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
ringprince
Re: usb key not recognized on pogo E02
May 05, 2019 12:04AM
Hi bodhi,

Thanks for keep on helping!

I have re-prepared the USB-Key without step 4 (which I had done previously). But this does not seem to help.

Here is the log: 

arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:53:0E
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
if_netconsole=ping $serverip
ipaddr=192.168.178.27
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.178.29
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.178.29
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2780/131068 bytes



PogoE02> boot                            
boot                                                      
starting USB...                         
USB0:   USB EHCI 1.00    
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=3", size 91 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 727, bad PEBs: 1, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 704, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
Error reading superblock on volume 'rootfs' errno=-22!
ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
1 bytes read in 258 ms (0 Bytes/s)
Found bootable drive on usb 0:1
3821592 bytes read in 507 ms (7.2 MiB/s)
7245696 bytes read in 661 ms (10.5 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2017-07-20   8:11:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3821528 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

- Andreas
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
May 05, 2019 12:37AM
Andreas,

The problem is easy. You are running new u-boot 
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700)
Pogo E02
But your envs are much older (looks like 2012 version).

The default envs image was not installed during the time you installed new u-boot.

Let me point you to a post that will load the default envs in a script and that will get you boot to Debian.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
May 05, 2019 01:51AM
Andreas,

To load the default envs for U-Boot 2016.05-tld-1, see this instruction:

https://forum.doozan.com/read.php?3,29362,29390#msg-29390

Basically just put that script uboot.2016.05-tld-1.environment.scr on your USB rootfs /boot folder and run the script loading commands at u-boot promtp.

Note that the DTB name is different. Yours is Pogo E02, so the dtb_file should be set to: 

setenv dtb_file '/boot/dts/kirkwood-pogo_e02.dtb'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
ringprince
Re: usb key not recognized on pogo E02
May 05, 2019 11:24PM
Thanks. This does not seem to work for me, though. Running the script does not seem to function and does not seem to have any effect. And it apparently disconnect from the netconsole?


Here is the output: 



U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700)
Pogo E02
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:   8
 0
PogoE02>
PogoE02> usb start
starting USB...
USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
PogoE02> ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
3232 bytes read in 284 ms (10.7 KiB/s)
PogoE02> source 0x800000
sou## Executing script at 00800000
rce 0x80000

I do not see any progress at that point. So, after a while (~5min) I restarted the pogo device. If I repeat these steps, I end up at the same situation.

Is my download of the script corrupt?

Regards,
Andreas
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
May 06, 2019 12:12AM
Andreas,

Ah! I forgot that you only have netconsole.

The reason netconsole was disconected because the default settings are for serial connection. So some netconsole-related envs were reset to serial when you run the script. And u-boot is still running, but you've lost the TCP connection.

I will post an alternative solution.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
May 06, 2019 12:53AM
Andreas,

Here is the new instruction:

https://forum.doozan.com/read.php?3,83124


I thought it's worthwhile to make it a howto post so I can add the Wiki thread later. You are the tester for this instruction :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
ringprince
Re: usb key not recognized on pogo E02
May 06, 2019 09:51PM
Hi bodhi,

Thanks a lot. This worked fine for me.

One last issue: This version of uboot shoud have accepted a wide range of USB-keys, correct?

So, I have probably screwed somewhere while preparing them?

So, some follow-up questions in this regard:
- Does the partition table have to be MSDOS?
- Should that work with 'proper' USB drives, too?
- What are other potential pit-falls?

Best,
Andreas
Reply Quote
ringprince
Re: usb key not recognized on pogo E02
May 06, 2019 10:19PM
Another follow up.

I see two warnings: 

Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

These seem to not affect functionality, though.

Here is the complete log: 

PogoE02> usb start
usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
PogoE02> ext2load usb 0:1 0x810000 /boot/uEnv.txt
ext2load usb 0:1 0x810000 /boot/uEnv.txt
2662 bytes read in 284 ms (8.8 KiB/s)
PogoE02> env import -t 0x810000 $filesize
env import -t 0x810000 $filesize
PogoE02> printenv
printenv
arcNumber=2097
baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_
uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=00:25:31:00:53:0E
fileaddr=810000
filesize=a66
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
if_netconsole=ping $serverip
ipaddr=192.168.178.27
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=0x831
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.178.29
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run preboot_nc
preboot_nc=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan
_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.178.29
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_ready_retry=15
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 4811/131068 bytes

PogoE02> boot
boot
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

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

Part    Start Sector    Num Sectors     UUID            Type
  1     512             61068800        aaca89db-01     0b
loading envs from usb 0 ...
2662 bytes read in 279 ms (8.8 KiB/s)
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
importing envs ...
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 252 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3821592 bytes read in 643 ms (5.7 MiB/s)
loading uInitrd ...
7245696 bytes read in 769 ms (9 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
10444 bytes read in 1264 ms (7.8 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2017-07-20   8:11:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3821528 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000


Starting kernel ...
Reply Quote
bodhi
Re: usb key not recognized on pogo E02
May 06, 2019 11:10PM
Andreas,

> Thanks a lot. This worked fine for me.

Cool!

>
> One last issue: This version of uboot shoud have
> accepted a wide range of USB-keys, correct?
>

Yes.

> So, I have probably screwed somewhere while
> preparing them?
>
> So, some follow-up questions in this regard:
> - Does the partition table have to be MSDOS?

No, it could be GPT, too.

> - Should that work with 'proper' USB drives, too?

Yes. Any reliable brand of USB flash drive.

> - What are other potential pit-falls?

USB rootfs should be a reliable brand such as Sandisk. Other brands like Transcend is OK. Avoid Patriot drives at all cost.

Some older USB HDD enclosure controllers are not very good. So if you use USB HDD enclosure to house the rootfs, be aware that it might cause problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
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: