2017.07-2023.04 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug
Posted by bodhi
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 15, 2014 12:07AM |
Admin Registered: 13 years ago Posts: 18,543 |
@archon,
You should wait for the formal release. But if you want to install it now, then only 2 posts are relevant:
- The 1st post of this thread
- This post: http://forum.doozan.com/read.php?3,12381,17420#msg-17420
Do you have difficulty understand all the steps in the first post?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/15/2014 12:08AM by bodhi.
You should wait for the formal release. But if you want to install it now, then only 2 posts are relevant:
- The 1st post of this thread
- This post: http://forum.doozan.com/read.php?3,12381,17420#msg-17420
Do you have difficulty understand all the steps in the first post?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/15/2014 12:08AM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 16, 2014 05:42AM |
Registered: 10 years ago Posts: 53 |
pogoplug e02
I am unable to see anything through putty, my USB to TTL Converter is http://www.ebay.com/itm/New-1PCS-5PIN-PL2303-USB-To-TTL-Auto-Converter-Adapter-Module-unit-For-arduino-/141150349286
I am following this guide:
http://blog.qnology.com/2013/10/pogoplug-e02-v2-serial-connection.html
Tested on 2 compters, winxp/win7 x32.
Putty window just stays blank.
If i connect sata drive inside 2.5" usb 2.0 external case it boots fine into debian installed on hdd, rescue system http://forum.doozan.com/read.php?4,7915 works too.
Here is fw_printenv output:
cat /etc/fw_env.config
Both outputs were created while booted into rescue system.
Here is netconsole output:
http://forum.doozan.com/read.php?3,14,page=1
Edited 2 time(s). Last edit at 10/16/2014 06:22AM by jst818.
I am unable to see anything through putty, my USB to TTL Converter is http://www.ebay.com/itm/New-1PCS-5PIN-PL2303-USB-To-TTL-Auto-Converter-Adapter-Module-unit-For-arduino-/141150349286
I am following this guide:
http://blog.qnology.com/2013/10/pogoplug-e02-v2-serial-connection.html
Tested on 2 compters, winxp/win7 x32.
Putty window just stays blank.
If i connect sata drive inside 2.5" usb 2.0 external case it boots fine into debian installed on hdd, rescue system http://forum.doozan.com/read.php?4,7915 works too.
Here is fw_printenv output:
//masked only my ethaddr.Quote
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_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; nand 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 && ubifsload 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 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_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_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 ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else 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=00:XX XX XX XX XX
serverip=192.168.1.2
ipaddr=192.168.1.100
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
arcNumber=3542
machid=dd6
usb_rootfstype=ext3
cat /etc/fw_env.config
Quote
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000
Both outputs were created while booted into rescue system.
Here is netconsole output:
http://forum.doozan.com/read.php?3,14,page=1
Quote
nc111nt_rodneybeede>nc -l -u -p 6666
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 91 MiB
UBI: number of good PEBs: 726
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 715
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
NAND read: device 0 offset 0x100000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2-kirkwide
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3627768 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment
Starting kernel ...
Edited 2 time(s). Last edit at 10/16/2014 06:22AM by jst818.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 16, 2014 01:30PM |
Registered: 10 years ago Posts: 53 |
Now i flashed with method A, now pogo e02 wont boot, with/without usb hdd.
\nc111nt_rodneybeede>nc -l -u -p 6666
output:
with 1 usb hdd attached:
Edited 3 time(s). Last edit at 10/16/2014 01:48PM by jst818.
\nc111nt_rodneybeede>nc -l -u -p 6666
output:
Quote
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Unknown command 'fw_setenv' - try 'help'
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
no USB devices available
no USB devices available
no USB devices available
no USB devices available
PogoE02>
with 1 usb hdd attached:
Quote
\nc111nt_rodneybeede>nc -l -u -p 6666
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Unknown command 'fw_setenv' - try 'help'
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start 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
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 20971520 000d7189-01 83 Boot
2 20973568 1932550144 000d7189-02 83
Unknown command 'setexpr' - try 'help'
Attempting to boot from usb 0:1...
Unknown command 'load' - try 'help'
Checking if uenvcmd is set ...
Running default loadzimage ...
Unknown command 'load' - try 'help'
Running default loaduimage ...
Unknown command 'load' - try 'help'
no USB devices available
no USB devices available
no USB devices available
PogoE02>
Quote
PogoE02> printenv
p r i n t e n v
arcNumber=3542
baudrate=115200
bootcmd=usb start; setenv letter 9;for type in usb; do for disk in 0 1 2 3; do i
f ${type} part ${disk};then setexpr letter $letter + 1;run load;fi;done;done;
bootcmd_pogo=run bootcmd_rescue
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000;
bootm 0x800000
bootdelay=10
bootm=echo Booting from ${disk} ...; run setargs; bootm ${loadaddr};
bootz=echo Booting from ${disk} ...; run setargs; bootz ${loadaddr} - ${fdt_addr
};
console=ttyS0
ethact=egiga0
ethaddr=00:XXXXXXXX
fdt_addr=0x800000
fdt_file=/boot/dtbs/kirkwood-pogo_e02.dtb
if_netconsole=ping $serverip
importbootenv=echo Importing environment (uEnv.txt)...; env import -t $loadaddr
$filesize
ipaddr=192.168.1.100
letter=9
load=echo Attempting to boot from ${type} ${disk}:1...;if run loadbootenv; then
run importbootenv;fi;echo Checking if uenvcmd is set ...;if test -n $uenvcmd; th
en echo Running uenvcmd ...;run uenvcmd;fi;echo Running default loadzimage ...;i
f run loadzimage; then run loadfdt;run bootz;fi;echo Running default loaduimage
...;if run loaduimage; then run bootm;fi;
loadaddr=0x810000
loadbootenv=load ${type} ${disk}:1 ${loadaddr} /boot/uEnv.txt
loadfdt=load ${type} ${disk}:1 ${fdt_addr} ${fdt_file}
loaduimage=load ${type} ${disk}:1 ${loadaddr} ${uimage}
loadzimage=load ${type} ${disk}:1 ${loadaddr} ${zimage}
machid=dd6
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
ncip=192.168.1.2
preboot=run if_netconsole start_netconsole
rescue_installed=1
serverip=192.168.1.2
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts
setargs=setenv bootargs console=${console},${baudrate} ${optargs} root=/dev/sd${
letter}1 rw rootwait ${mtdparts}
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;fw_setenv start_netconsole setenv ncip
$serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stder
r nc; version;
stderr=nc
stdin=nc
stdout=nc
uimage=/boot/uImage
zimage=/boot/zImage
Environment size: 2162/131068 bytes
PogoE02>
Edited 3 time(s). Last edit at 10/16/2014 01:48PM by jst818.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 16, 2014 02:23PM |
Registered: 9 years ago Posts: 11 |
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 16, 2014 02:44PM |
Admin Registered: 13 years ago Posts: 18,543 |
jst818,
> U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
> Pogoplug E02
You are in a wrong thread! this u-boot buid is davygravy's, it's a different build. Please repost in a new thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
> Pogoplug E02
You are in a wrong thread! this u-boot buid is davygravy's, it's a different build. Please repost in a new thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 16, 2014 02:54PM |
Admin Registered: 13 years ago Posts: 18,543 |
jst818,
The right u-boot:
But wrong u-boot envs:
For 2014.07-tld-1 u-boot, you need to flash the default envs in section B in the 1st post of this thread:
You seem to have tried every released u-boots out there in the wild :) it's not a bad thing to try and find what you like. However, please be aware that they are all different versions, therefore the envs most likely can not be used interchangebly. Whenever you flash a u-boot image, you must also flash the default envs that come with it (unless you already know that your existing u-boot envs can be used).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
The right u-boot:
> U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52) > Pogo E02
But wrong u-boot envs:
> PogoE02> printenv
> p r i n t e n v
> arcNumber=3542
> baudrate=115200
> bootcmd=usb start; setenv letter 9;for type in
> usb; do for disk in 0 1 2 3; do i
> f ${type} part ${disk};then setexpr letter $letter
> + 1;run load;fi;done;done;
> bootcmd_pogo=run bootcmd_rescue
> bootcmd_rescue=run set_bootargs_rescue; nand
> read.e 0x800000 0x100000 0x400000;
> bootm 0x800000
> bootdelay=10
> bootm=echo Booting from ${disk} ...; run setargs;
> bootm ${loadaddr};
> bootz=echo Booting from ${disk} ...; run setargs;
> bootz ${loadaddr} - ${fdt_addr
> };
> console=ttyS0
> ethact=egiga0
> ethaddr=00:XXXXXXXX
> fdt_addr=0x800000
> fdt_file=/boot/dtbs/kirkwood-pogo_e02.dtb
> if_netconsole=ping $serverip
> importbootenv=echo Importing environment
> (uEnv.txt)...; env import -t $loadaddr
> $filesize
> ipaddr=192.168.1.100
> letter=9
> load=echo Attempting to boot from ${type}
> ${disk}:1...;if run loadbootenv; then
> run importbootenv;fi;echo Checking if uenvcmd is
> set ...;if test -n $uenvcmd; th
> en echo Running uenvcmd ...;run uenvcmd;fi;echo
> Running default loadzimage ...;i
> f run loadzimage; then run loadfdt;run
> bootz;fi;echo Running default loaduimage
> ...;if run loaduimage; then run bootm;fi;
> loadaddr=0x810000
> loadbootenv=load ${type} ${disk}:1 ${loadaddr}
> /boot/uEnv.txt
> loadfdt=load ${type} ${disk}:1 ${fdt_addr}
> ${fdt_file}
> loaduimage=load ${type} ${disk}:1 ${loadaddr}
> ${uimage}
> loadzimage=load ${type} ${disk}:1 ${loadaddr}
> ${zimage}
> machid=dd6
> mtdids=nand0=orion_nand
> mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
> ncip=192.168.1.2
> preboot=run if_netconsole start_netconsole
> rescue_installed=1
> serverip=192.168.1.2
> set_bootargs_rescue=setenv bootargs
> console=$console ubi.mtd=2 root=ubi0:rootfs
> ro rootfstype=ubifs $mtdparts
> setargs=setenv bootargs
> console=${console},${baudrate} ${optargs}
> root=/dev/sd${
> letter}1 rw rootwait ${mtdparts}
> start_netconsole=setenv ncip $serverip; setenv
> bootdelay 10; setenv stdin nc; se
> tenv stdout nc; setenv stderr nc;
> version;fw_setenv start_netconsole setenv ncip
> $serverip; setenv bootdelay 10; setenv stdin nc;
> setenv stdout nc; setenv stder
> r nc; version;
> stderr=nc
> stdin=nc
> stdout=nc
> uimage=/boot/uImage
> zimage=/boot/zImage
>
> Environment size: 2162/131068 bytes
> PogoE02>
For 2014.07-tld-1 u-boot, you need to flash the default envs in section B in the 1st post of this thread:
B. Flashing default u-boot envs image
You seem to have tried every released u-boots out there in the wild :) it's not a bad thing to try and find what you like. However, please be aware that they are all different versions, therefore the envs most likely can not be used interchangebly. Whenever you flash a u-boot image, you must also flash the default envs that come with it (unless you already know that your existing u-boot envs can be used).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 25, 2014 04:38PM |
Registered: 11 years ago Posts: 214 |
shv Wrote:
-------------------------------------------------------
> bodhi Wrote:
> > ------------------------------------------------------
> > @shv,
> >
> > uboot.2014.07-tld-1.goflexnet.bodhi.tar is the latest U-Boot and I'm running it on my GoFlex Net.
> > Did you keep the log? I can take a look to see if you've missed anything.
> > I hope you did not flash the archive itself?
> >
> I don't have a log. But I am sure that I didn't flash the archive. I hope I will get the JTAG
> running so that I can check the Flash memory content to see what is is wrong. I will try to use
> a USB Blaster interface togther with OpenOCD tool. It will take some time to get the interface
> delivered from China.
>
> -shv
I successfully unbricked the Goflex Net device using a J-link JTAG interface together with OpenOCD. I read out the first 64 KB of the flash and compared it to uboot.2014.07-tld-1.goflexnet.mtd0.kwb. The overall data structure was the same but some bytes were different. After I flashed the file again with the JTAG interface the device is working again. I don't know where in the previous flashing process the memory content was corrupted.
-shv
Edited 4 time(s). Last edit at 10/26/2014 04:19AM by shv.
-------------------------------------------------------
> bodhi Wrote:
> > ------------------------------------------------------
> > @shv,
> >
> > uboot.2014.07-tld-1.goflexnet.bodhi.tar is the latest U-Boot and I'm running it on my GoFlex Net.
> > Did you keep the log? I can take a look to see if you've missed anything.
> > I hope you did not flash the archive itself?
> >
> I don't have a log. But I am sure that I didn't flash the archive. I hope I will get the JTAG
> running so that I can check the Flash memory content to see what is is wrong. I will try to use
> a USB Blaster interface togther with OpenOCD tool. It will take some time to get the interface
> delivered from China.
>
> -shv
I successfully unbricked the Goflex Net device using a J-link JTAG interface together with OpenOCD. I read out the first 64 KB of the flash and compared it to uboot.2014.07-tld-1.goflexnet.mtd0.kwb. The overall data structure was the same but some bytes were different. After I flashed the file again with the JTAG interface the device is working again. I don't know where in the previous flashing process the memory content was corrupted.
-shv
Edited 4 time(s). Last edit at 10/26/2014 04:19AM by shv.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 28, 2014 02:48AM |
Admin Registered: 13 years ago Posts: 18,543 |
>
> I successfully unbricked the Goflex Net device
> using a J-link JTAG interface together with
> OpenOCD. I read out the first 64 KB of the flash
> and compared it to
> uboot.2014.07-tld-1.goflexnet.mtd0.kwb. The
> overall data structure was the same but some bytes
> were different. After I flashed the file again
> with the JTAG interface the device is working
> again. I don't know where in the previous flashing
> process the memory content was corrupted.
>
> -shv
Interesting. But it's a good learning exeperience with JTAG. It would be nice if you can post your JTAG unbricking log and parts, setup …. :) when you find the time to do it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I successfully unbricked the Goflex Net device
> using a J-link JTAG interface together with
> OpenOCD. I read out the first 64 KB of the flash
> and compared it to
> uboot.2014.07-tld-1.goflexnet.mtd0.kwb. The
> overall data structure was the same but some bytes
> were different. After I flashed the file again
> with the JTAG interface the device is working
> again. I don't know where in the previous flashing
> process the memory content was corrupted.
>
> -shv
Interesting. But it's a good learning exeperience with JTAG. It would be nice if you can post your JTAG unbricking log and parts, setup …. :) when you find the time to do it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 28, 2014 10:54AM |
Registered: 11 years ago Posts: 214 |
bodhi Wrote:
-------------------------------------------------------
> Interesting. But it's a good learning exeperience
> with JTAG. It would be nice if you can post your
> JTAG unbricking log and parts, setup …. :) when
> you find the time to do it.
Yes, I will do if I find some time. For most steps howto's are already available. For the time being: I've taken necessary information from the following links:
http://wiki.openwrt.org/toh/seagate/goflexnet
http://www.yourwarrantyisvoid.com/2010/09/08/dead-dockstar-resurrected-with-jtag/
http://forum.doozan.com/read.php?3,7317,7317,quote=1
@bodhi:
Can you please help me with the boot environment settings to boot the original kernel from mtd1 of my Seagate Goflex Net with the new kernel?
-shv
Edited 1 time(s). Last edit at 10/28/2014 11:01AM by shv.
-------------------------------------------------------
> Interesting. But it's a good learning exeperience
> with JTAG. It would be nice if you can post your
> JTAG unbricking log and parts, setup …. :) when
> you find the time to do it.
Yes, I will do if I find some time. For most steps howto's are already available. For the time being: I've taken necessary information from the following links:
http://wiki.openwrt.org/toh/seagate/goflexnet
http://www.yourwarrantyisvoid.com/2010/09/08/dead-dockstar-resurrected-with-jtag/
http://forum.doozan.com/read.php?3,7317,7317,quote=1
@bodhi:
Can you please help me with the boot environment settings to boot the original kernel from mtd1 of my Seagate Goflex Net with the new kernel?
dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 02000000 00020000 "rootfs" mtd3: 0db00000 00020000 "data"
-shv
Edited 1 time(s). Last edit at 10/28/2014 11:01AM by shv.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 29, 2014 12:10AM |
Admin Registered: 13 years ago Posts: 18,543 |
@shv,
If you've installed directly from stock to the new u-boot, you've missed this. To boot stock kernel from davygravy's or jeff's u-boot:
But with the new u-boot, you can do the same. If you have saved mtd0 then: mount NAND rootfs mtd2, copy that u-boot image to the / directory of mtd2. And in serial console try to run pogo_bootcmd.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
If you've installed directly from stock to the new u-boot, you've missed this. To boot stock kernel from davygravy's or jeff's u-boot:
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fiJeff's script copies the orginal u-boot to NAND rootfs. The above pogo_bootmcd will load u-boot from mtd2 and that will boot uImage (mtd1). And then the mtd1 uImage will mount the NAND rootfs.
But with the new u-boot, you can do the same. If you have saved mtd0 then: mount NAND rootfs mtd2, copy that u-boot image to the / directory of mtd2. And in serial console try to run pogo_bootcmd.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 29, 2014 02:40PM |
Registered: 11 years ago Posts: 214 |
|
Juan C. Galvez
OenWRT doesn't boot. October 29, 2014 05:38PM |
Hi bodhi and excuses for the delay in posting my environment and booting messages. I didn't have my Pogoplug V4 device. Now I have a Dockstar GoFlex NET to test an thwse are the results:
The same USB memory stick boots in another Goflex NET with davygravy's uboot.
The partition is formated as ext3.
This is the environment of my device:
I intentionally removed my device MAC Address (you know).
This is the kernet boot process:
The same USB memory stick boots in another Goflex NET with davygravy's uboot.
The partition is formated as ext3.
This is the environment of my device:
GoFlexNet> printenv arcNumber=3089 baudrate=115200 bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset 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 ethaddr=<removed> if_netconsole=ping $serverip ipaddr=192.168.2.89 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 mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) partition=nand0,2 preboot=run preboot_nc preboot_nc=run if_netconsole start_netconsole 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 serverip=192.168.2.166 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 Environment size: 2230/131068 bytes GoFlexNet>
I intentionally removed my device MAC Address (you know).
This is the kernet boot process:
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:35:50)
Seagate GoFlex Net
SoC: Kirkwood 88F6281_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
No link on egiga0
ping failed; host 192.168.2.166 is not alive
Hit any key to stop autoboot: 0
(Re)start 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
1680910 bytes read in 307 ms (5.2 MiB/s)
** File not found /boot/uInitrd **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: ARM OpenWrt Linux-3.10.36
Created: 2014-05-02 19:08:23 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1680846 Bytes = 1.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.10.36 (debian@Debian) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.01 r40593) ) #2 Fri May 2 14:04:27 EDT 2014
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Marvell Kirkwood (Flattened Device Tree), model: Seagate FreeAgent Dockstar
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 124916k/124916k available, 6156k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0455dbc (4408 kB)
[ 0.000000] .init : 0xc0456000 - 0xc047cabc ( 155 kB)
[ 0.000000] .data : 0xc047e000 - 0xc04a77a0 ( 166 kB)
[ 0.000000] .bss : 0xc04a77a0 - 0xc04d8114 ( 195 kB)
[ 0.000000] NR_IRQS:114
[ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
[ 1.891147] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[ 1.981138] pid_max: default: 32768 minimum: 301
[ 1.981245] Mount-cache hash table entries: 512
[ 1.982900] CPU: Testing write buffer coherency: ok
[ 1.983227] Setting up static identity map for 0xc0010800 - 0xc001083c
[ 1.984848] pinctrl core: initialized pinctrl subsystem
[ 1.985708] regulator-dummy: no parameters
[ 1.986073] NET: Registered protocol family 16
[ 1.986497] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 1.989007] Kirkwood: MV88F6281-A1, TCLK=200000000.
[ 1.989026] Feroceon L2: Enabling L2
[ 1.989064] Feroceon L2: Cache support initialised.
[ 1.993738] No ATAGs?
[ 2.005000] bio: create slab <bio-0> at 0
[ 2.005856] USB Power: Failed to request enable GPIO29: -517
[ 2.006022] reg-fixed-voltage 1.regulator: Failed to register regulator: -517
[ 2.006042] platform 1.regulator: Driver reg-fixed-voltage requests probe deferral
[ 2.006807] SCSI subsystem initialized
[ 2.007819] usbcore: registered new interface driver usbfs
[ 2.007969] usbcore: registered new interface driver hub
[ 2.008146] usbcore: registered new device driver usb
[ 2.009575] NET: Registered protocol family 23
[ 2.009734] Switching to clocksource orion_clocksource
[ 2.009842] FS-Cache: Loaded
[ 2.011804] NET: Registered protocol family 2
[ 2.012196] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[ 2.012231] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 2.012250] TCP: Hash tables configured (established 1024 bind 1024)
[ 2.012299] TCP: reno registered
[ 2.012311] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 2.012331] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 2.012462] NET: Registered protocol family 1
[ 2.014198] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 2.014357] FS-Cache: Netfs 'cifs' registered for caching
[ 2.014413] Key type cifs.spnego registered
[ 2.014454] Key type cifs.idmap registered
[ 2.014466] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 2.014895] msgmni has been set to 243
[ 2.016185] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 2.016197] io scheduler noop registered
[ 2.016204] io scheduler deadline registered (default)
[ 2.016883] kirkwood-pinctrl f1010000.pinctrl: registered pinctrl driver
[ 2.100140] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 2.101425] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[ 2.497714] console [ttyS0] enabled
[ 2.506074] loop: module loaded
[ 2.510787] ONFI param page 0 valid
[ 2.514296] ONFI flash detected
[ 2.517459] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08AAD), 256MiB, page size: 2048, OOB size: 64
[ 2.528571] Scanning device for bad blocks
[ 2.685194] 4 cmdlinepart partitions found on MTD device orion_nand
[ 2.691498] Creating 4 MTD partitions on "orion_nand":
[ 2.696662] 0x000000000000-0x000000100000 : "u-boot"
[ 2.702634] 0x000000100000-0x000000500000 : "uImage"
[ 2.708484] 0x000000500000-0x000002500000 : "rootfs"
[ 2.714404] mtd: device 2 (rootfs) set to be root filesystem
[ 2.720190] __nand_correct_data: uncorrectable ECC error
[ 2.725349] mtdsplit: error occured while reading from "orion_nand"
[ 2.731837] 0x000002500000-0x000010000000 : "data"
[ 2.738764] libphy: orion_mdio_bus: probed
[ 2.743603] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 2.751669] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:26:6c:88
[ 2.760722] usbcore: registered new interface driver mcs7780
[ 2.766540] usbcore: registered new interface driver dm9601
[ 2.772289] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[ 2.779895] usbcore: registered new interface driver qmi_wwan
[ 2.785671] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.792242] ehci-pci: EHCI PCI platform driver
[ 2.796834] ehci-orion: EHCI orion driver
[ 2.800965] orion-ehci f1050000.ehci: EHCI Host Controller
[ 2.806498] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 2.814299] orion-ehci f1050000.ehci: irq 19, io mem 0xf1050000
[ 2.839767] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 2.845869] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.852704] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.859970] usb usb1: Product: EHCI Host Controller
[ 2.864868] usb usb1: Manufacturer: Linux 3.10.36 ehci_hcd
[ 2.870390] usb usb1: SerialNumber: f1050000.ehci
[ 2.875700] hub 1-0:1.0: USB hub found
[ 2.879485] hub 1-0:1.0: 1 port detected
[ 2.883978] usbcore: registered new interface driver usblp
[ 2.889635] usbcore: registered new interface driver cdc_wdm
[ 2.895536] usbcore: registered new interface driver usb-storage
[ 2.901878] usbcore: registered new interface driver usbserial
[ 2.907859] usbcore: registered new interface driver usbserial_generic
[ 2.914553] usbserial: USB Serial support registered for generic
[ 2.920729] usbcore: registered new interface driver cypress_m8
[ 2.926794] usbserial: USB Serial support registered for DeLorme Earthmate USB
[ 2.934188] usbserial: USB Serial support registered for HID->COM RS232 Adapter
[ 2.941738] usbserial: USB Serial support registered for Nokia CA-42 V2 Adapter
[ 2.949206] usbcore: registered new interface driver option
[ 2.954941] usbserial: USB Serial support registered for GSM modem (1-port)
[ 2.962223] usbcore: registered new interface driver qcserial
[ 2.968122] usbserial: USB Serial support registered for Qualcomm USB modem
[ 2.975406] i2c /dev entries driver
[ 2.979318] usbcore: registered new interface driver i2c-tiny-usb
[ 2.986508] orion_wdt: Initial timeout 21 sec
[ 2.991040] cpuidle: using governor ladder
[ 2.995829] leds-gpio gpio-leds.1: pins are not configured from the driver
[ 3.004114] TCP: cubic registered
[ 3.007449] NET: Registered protocol family 17
[ 3.012176] 8021q: 802.1Q VLAN Support v1.8
[ 3.016423] Key type dns_resolver registered
[ 3.020817] VFP support v0.3: not present
[ 3.025781] regulator-dummy: disabling
[ 3.030023] USB Power: 5000 mV
[ 3.033540] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 3.040240] Waiting 10sec before mounting root device...
[ 3.199775] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 3.351940] usb 1-1: New USB device found, idVendor=0951, idProduct=1665
[ 3.358685] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.365874] usb 1-1: Product: DataTraveler 2.0
[ 3.370352] usb 1-1: Manufacturer: Kingston
[ 3.374552] usb 1-1: SerialNumber: 001BFC3653D2FE10B94773B9
[ 3.381005] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 3.387278] scsi0 : usb-storage 1-1:1.0
[ 4.407287] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 4
[ 4.416971] sd 0:0:0:0: [sda] 15131636 512-byte logical blocks: (7.74 GB/7.21 GiB)
[ 4.424958] sd 0:0:0:0: [sda] Write Protect is off
[ 4.430208] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4.443367] sda: sda1
[ 4.447959] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 13.050965] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[ 13.058754] List of all partitions:
[ 13.062296] 1f00 1024 mtdblock0 (driver?)
[ 13.067401] 1f01 4096 mtdblock1 (driver?)
[ 13.072493] 1f02 32768 mtdblock2 (driver?)
[ 13.077589] 1f03 224256 mtdblock3 (driver?)
[ 13.082678] 0800 7565818 sda driver: sd
[ 13.087324] 0801 7565008 sda1 35fe23c1-01
[ 13.092231] No filesystem could mount root, tried: ext3
[ 13.097581] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 30, 2014 12:00AM |
Admin Registered: 13 years ago Posts: 18,543 |
shv,
Take alook at how the rescue system and the ubifs system is booted in the envs set by Jeff's script:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Take alook at how the rescue system and the ubifs system is booted in the envs set by Jeff's script:
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset 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 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 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
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OenWRT doesn't boot. October 30, 2014 12:08AM |
Admin Registered: 13 years ago Posts: 18,543 |
@Juan,
This is a typical rootfs mounting problem.
- Ensure your rootfs (/ partition) is formatted as Ext3, because your rootfstype env is:
rootfstype=ext3
- Label your rootfs (sdxx is the partition letter for you rootfs /) \. In Linux:
tune2fs -L rootfs /dev/sdxx
- Set your rootfs label in bootargs in serial console
setenv usb_root 'LABEL=rootfs'
If you have 2 partitions on your USB, then most likely the /boot partition was mistakenly mounted as rootfs. Therefore the error.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
This is a typical rootfs mounting problem.
- Ensure your rootfs (/ partition) is formatted as Ext3, because your rootfstype env is:
rootfstype=ext3
- Label your rootfs (sdxx is the partition letter for you rootfs /) \. In Linux:
tune2fs -L rootfs /dev/sdxx
- Set your rootfs label in bootargs in serial console
setenv usb_root 'LABEL=rootfs'
If you have 2 partitions on your USB, then most likely the /boot partition was mistakenly mounted as rootfs. Therefore the error.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 30, 2014 12:24PM |
Registered: 11 years ago Posts: 214 |
bodhi Wrote:
-------------------------------------------------------
> shv,
>
> 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
> [/code]
bodhi,
I don't think that this will work because there is no boot folder in rootfs(mtd2). Do you think that the nboot command could help to boot the kernel from mtd1? If yes which are the parameters?
e.g. nboot 0x800000 0 0x100000; bootm 0x800000
-shv
Edited 3 time(s). Last edit at 10/30/2014 12:44PM by shv.
-------------------------------------------------------
> shv,
>
> 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
> [/code]
bodhi,
I don't think that this will work because there is no boot folder in rootfs(mtd2). Do you think that the nboot command could help to boot the kernel from mtd1? If yes which are the parameters?
e.g. nboot 0x800000 0 0x100000; bootm 0x800000
-shv
Edited 3 time(s). Last edit at 10/30/2014 12:44PM by shv.
|
Juan C Galvez
Re: OenWRT doesn't boot. October 30, 2014 02:00PM |
@bodhi.
Thank you for your reply.
I fact there is only one USB memory stck with only one partition.
I did what you sugested but it didn't work.
It is curious. If i set this environment variables it works with OpenWRT but stops working with Debian:
Juan C.
Thank you for your reply.
I fact there is only one USB memory stck with only one partition.
I did what you sugested but it didn't work.
It is curious. If i set this environment variables it works with OpenWRT but stops working with Debian:
setenv bootcmd_usb 'run usb_init\; run usb_load_uimage\; run set_bootargs_usb\; bootm 0x800000\;' setenv usb_init 'usb start' setenv usb_load_uimage 'mw 0x800000 0 1\; ext2load usb $device 0x800000 /boot/uImage' setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$usb_rootfstype $mtdparts' boot
Juan C.
|
Re: OenWRT doesn't boot. October 30, 2014 02:49PM |
Admin Registered: 13 years ago Posts: 18,543 |
@Juan C
Ah! I'm not familiar with OpenWRT so did not know that it boots only with uImage. This should boot with Debian, OpenWRT, and Arch:
Add load_initrd, and modify bootcmd_usb:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 10/30/2014 02:58PM by bodhi.
Ah! I'm not familiar with OpenWRT so did not know that it boots only with uImage. This should boot with Debian, OpenWRT, and Arch:
Add load_initrd, and modify bootcmd_usb:
setenv usb_load_initrd 'ext2load usb $device 0x1100000 /boot/uInitrd' setenv bootcmd_usb 'run usb_init; run set_bootargs_usb; run usb_load_uimage; if run usb_load_initrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 10/30/2014 02:58PM by bodhi.
|
Juan C Galvez
Re: OenWRT doesn't boot. October 30, 2014 06:15PM |
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 31, 2014 03:17AM |
Admin Registered: 13 years ago Posts: 18,543 |
shv,
Something similar to this:
Consider this about the rescue system: similar to the original kernel uImage.
Sorry I can't be more specific. I'm just not interested in booting Popo OS so never thought about this much, if at all :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/31/2014 03:21AM by bodhi.
Something similar to this:
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
Consider this about the rescue system: similar to the original kernel uImage.
Sorry I can't be more specific. I'm just not interested in booting Popo OS so never thought about this much, if at all :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/31/2014 03:21AM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 31, 2014 09:03AM |
Registered: 11 years ago Posts: 214 |
Seams to be not possible to boot the old original kernel:
Edited 11 time(s). Last edit at 10/31/2014 01:29PM by shv.
GoFlexNet> nboot 0x800000 0 0x100000; bootm 0x800000 Loading from nand0, offset 0x100000 Image Name: Linux-2.6.22.18 Created: 2010-10-19 23:05:02 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1979140 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.22.18 Created: 2010-10-19 23:05:02 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1979140 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux............................................................ ................................................................ done, booting the kernel.
GoFlexNet> nand read.e 0x800000 0x100000 0x400000; bootm 0x800000 NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OK ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-2.6.22.18 Created: 2010-10-19 23:05:02 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1979140 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux............................................................ ................................................................ done, booting the kernel.
GoFlexNet> if fsload uboot-original-mtd0.kwb; then go 0x800200; fi ### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000 Scanning JFFS2 FS: ........ done. ### JFFS2 load complete: 524288 bytes loaded to 0x800000 ## Starting application at 0x00800200 ...-shv
Edited 11 time(s). Last edit at 10/31/2014 01:29PM by shv.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile October 31, 2014 05:11PM |
Admin Registered: 13 years ago Posts: 18,543 |
shv,
In the first 2 tries, the bootargs might have something to do with it not being able to go further. There are 3 possibilities:
1. bootargs variable was set explicitly in the envs in stock.
2. bootargs variable was set by stock u-boot internally (bootargs env might be undefined).
3. bootargs are hardcoded in stock kernel, so it does not matter what the bootargs content is (bootargs env might be undefined).
In 1, you can find bootargs env in stock GoFlex Net. In 2 and 3, you can find out about the bootagrs by looking at a stock GoFlex Net envs using serial console. Or you can look in GPL code for both 2 and 3.
You are booting with the new u-boot, so I think it is very likely that the bootargs variable is not matching with what stock kernel expects.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/31/2014 05:13PM by bodhi.
In the first 2 tries, the bootargs might have something to do with it not being able to go further. There are 3 possibilities:
1. bootargs variable was set explicitly in the envs in stock.
2. bootargs variable was set by stock u-boot internally (bootargs env might be undefined).
3. bootargs are hardcoded in stock kernel, so it does not matter what the bootargs content is (bootargs env might be undefined).
In 1, you can find bootargs env in stock GoFlex Net. In 2 and 3, you can find out about the bootagrs by looking at a stock GoFlex Net envs using serial console. Or you can look in GPL code for both 2 and 3.
You are booting with the new u-boot, so I think it is very likely that the bootargs variable is not matching with what stock kernel expects.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/31/2014 05:13PM by bodhi.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 01, 2014 02:21AM |
Registered: 11 years ago Posts: 214 |
bodhi,
I found a backup of Goflex Net Stock uboot envs:
Edited 2 time(s). Last edit at 11/01/2014 02:29AM by shv.
I found a backup of Goflex Net Stock uboot envs:
baudrate=115200 loads_echo=0 ipaddr=169.254.254.253 serverip=169.254.254.254 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 run_diag=yes console=console=ttyS0,115200 CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=root=/dev/mtdblock2 ro ethmtu=1500 usb0Mode=host nandEcc=1bit ethact=egiga0 stdin=serial stdout=serial stderr=serial nandEnvBase=a0000 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 bootdelay=3 disaMvPnp=no pcieTune=no ethaddr=xx:xx:xx:xx:xx:xx cesvcid=XXXXXXXXXXXXXXXXXXXXXXXXXXX ceserialno=XXXXXXX ceboardver=DISCOVERY:0.1 bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000If I added the missing variables to the environment in RAM but not flashed them. I also deleted arcNumber in RAM. Afterwards I tried to start the kernel using the same commands as before. I also tried to use the bootcmd from the last line. The result was the same as before.
Edited 2 time(s). Last edit at 11/01/2014 02:29AM by shv.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 01, 2014 03:28AM |
Admin Registered: 13 years ago Posts: 18,543 |
shv,
Have you tried these? mainlineLinux=no is relevant:
If this does not boot, the next thing you can do is to create a script to set all these envs before booting stock kernel. I'll post instruction for that if you can't still boot with these envs.
UPDATE:
You also need stock mtdparts definition (are they the same as the new definition?), because of this:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
a backup of Goflex Net Stock uboot envsVery encouraging.
Have you tried these? mainlineLinux=no is relevant:
mainlineLinux=no console=console=ttyS0,115200 bootargs_root=root=/dev/mtdblock2 ro bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000
If this does not boot, the next thing you can do is to create a script to set all these envs before booting stock kernel. I'll post instruction for that if you can't still boot with these envs.
UPDATE:
You also need stock mtdparts definition (are they the same as the new definition?), because of this:
bootargs_root=root=/dev/mtdblock2 ro
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 01, 2014 09:53AM |
Registered: 11 years ago Posts: 214 |
I just recovered to the original uboot to find out the definition of stock mtd parts.
Edited 8 time(s). Last edit at 11/01/2014 10:36AM by shv.
-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"It is the same as the new definition. But it seams that the original environment variables are at a different location.
-sh-3.2# cat /etc/fw_env.config # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundant # environment sector is assumed present. # Notice, that the "Number of sectors" is ignored on NOR. # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000The command fw_printenv prints the Debian environment and blparm prints the environment of the original uboot/PogoOS which is also printed with printenv if I stop the original uboot. Both environments are different. I think the original environment is located at a different memory address, e.g. 0xa0000. Moreover it has a different format and/or checksum because I can't print it with fw_printenv if I change Device offset to 0xa0000 in /etc/fw_env.config.
Edited 8 time(s). Last edit at 11/01/2014 10:36AM by shv.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 01, 2014 04:13PM |
Admin Registered: 13 years ago Posts: 18,543 |
Quote
I think the original environment is located at a different memory address, e.g. 0xa0000. Moreover it has a different format and/or checksum because I can't print it with fw_printenv if I change Device offset to 0xa0000 in /etc/fw_env.config
Correct, they are at different location, and use different checksum. So running original u-boot, you'll need 0xa0000 and blparam. That's the good thing about choosing 0xC0000 for new envs, e.g. you can switch back to stock easily by loading orginal u-boot and run it.
However, new u-boot is too different from stock, chain loading might or might not work. So you could try starting the new u-boot as normal, and in serial console, set the envs to exactly the same as stock and then boot the kernel. If the bootargs env was not hard-coded, most likely it will work.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 03, 2014 11:47AM |
Registered: 11 years ago Posts: 214 |
Also with envs set exactly to the same as stock env the kernel didn't boot. I will not continue trying to find a solution to boot the old kernel/rootfs anymore.
In the meantime I made some pictures of the JTAG interface:
http://pogoplug.cwsurf.de/jlink.jpg
http://pogoplug.cwsurf.de/customadapter.jpg
http://pogoplug.cwsurf.de/goflexnetjlink.jpg
-shv
Edited 2 time(s). Last edit at 11/03/2014 12:01PM by shv.
In the meantime I made some pictures of the JTAG interface:
http://pogoplug.cwsurf.de/jlink.jpg
http://pogoplug.cwsurf.de/customadapter.jpg
http://pogoplug.cwsurf.de/goflexnetjlink.jpg
-shv
Edited 2 time(s). Last edit at 11/03/2014 12:01PM by shv.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 04, 2014 01:23AM |
Admin Registered: 13 years ago Posts: 18,543 |
Thanks shv, it will come in handy someday!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 04, 2014 10:43AM |
Registered: 9 years ago Posts: 11 |
Hi bodhi,
i really don't wanna mess this thread up, but before flashing to NAND i wanna ensure, that the following two bad blocks are harmless. Can you confirm?
EDIT: Everything's fine. Found the answer in an older post from you. Link Keep on hacking :)
Edited 1 time(s). Last edit at 11/04/2014 10:49AM by Eike.
i really don't wanna mess this thread up, but before flashing to NAND i wanna ensure, that the following two bad blocks are harmless. Can you confirm?
root@debian:/# dmesg | grep -i 'bad' [ 11.985410] Scanning device for bad blocks [ 11.994858] Bad eraseblock 100 at 0x000000c80000 [ 12.004771] Bad eraseblock 200 at 0x000001900000Thanks, Eike
EDIT: Everything's fine. Found the answer in an older post from you. Link Keep on hacking :)
Edited 1 time(s). Last edit at 11/04/2014 10:49AM by Eike.
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 06, 2014 04:22PM |
Admin Registered: 13 years ago Posts: 18,543 |
Eike Wrote:
-------------------------------------------------------
> Hi bodhi,
>
> i really don't wanna mess this thread up, but
> before flashing to NAND i wanna ensure, that the
> following two bad blocks are harmless. Can you
> confirm?
You never did :) questions and answers are great (as long as not troubleshooting).
> root@debian:/# dmesg | grep -i 'bad'
> [ 11.985410] Scanning device for bad blocks
> [ 11.994858] Bad eraseblock 100 at
> 0x000000c80000
> [ 12.004771] Bad eraseblock 200 at
> 0x000001900000
>
> Thanks, Eike
>
> EDIT: Everything's fine. Found the answer in an
> older post from you.
> [url=http://forum.doozan.com/read.php?3,12381,1743
> 3#msg-17433]Link[/url] Keep on hacking :)
Cool!
-bodhi
===========================
[color=#3333FF][url=http://forum.doozan.com/read.php?2,23630]Forum Wiki[/url][/color]
[url=https://mibodhi.blogspot.com]bodhi's corner (buy bodhi a beer)[/url]
-------------------------------------------------------
> Hi bodhi,
>
> i really don't wanna mess this thread up, but
> before flashing to NAND i wanna ensure, that the
> following two bad blocks are harmless. Can you
> confirm?
You never did :) questions and answers are great (as long as not troubleshooting).
> root@debian:/# dmesg | grep -i 'bad'
> [ 11.985410] Scanning device for bad blocks
> [ 11.994858] Bad eraseblock 100 at
> 0x000000c80000
> [ 12.004771] Bad eraseblock 200 at
> 0x000001900000
>
> Thanks, Eike
>
> EDIT: Everything's fine. Found the answer in an
> older post from you.
> [url=http://forum.doozan.com/read.php?3,12381,1743
> 3#msg-17433]Link[/url] Keep on hacking :)
Cool!
-bodhi
===========================
[color=#3333FF][url=http://forum.doozan.com/read.php?2,23630]Forum Wiki[/url][/color]
[url=https://mibodhi.blogspot.com]bodhi's corner (buy bodhi a beer)[/url]
|
Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile November 14, 2014 01:52AM |
Registered: 9 years ago Posts: 28 |
@bodhi,
i recently acquired a GFN to play with. I install Jeff's script in order to install uboot (http://projects.doozan.com/uboot/install_uboot_mtd0.sh) and Jeff's script again to install rescue system in the nand (http://jeff.doozan.com/debian/rescue/install_rescue.sh). With netconsole i saw that the uboot that was installed was 2011.xx .Rescue worked just fine with no usb attached. Also i managed to load your 3.17 rootfs from a usb thumb drive. When i tried to load from SATA no luck (of course i needed to set boot parameters) so at that point i decided to install your 2014.07 u-boot (familiar procedure after flashing my oxnas pogoplug). It booted fine with my usb thumb drive but no rescue boot, which makes sense since no appropriate paramaters are defined). Is it possible to be able to load Jeff''s rescue system at NAND when no other rootfs is found? If it helps, i have kept a backup of fw boot env config prior installing your U-BOOT. What i mostly want to ask if setting the following boot envs (as seen at Jeff's script):
i recently acquired a GFN to play with. I install Jeff's script in order to install uboot (http://projects.doozan.com/uboot/install_uboot_mtd0.sh) and Jeff's script again to install rescue system in the nand (http://jeff.doozan.com/debian/rescue/install_rescue.sh). With netconsole i saw that the uboot that was installed was 2011.xx .Rescue worked just fine with no usb attached. Also i managed to load your 3.17 rootfs from a usb thumb drive. When i tried to load from SATA no luck (of course i needed to set boot parameters) so at that point i decided to install your 2014.07 u-boot (familiar procedure after flashing my oxnas pogoplug). It booted fine with my usb thumb drive but no rescue boot, which makes sense since no appropriate paramaters are defined). Is it possible to be able to load Jeff''s rescue system at NAND when no other rootfs is found? If it helps, i have kept a backup of fw boot env config prior installing your U-BOOT. What i mostly want to ask if setting the following boot envs (as seen at Jeff's script):
fw_setenv rescue_installed 1 fw_setenv set_bootargs_rescue 'setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts' fw_setenv bootcmd_rescue 'run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000' fw_setenv bootcmd_pogo 'run bootcmd_rescue'will make the rescue system working again
Sorry, you can't reply to this topic. It has been closed.