Quantcast
Channel: Linux Device Hacking - uBoot
Viewing all 900 articles
Browse latest View live
↧

Pogoplug Series 4 green light keeps flashing (1 reply)

March 15, 2017, 3:10 pm
$
0
0
I started the process to hack Pogoplug v4, but ended up appeared to be in an infinite loop problem. The green light in the front keeps blinking. I don't know Linux that well. Please help.

I started with a new Pogoplug v4 and connected via serial console. SSH cannot be activated. I first tried to backup the uBoot image in mtd0 with the command "nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0", but returned with something like nanddump not found in /bin/sh error. I copied the screen session, but accidentally pasted it and somehow executed the whole "session". Now I ended up with the infinite loop issue.

How can I recover from this?

Your help is greatly appreciated.
↧
Search

uboot env analysis uboot.2013.10-tld-5.ox820.environment (1 reply)

March 17, 2017, 8:57 pm
$
0
0
uboot.2013.10-tld-5.ox820.environment 



bootdelay=10

ethaddr=52:3b:20:9c:11:51
ethact=mii0

ipaddr=192.168.0.222
#pogo’s ip
serverip=192.168.0.220
# ip of pc running nc or Hercules SETUP utility
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot_nc=run if_netconsole start_netconsole
# wihout judge whether pc running nc or Hercules ready or not, start net-console directly

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
# Wait 5 seconds  countdown, which can be broken.And enter net-console when pc running nc or Hercules ready.
preboot = run preboot_nc
# preboot called by uboot 





dtb_file=/boot/dts/ox820-pogoplug-pro.dtb
load_dtb=echo loading DTB $dtb_file ...; ext2load $bootdev $device 0x62c00000 $dtb_file
load_initrd=echo loading uInitrd ...; ext2load $bootdev $device 0x60e00000 /boot/uInitrd
load_uimage=echo loading uImage ...; ext2load $bootdev $device 0x60500000 /boot/uImage




devices=usb ide
# usb ide mmc different types of boot device by sequence
disks=0 1 2 3
# multi disks connected for each usb ide or mmc, eg. usb0 to usb3 when multi usb disk plugged
bootdev=usb
# boot device usb
device=0:1
# boot disk:partition default disk0 partition1

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 ext2load $dev $disknum:1 0x60500000 /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

#scan each  disks and load uImage from first partition. eg: usb [0-3]:1 ide 0:1 mmc 0:1,set bootdev to (usb)|(ide)|(mmc) device to [0-3]:1


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;

# init usb, ide or mmc to read uEnv.txt


uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x60500000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
#load uEnv.txt from first partition of usb [0-3] ide 0 mmc0

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
#what is the functionn? whatever the result of if,run  uenv_read both?
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;
#??for disknum in 0?for sentence is for loop but only 0?

uenv_import=echo importing envs ...; env import -t 0x60500000

bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi

mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
# cusom_params no defination

bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm 0x60500000 0x60e00000 0x62c00000; else bootm 0x60500000 0x60e00000; fi; else if run load_dtb; then bootm 0x60500000 - 0x62c00000; else bootm 0x60500000; fi; fi

# according to uimage initrd and dtb,run bootm uimage initrd dtb or bootm uimage initrd or  bootm uimage – dtb or bootm uimage

bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
# load uenv,then boot



usb_custom_params=zswap.enabled=1
# definition  but not use



mainlineLinux=yes
usb_ready_retry=15
# definition  but not use

stderr=serial
stdin=serial
stdout=serial

blue comment is not clear,please help me,
red is another version to enable net-console with judgment, what about this sentence?
↧
↧

Problem installing Netgear Stora (10 replies)

March 18, 2017, 1:03 pm
$
0
0
Hi Bodhi,

I have started with the instructions of installing new uboot.
- First i did unpack the env-tools - did look if kernel did support it
Did see this: 
Updated 05 Sept 2015:

Kernel linux-4.2.0-kirkwood-tld-1 package has been uploaded. The following features were updated/added:

1. Incorprate patched nsa3xx-hwmon module for NSA320 and NSA310 (some variant of). This patch allows these boxes to use the nsa3xx-hwmon like before (Device Tree transition in kernel 3.17 has broken this module). It also streams line the way NSA3xx hwmon is implemented in the kernel.
2. New Marvell CESA crypto driver is activated in this kernel.
3. Netgear Stora DTS was modified to correct NAND chip deday and enable write access to mtd0 (u-boot and u-boot envs).

So i think fw_tools are supported with kernel 4.4.0 and higher.
Question: Does kernel 4.4.0 support envir-tools?

I ask this question becaus i get: 

root@debian:~# fw_printenv ethaddr
[  314.738491] __nand_correct_data: uncorrectable ECC error
...
[  317.216841] __nand_correct_data: uncorrectable ECC error
Warning: Bad CRC, using default environment
## Error: "ethaddr" not defined
root@debian:~#

And i don know if its important; the name of mtd0 is not u-boot, but orion_nand: 
root@debian:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 10000000 00020000 "orion_nand"
↧

Dockstar: bad block: it is save to flash uboot? (1 reply)

March 26, 2017, 8:01 pm
$
0
0
Hey there,

i want to flash one of my dockstar devices with newer u-boot, as described in http://forum.doozan.com/read.php?3,12381.

But demesg says it found a bad block, so i want ask if its save to flash u-boot? If not, what's the workaround?
(it's not important to preserve the original uboot or kernel)

Regards Lutz

Some snippets from the serial console: (boot log) 
U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
[...]
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ......... done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...


U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
[...]
Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-08-31  23:31:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1976384 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...
[...]
[    1.050000] Scanning device for bad blocks
[    1.140000] Bad eraseblock 1865 at 0x0e920000
[    1.150000] Using static partition definition

[    1.160000] Creating 4 MTD partitions on "nand_mtd":
[    1.160000] 0x00000000-0x00100000 : "u-boot"
[    1.170000] 0x00100000-0x00500000 : "uImage"
[    1.170000] 0x00500000-0x02500000 : "root"
[    1.180000] 0x02500000-0x10000000 : "data"
[...]
starting pid 333, tty '': '/bin/sh'
-sh-3.2# dmesg | egrep -i 'bad|flash'
[    0.240000] NFLASH_CS ....base fa000000, size   2MB
[    1.050000] Scanning device for bad blocks
[    1.140000] Bad eraseblock 1865 at 0x0e920000
[    7.870000] Empty flash at 0x00de8e44 ends at 0x00de9000
-sh-3.2# uname -a
Linux Pogoplug 2.6.22.18 #57 Mon Aug 31 16:31:01 PDT 2009 armv5tejl unknown
-sh-3.2# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "root"
mtd3: 0db00000 00020000 "data"
-sh-3.2#
↧

NSA310 heat (no replies)

April 3, 2017, 1:40 pm
$
0
0
Re-installing / setting up my NSA310 & NSA310S & I noticed the NSA310 gets extremely hot, even just idling the CPU is too hot to touch for more than a few seconds.The NSA310S on the other hand isn't as hot, but I have noticed it's much slower.

I can only assume that Zyxel noticed this and released the S variant to fix it. I'm planning on getting a small heatsink to try and cool it down a little.

My question is, what else can I do to try and reduce the heat?
↧
↧

how to transport u boot to a new Kirkwood device (no replies)

April 3, 2017, 8:28 pm
$
0
0
every teachers,I got a new Kirkwood devices a soft router.I hope to port your new and advanced uboot to this device what part I should know and modify ?and what is the debrick method if the kwboot doesn't work?
↧

V4 uBoot flash - boot from Stock Pogo OS (1 reply)

April 4, 2017, 4:16 pm
$
0
0
Hi all, It's been a while since I've been here! And my Goflex Net is still chugging along nicely (although it runs stock Pogo OS with optware and nothing exotic). No hardware mods, although it is powered through PoE via an adaptor - no worrying about power sockets for it!

I've just recently dug out my old V4 and thought it's time to start playing again. As mentioned with my GFN, I do like the Pogo functionality (when it works) so I don't want to lose that ability. It's been a long time since I played with uboot, and I've never touched the V4, but it looks like now it's got the capability to boot from the stock OS? I'm quite far out of the loop so it looks like I've confused myself.

Just so I'm clear in my own mind, by flashing uboot I still retain the ability to boot Pogo OS from the NAND? And I don't have to worry about the Env's (such as the pogo CEID?) being wiped from uboot which will break my.pogoplug.com functionality?

My ultimate goal would be to have debian on and SD card, but be able to remove that and boot into Pogo OS as needed. Is this doable without the need to reflash uboot each time these days?
↧

Pogo dead after uBoot update? (1 reply)

April 4, 2017, 4:26 pm
$
0
0
Hi all,

I wanted to update my Pogoplug (pink E02) from "Debian-3.17.0-kirkwood" to the latest version. Before installing new USB Debian rootfs I wanted to update uBoot to actual version.
I used following instructions from a german forum: 
cd /tmp
wget -c https://www.dropbox.com/s/0jkzjbryiz9qmbw/uboot.2016.05-tld-1.pogo_e02.bodhi.tar
wget -c https://www.dropbox.com/s/4smmw2wr4ugayz9/uboot.2016.05-tld-1.environment.bodhi.tar
tar -xf uboot.2016.05-tld-1.pogo_e02.bodhi.tar
tar -xf uboot.2016.05-tld-1.environment.bodhi.tar

# flash new uboot:
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot.2016.05-tld-1.pogo_e02.mtd0.kwb

# flash new uboot envs:
#(The MAC address will be set to a valid randomly generated local address.
# you can change it later in debian)
/usr/sbin/flash_erase /dev/mtd0 0xc0000 1
/usr/sbin/nandwrite -s 786432 /dev/mtd0 uboot.2016.05-tld-1.environment.img

The USB Thumb with old Debian rootfs was plugged in. After Pogo reboot the LED is fast blinking green (~20sec) and than changing to fast blinking orange. The LED do not stop blinking. If I detach the USB thumb the LED is also blinking like with it.
No chance to SSH. I have a USB-2-serial cable, but I am not sure what to do.
Any suggestions that might help me? Thanks!

Jörg
↧
Search

Qizhitong m501 v2 uboot and env (1 reply)

April 11, 2017, 12:00 pm
$
0
0
hello, I got a Qizhitong m501 v2, the uboot is customed, uboot env:

bootdelay=5
baudrate=9600
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
run_diag=yes
console=console=ttyS0,9600
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=mem=512M root=/dev/ram
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
bootcmd1=ide reset; ext2load ide 0:1 0x2000000 /uImage;setenv bootargs ro root=/dev/sda2 $(console) $(mvNetConfig) quiet;bootm 0x2000000
boottitle1=QiZhiTong Bootup
bootcmd2=ide reset; ext2load ide 0:c 0x2000000 /boot/uImage;setenv bootargs ro root=/dev/sda12 $(console) $(mvNetConfig) quiet;bootm 0x2000000
boottitle2=QiZhiTong Restore
password=$1$F5w1D$nzHGehkXN8JlDdjraKy1n/
bootdefault=1
bootcmd=nand read.e 0x2800000 0x400000 0x700000; nand read.e 0x2000000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root) $(mvNetConfig);bootm 0x2000000 0x2800000
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000;
ethaddr=00:90:0b:1f:bb:6c
ethmtu=1500
eth1addr=00:90:0b:1f:bb:6d
eth1mtu=1500
mvNetConfig=mv_net_config=(00:90:0b:1f:bb:6d,0:1:2:3)(00:90:0b:1f:bb:6e,4),mtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=no
pcieTune=no

Environment size: 1556/131068 bytes
MB302>>

bodhi, Is there newer uboot ?

support uart boot.
md ff00003c
ff00003c: 00000121 e3a00000 e59f222c e5921000 !.......,"......
ff00004c: e2013008 e3530000 1a000002 e3811008 .0....S.........
↧
↧

booting Pogo V4 with Openwrt on NAND (3 replies)

April 14, 2017, 5:31 pm
$
0
0
I have replaced the uboot in the NAND with bodhi's by following http://forum.doozan.com/read.php?3,12381

I can boot debian on MMC.


However, now I would like to put openwrt on the nand and setup such that in case it cannot boot from USB, MMC, then it should go boot from the nand.

This is what I have done on the NAND so far:

/tmp/ubiformat /dev/mtd1

/tmp/ubiattach -p /dev/mtd1
/tmp/ubimkvol /dev/ubi0 -m -N rootfs

#mount ubi rootfs to /tmp/ubi
mkdir /tmp/ubi
mount -t ubifs ubi0:rootfs /tmp/ubi

#Chaos Calmer 15.05
cd /tmp
wget http://downloads.openwrt.org/chaos_calmer/15.05/kirkwood/generic/openwrt-15.05-kirkwood-generic-rootfs.tar.gz
wget http://downloads.openwrt.org/chaos_calmer/15.05/kirkwood/generic/openwrt-15.05-kirkwood-zImage
wget http://downloads.openwrt.org/chaos_calmer/15.05/kirkwood/generic/md5sums

#extract rootfs.tar.gz to ubi rootfs at /tmp/ubi
cd /tmp/ubi
tar xvzf /tmp/openwrt*rootfs.tar.gz

mkdir boot
mv /tmp/openwrt*kirkwood-zImage ./boot/zImage

cd boot
mkdir dts
cp /boot/dts/kirkwood-pogoplug_v4.dtb .

sync
cd /
umount /tmp/ubi

Now how should I modify the env to do this? I have flashed the default env from 2016.05 U-Boot at the moment.
↧

Pogoplug V4 - uBoot with Debian (1 reply)

April 16, 2017, 1:24 pm
$
0
0
Dear Friends,

I have successfully installed uBoot and Debian is running smoothly on my Seagate Dockstar. I used this url http://projects.doozan.com/uboot for uBoot flash.

Now i want to setup the uboot and Debian on my New Pogoplug Series 4. I have few queries before i proceed.

1.Uboot Script : Does this script http://projects.doozan.com/uboot will pick up the latest Uboot or should i need to use a different Url. Because bodhi has mentioned to use the latest uBoot package for a better Modern NAS support.

2.Does anyone has experience in using Debian on micro SD card with class 4 in Pogoplug V4. is that stable?

Thanks
Nirmal
↧

Dockstar - no network (1 reply)

April 18, 2017, 7:17 pm
$
0
0
Guys, can I get some help with a Dockstar not getting/starting network?

I do have serial setup and see the following error while starting up:
[ 54.147022] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

I'm not sure if the ethernet port is dead or if I messed up some uboot variables as I was trying to upgrade uboot.
Not sure what logs to include but I'l be willing to grab them and post here.

Also I have read and is willing to update to the latest uboot but would like some input before I mess things up further.
I'm running an old uboot: 
U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
u-boot>>

ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; na
nd read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
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
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && u
bifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm
0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if t
est $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; se
tenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
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_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext
2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; el
se bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd;
 usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=xx:xx:xx:xx:xx:xx
arcNumber=2097

Thanks
↧

Pogoplug v4 usb image (12 replies)

April 24, 2017, 11:41 pm
$
0
0
a friend gave me his pogoplug but didnt have the usb drive he was booting from
i need a bootable usb drive image i can start with
all the pogoplug does is the green led flashes

he told me he had it set to boot from the usb drive
so im guessing its looking for a boot image from the usb

its not pulling an ip from the dhcp server so im pretty sure its not booting


thanks for any help
↧
↧

Command missing from 2016.05-tld-1 Uboot for SheevaPlug (no replies)

April 25, 2017, 8:21 pm
$
0
0
I have acquired a Sheevaplug and I just tried installed the latest uboot 2016.05-tld-1. I then tried to boot an SD with the Debian root file system from the Debian section of this forum. It appears that the Sheevaplug version of uboot is missing at least the mmc and load commands. See the following log from attempting to boot the SD card after successful install of uboot and the uboot.2016.05-tld-1 environment files. I did add some other uboot environment variable to allow me to boot from nand, but the commands which should allow booting from SD have not been modified. 


U-Boot 2016.05-tld-1 (Jun 12 2016 - 14:02:47 -0700)
Marvell-Sheevaplug

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
2 USB Device(s) found
       scanning usb for storage devices... Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device

Use USB retry period from the environment: 15 second(s)
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
1 Storage Device(s) found
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
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
Error: Cannot find high speed parent of usb-1 device
  1     2048            29184           972187e0-01     0b
loading envs from usb 0 ...
Unknown command 'load' - try 'help'
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
Unknown command 'load' - try 'help'
device usb 1:1
Unknown command 'load' - try 'help'
device usb 2:1
Unknown command 'load' - try 'help'
device usb 3:1
Unknown command 'load' - try 'help'
Scan device ide
Unknown command 'ide' - try 'help'
device ide 0:1
Unknown command 'load' - try 'help'
device ide 1:1
Unknown command 'load' - try 'help'
device ide 2:1
Unknown command 'load' - try 'help'
device ide 3:1
Unknown command 'load' - try 'help'
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
Unknown command 'load' - try 'help'
device mmc 1:1
Unknown command 'load' - try 'help'
device mmc 2:1
Unknown command 'load' - try 'help'
device mmc 3:1
Unknown command 'load' - try 'help'
loading uImage ...
Unknown command 'load' - try 'help'
loading uInitrd ...
Unknown command 'load' - try 'help'
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
Unknown command 'load' - try 'help'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Sheevaplug> help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootefi - Boots an EFI payload from memory

bootelf - Boot from an ELF image in memory
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bootvx  - Boot vxWorks from an ELF image
bootz   - boot Linux zImage image from memory
chpart  - change active partition
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
date    - get/set/reset date & time
dhcp    - boot image via network using DHCP/TFTP protocol
dns     - lookup the IP of a hostname
echo    - echo args to console
editenv - edit environment variable
env     - environment handling commands
exit    - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
ext4load- load binary file from a Ext4 filesystem
ext4ls  - list files in a directory (default /)
ext4size- determine a file's size
false   - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fatsize - determine a file's size
fdt     - flattened device tree utility commands
fsinfo  - print information about jffs filesystems
fsload  - load binary file from a jffs filesystem image
fsls    - list jffs files in a directory (default /)
go      - start application at address 'addr'
gpio    - query and control gpio pins
help    - print command description/usage
iminfo  - print header information for application image
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loadx   - load binary file over serial line (xmodem mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mtdparts- define flash/nand partitions
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
setexpr - set environment variable as the result of eval expression
showvar - print local hushshell variables
sleep   - delay execution for some time
sntp    - synchronize RTC via network
source  - run script from memory
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true    - do nothing, successfully
ubi     - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
Sheevaplug> printenv
arcNumber=2097
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootargs_nand=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
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_nand=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=00:50:43:01:44:F0
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.231
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
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
 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
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_nand=setenv bootargs $bootargs_nand
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x81
0000
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_loaded=0
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_ready_retry=15

Environment size: 3456/131068 bytes
Sheevaplug>

As you can see from the ouput of help above there is no "mmc" command or any "load" command which causes issues with the scan_disk run command. I believe this will also cause issues with booting from USB, but I could modify scandisk to use ext4load instead of load to allow boot from USB. However I don't see any way to boot from SD with this uboot version.

Ray
↧

Pogoplug v4 Mobile uboot issue. (1 reply)

April 26, 2017, 2:31 pm
$
0
0
Prior to flashing I entered ethaddr: 

fw_printenv ethaddr 
Warning: Bad CRC, using default environment.
## Error: "ethaddr" not defined


I ignored it since I'd be flashing the envs anyway per the instructions.

I flashed the new u-boot successfully changed all the corresponding envs except ethaddr. This time it said, 

Can't overwrite "ethaddr"


I figured I'd reboot the box into linux and then adjust it. The Pogo successfully booted into Debian with the default ethaddr from the flashed envs and changed the ethaddr to the one on the bottom of the case (I assume that is the right one). When I reboot, I am not able to access the device. It only works with the default ethaddr that I flashed from uboot.2016.05-tld-1.environment.bodhi.tar.

Is that fixable?
↧
Search

Assistance requested booting PogoOS (1 reply)

April 27, 2017, 3:25 pm
$
0
0
After using my pogoplug v4 mobile mofified with optware as per instructions in Qui's blog, I decided to install the Debian linux.
Since download.qnology.com is down, I used the script at https://github.com/pepaslabs/pogoplug_mobile_uboot_installer to install uboot

Now my pogoplug v4 mobile works fine with SD-Card or USB using the pre-built rootfs images at https://github.com/pepaslabs/pogoplug-v4-bodhi-rootfs-debian/releases/download/jessie-3.18.5-20151110/Debian-jessie-3.18.5-pogoplug-v4-20151110-disk-image.4GB.img.zip.

However I am unable too boot into the original PogoOS when I start the pogoplug without SD-Card or USB attached. I spent many days reading Qui's and Bodhi's various documents including http://blog.qnology.com/p/pogoplug-v4-boot-default-pogoplug-os.html and may have messed-up my environment, experimenting with said instructions. While experimenting the plug booted into the original OS once, but I am unable to repeat.

Would appreciate any help in configuring my pogoplug so that it boots into original PogoOS when SD-Card or USB is *not attached*.

Following is my environment and netconsole output.

fw_printenv:-

root@Pogoplug:~# fw_printenv
baudrate=115200
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
partition=nand0,2
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
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_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
ethaddr=00:25:31:05:b6:5a
arcNumber=3960
machid=F78
usb_rootfstype=ext3
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
bootcmd=run bootcmd_mmc; run bootcmd_usb; run bootcmd_pogo; run bootcmd_sata; reset
bootcmd_pogo=if ubi part root 2048 && ubifsmount ubi:rootfs && ubifsload 0x800000 uboot.mtd0.dockstar.original.kwb ; then go 0x800200; fi
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
preboot=run preboot_nc
ipaddr=192.168.1.13
serverip=192.168.1.15


Netconsole without usb or sdcard attached (Fails to boot PogoOS):-

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot: 0
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=4", size 112 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 895, bad PEBs: 1, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/4, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 0, total reserved PEBs: 895, PEBs reserved for bad PEB handling: 8
Loading file 'uboot.mtd0.dockstar.original.kwb' to addr 0x00800000...
Done
## Starting application at 0x00800200 ...


Netconsole with SD-Card(OS) and USB(Storage) attached (Sucessful boot into Debian):-

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot: 0

MMC rescan: current device # 0 initialized OK
2875692 bytes read in 1202 ms (2.3 MiB/s)
6535284 bytes read in 1410 ms (4.4 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.18.5-kirkwood-tld-1
Created: 2015-11-11 5:03:31 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2875628 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.18.5-kirkwood-tld-1
Created: 2015-02-19 1:49:36 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6535220 Bytes = 6.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK


Starting kernel ...
↧

Booting Pogo V3 Debian rootfs from OpenWrt u-boot (no replies)

May 2, 2017, 7:51 am
$
0
0
bodhi Wrote:
-------------------------------------------------------
> ming,
>
> hahibie has a good point, if the uboot envs are c
> urrently set up to boot Openwrt, you need to modif
> y them to boot USB. Please post the current uboot
> envs if you have installed new uboot. 
root@PogoPlug:/# fdisk -l 
You must set cylinders.
You can do this from the extra functions menu.

Disk /dev/mtdblock0: 0 MB, 262144 bytes
171 heads, 42 sectors/track, 0 cylinders, total 512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaaaaaaaa

This doesn't look like a partition table
Probably you selected the wrong device.

          Device Boot      Start         End      Blocks   Id  System
/dev/mtdblock0p1   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock0p2   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock0p3   ?  2863311530       21843   715838805   aa  Unknown
/dev/mtdblock0p4   ?  2863311530  1426085203  1428870485   aa  Unknown
You must set cylinders.
You can do this from the extra functions menu.

Disk /dev/mtdblock1: 1 MB, 1441792 bytes
255 heads, 63 sectors/track, 0 cylinders, total 2816 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaaaaaaaa

This doesn't look like a partition table
Probably you selected the wrong device.

          Device Boot      Start         End      Blocks   Id  System
/dev/mtdblock1p1   ?  1437226410     5570643  1431655765   aa  Unknown
/dev/mtdblock1p2   ?  2863289685     5570558   718624085   aa  Unknown
/dev/mtdblock1p3   ?  1431677610       21843  1431655765   aa  Unknown
/dev/mtdblock1p4   ?  2863289685     5570558   718624085   aa  Unknown

Partition table entries are not in disk order

Disk /dev/mtdblock2: 0 MB, 262144 bytes
255 heads, 63 sectors/track, 0 cylinders, total 512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock3: 33 MB, 33554432 bytes
171 heads, 42 sectors/track, 9 cylinders, total 65536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaaaaaaaa

This doesn't look like a partition table
Probably you selected the wrong device.

          Device Boot      Start         End      Blocks   Id  System
/dev/mtdblock3p1   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock3p2   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock3p3   ?  2863311530       21843   715838805   aa  Unknown
/dev/mtdblock3p4   ?  2863311530  1426085203  1428870485   aa  Unknown

Disk /dev/mtdblock4: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders, total 256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock5: 10 MB, 10485760 bytes
255 heads, 63 sectors/track, 1 cylinders, total 20480 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock6: 119 MB, 119537664 bytes
255 heads, 63 sectors/track, 14 cylinders, total 233472 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock7: 132 MB, 132120576 bytes
255 heads, 63 sectors/track, 16 cylinders, total 258048 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock8: 134 MB, 134217728 bytes
171 heads, 42 sectors/track, 36 cylinders, total 262144 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaaaaaaaa

This doesn't look like a partition table
Probably you selected the wrong device.

          Device Boot      Start         End      Blocks   Id  System
/dev/mtdblock8p1   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock8p2   ?  2863311530  1431655763  1431655765   aa  Unknown
/dev/mtdblock8p3   ?  2863311530       21843   715838805   aa  Unknown
/dev/mtdblock8p4   ?  2863311530  1426085203  1428870485   aa  Unknown

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 16.2 GB, 16239329280 bytes
64 heads, 32 sectors/track, 15487 cylinders, total 31717440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@PogoPlug:/# tune2fs -L rootfs /dev/sdb
tune2fs 1.42.4 (12-June-2012)
root@PogoPlug:/#

how can i set up to boot USB rootfs
↧
↧

Pogoplug Mobile no light/ssh/serial connection (3 replies)

May 3, 2017, 10:24 am
$
0
0
Hi, I am new here so I hope I'm posting this in the correct place. I have a pogoplug Mobile that I was experimenting with. I started by following this tutorial http://blog.qnology.com/2014/07/hacking-pogoplug-v4-series-4-and-mobile.html?m=1

The device was new so I needed serial console access. I got serial access and changed the rcS file to start up dropbear and disable the pogoplug services. Then I followed the tutorial from ssh.

I self hosted the files from a git mirror and pulled them in wget. I followed all the way up to the section of installing Debian /alarm. I didn't start this step yet. Everything looked good and on all my flashes I got a success.

Before I was about to start the Linux install, I rebooted the device. That's when it never came back up. I did up to this point with no usb or sd card in. I did do the netconsole part of the tutorial. I literally copied the exact commands from the tutorial. However my network is on 192.168.0.1.

When I rebooted I ran /sbin/reboot command. No lights ever came back on. I also tried connecting back to the serial console and nothing was loading there either.

Is this something I can save? And where did I probably go wrong?
↧

Netgear Stora: EHCI timed out on TD when loading uInitrd (no replies)

May 8, 2017, 5:41 am
$
0
0
Hi bodhi,

I have successfully installed the latest u-boot on my Netgear Stora, and have sucessfully booted debian 8 wheezy from a 2GB industrial grade USB stick from HGST. Thanks a lot for your effort and instructions!

However, repeating the same procedure using a 8GB commercial grade USB stick from Patriot, u-boot fails loading uInitrd. I find this rather strange since u-boot loads uImage (3166745 bytes) just fine immediately before failing to load uInitrd (7179935 bytes).

This is the complete boot sequense: 
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:45:22 -0700)
Netgear-MS2110

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0 
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

Reset IDE: ide_preinit failed

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

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            15122432        b138172b-01     83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **

IDE device 0 not available
3166745 bytes read in 350 ms (8.6 MiB/s)
EHCI timed out on TD - token=0xd8d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x128d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x20008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x128d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x20008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x128d80
EHCI timed out on TD - token=0x80008d80
 ** ext4fs_devread read error - block
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2017-05-08  11:15:07 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3166681 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux...

As expected, without a root file system, the linux kernel panics: 

[    3.639815] rtc-pcf8563 0-0051: setting system clock to 1970-01-02 00:39:42 UTC (88782)
[    3.650259] Waiting 5 sec before mounting root device...
[    8.664286] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -19
[    8.671719] Please append a correct "root=" boot option; here are the available partitions:
[    8.680182] 1f00            1024 mtdblock0  (driver?)
[    8.685329] 1f01            4096 mtdblock1  (driver?)
[    8.690418] 1f02          257024 mtdblock2  (driver?)
[    8.695572] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    8.703882] CPU: 0 PID: 1 Comm: swapper Not tainted 4.4.0-kirkwood-tld-1 #1
[    8.710869] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[    8.717203] [<c0016784>] (unwind_backtrace) from [<c00129f8>] (show_stack+0x10/0x14)
[    8.724991] [<c00129f8>] (show_stack) from [<c00c2200>] (panic+0x80/0x214)
[    8.731908] [<c00c2200>] (panic) from [<c07d9280>] (mount_block_root+0x204/0x24c)
[    8.739438] [<c07d9280>] (mount_block_root) from [<c07d93b4>] (mount_root+0xec/0x118)
[    8.747311] [<c07d93b4>] (mount_root) from [<c07d9504>] (prepare_namespace+0x124/0x184)
[    8.755359] [<c07d9504>] (prepare_namespace) from [<c07d8e9c>] (kernel_init_freeable+0x208/0x258)
[    8.764287] [<c07d8e9c>] (kernel_init_freeable) from [<c05b16b4>] (kernel_init+0x8/0xe4)
[    8.772427] [<c05b16b4>] (kernel_init) from [<c000f090>] (ret_from_fork+0x14/0x24)
[    8.780039] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   84.803920] random: nonblocking pool is initialized

The u-boot environment is 
Netgear Stora> printenv
arcNumber=2743
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; reset
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=5
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1m(uboot),4m@1m(kernel),251m@5m(rootfs) rw
partition=nand0,2
rootdelay=5
rootfstype=ext2
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; ide reset; setenv uenv_loaded 0; for devtype in usb ide; 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 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if $devtype part $disknum; then run uenv_read; fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 1436/131068 bytes

In addition to its larger capasity, the Patriot "Tabi Lifestyle Series" USB stick supports USB 3.0, but if compatibility was an issue u-boot should have failed on both the uImage and uInitrd images. Right?

With the 2 GB HGST stick, u-boot reports 
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

Reset IDE: ide_preinit failed

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

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            3909632         00091483-01     83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **

IDE device 0 not available
3154896 bytes read in 349 ms (8.6 MiB/s)
7179935 bytes read in 426 ms (16.1 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   5:55:25 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3154832 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

So the messages "Reset IDE: ide_preinit failed", "** File not found /boot/uEnv.txt **" and "IDE device 0 not available" can safely be ignored, but this error message puzzels me a bit: 
 ** ext4fs_devread read error - block

It is true that this stick was once been formatted with ext4, but it has then been formatted both as fat32 and now ext3. Does the current u-boot always load uInitrd using ext4fs_devread() or does this error mean that the ext4 signature is somehow "sticky" on the USB stick?

It seems I'm not the first to experience this. So should I go and get a new USB stick, or have I stumbled over a bug in u-boot?

Regards,
Trond Melen
↧

GoFlexHome not booting (no replies)

May 9, 2017, 8:38 am
$
0
0
I have only just discovered this forum, so apologies if I'm posting in the wrong place...

I have been using a Seagate GoFlex Home unit for several years and had read that it was possible to install one's own operating system on it after reading https://archlinuxarm.org/platforms/armv5/seagate-goflex-home. I didn't want to mess with my unit as it was doing a reasonable job as a SAMBA server, but eventually decided to get a second dock to experiment with and managed to install Arch Linux, but after trying one or two things I found I was unable to restore the factory settings and it became inaccessible from the network.

On this forum I'm confused by all the different platforms supported and don't know the relationship between dockstar, shiva pogoplug and GoFlex. My question is, is there some software I can install on a USB stick which will enable my unit to boot up and connect to the network? Alternatively can I set up some verbose logging which will output to a logfile which I can examine after removing the USB stick?
↧
Viewing all 900 articles
Browse latest View live
Search