Iomega ix4-200d U-boot needed
Posted by Reto
|
Iomega ix4-200d U-boot needed January 08, 2016 07:48AM |
Registered: 8 years ago Posts: 49 |
Hi,
I am a complete Linux noob and need an u-boot binary. Is there someone who could compile it for me? I need this one:
Line 148 in https://github.com/niamster/uboot-marvell-openrd-ultimate/blob/master/create_all_images.sh
Thanks in advance,
Reto
Edited 2 time(s). Last edit at 01/28/2016 02:51PM by Reto.
I am a complete Linux noob and need an u-boot binary. Is there someone who could compile it for me? I need this one:
u-boot-rd88f6281a_400rd_nand.binAs far as I can see this code should generate it? https://github.com/niamster/uboot-marvell-openrd-ultimate
Line 148 in https://github.com/niamster/uboot-marvell-openrd-ultimate/blob/master/create_all_images.sh
Thanks in advance,
Reto
Edited 2 time(s). Last edit at 01/28/2016 02:51PM by Reto.
|
Re: Who can compile an u-boot bin for me? January 09, 2016 02:53AM |
Admin Registered: 13 years ago Posts: 18,543 |
I could help you, but you should post more info about the box. So that it will help the community at large!
Hardware, model, all you know about the box.
system info
And whether you have serial console connected.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Hardware, model, all you know about the box.
system info
dmesg cat /proc/cpuinfo
And whether you have serial console connected.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 09, 2016 03:37PM |
Registered: 8 years ago Posts: 49 |
Hi bodhi,
Thank you for your answer. It is an Iomega ix4-200d. I accidentially erased the whole NAND.
vasichkin posted here that he had best results with u-boot-rd88f6281a_400rd_nand.bin: http://forum.doozan.com/read.php?3,12381,15570#msg-15570
I have a serial connection and am able to load an u-boot via kwboot.
Thanks for your help,
Reto
Thank you for your answer. It is an Iomega ix4-200d. I accidentially erased the whole NAND.
vasichkin posted here that he had best results with u-boot-rd88f6281a_400rd_nand.bin: http://forum.doozan.com/read.php?3,12381,15570#msg-15570
I have a serial connection and am able to load an u-boot via kwboot.
Thanks for your help,
Reto
|
Re: Who can compile an u-boot bin for me? January 10, 2016 02:02AM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto Wrote:
-------------------------------------------------------
> Hi bodhi,
>
> Thank you for your answer. It is an Iomega
> ix4-200d. I accidentially erased the whole NAND.
> vasichkin posted here that he had best results
> with u-boot-rd88f6281a_400rd_nand.bin:
> http://forum.doozan.com/read.php?3,12381,15570#msg
> -15570
>
> I have a serial connection and am able to load an
> u-boot via kwboot.
>
>
> Thanks for your help,
>
> Reto
Try kwboot with latest Sheevaplug u-boot-2015 from my uboot release thread
http://forum.doozan.com/read.php?3,12381
Sheevaplug is a better reference board. Same CPU and clock.
And pls post if you have more info about the ix4-200d. eg, memory, nand , sata, usb, dmesg from stock kernel...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi bodhi,
>
> Thank you for your answer. It is an Iomega
> ix4-200d. I accidentially erased the whole NAND.
> vasichkin posted here that he had best results
> with u-boot-rd88f6281a_400rd_nand.bin:
> http://forum.doozan.com/read.php?3,12381,15570#msg
> -15570
>
> I have a serial connection and am able to load an
> u-boot via kwboot.
>
>
> Thanks for your help,
>
> Reto
Try kwboot with latest Sheevaplug u-boot-2015 from my uboot release thread
http://forum.doozan.com/read.php?3,12381
Sheevaplug is a better reference board. Same CPU and clock.
And pls post if you have more info about the ix4-200d. eg, memory, nand , sata, usb, dmesg from stock kernel...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 10, 2016 02:07AM |
Admin Registered: 13 years ago Posts: 18,543 |
Also see this thread:
http://forum.doozan.com/read.php?2,22623
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
http://forum.doozan.com/read.php?2,22623
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 12, 2016 07:33AM |
Registered: 8 years ago Posts: 49 |
bodhi,
I loaded the Sheevaplug u-boot via kwboot. Does this look ok?
I now would like to flash this to NAND. Unfortuantely I am stuck. What I tried:
On the host system the IP is set:
But I cannot even ping it...
I also tried pinging from the other side, no response.
And yes, there is a cable in between the two... Any ideas what could be wrong here? Or another way how I could get the u-boot into NAND?
Edited 1 time(s). Last edit at 01/12/2016 08:01AM by Reto.
I loaded the Sheevaplug u-boot via kwboot. Does this look ok?
U-Boot 2015.10-tld-1 (Nov 08 2015 - 21:01:07 -0800) Marvell-Sheevaplug SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB (ECC not enabled) WARNING: Caches not enabled NAND: 32 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 PHY reset timed out 88E1116 Initialized on egiga0 Hit any key to stop autoboot: 0 Sheevaplug>
I now would like to flash this to NAND. Unfortuantely I am stuck. What I tried:
Sheevaplug> setenv serverip 10.0.0.1 Sheevaplug> setenv ipaddr 10.0.0.2 Sheevaplug> mw 0x800000 0xffff 0x100000 Sheevaplug> tftp 0x800000 uboot.2015.10-tld-1.sheevaplug.mtd0.kwb Using egiga0 device TFTP from server 10.0.0.1; our IP address is 10.0.0.2 Filename 'uboot.2015.10-tld-1.sheevaplug.mtd0.kwb'. Load address: 0x800000 Loading: T T T T T T T T T T Retry count exceeded; starting again
On the host system the IP is set:
eth0 Link encap:Ethernet Hardware Adresse D8:D3:85:04:F5:18
inet Adresse:10.0.0.1 Bcast:10.0.0.255 Maske:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:3662 (3.5 Kb)
Interrupt:17
But I cannot even ping it...
Sheevaplug> ping 10.0.0.1 Using egiga0 device ping failed; host 10.0.0.1 is not alive
I also tried pinging from the other side, no response.
And yes, there is a cable in between the two... Any ideas what could be wrong here? Or another way how I could get the u-boot into NAND?
Edited 1 time(s). Last edit at 01/12/2016 08:01AM by Reto.
|
Re: Who can compile an u-boot bin for me? January 12, 2016 01:42PM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
It looks OK, but you should not flash it to NAND until after you can boot into Debian with the ix4-200d DTB and verify that it works correctly!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It looks OK, but you should not flash it to NAND until after you can boot into Debian with the ix4-200d DTB and verify that it works correctly!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 12, 2016 02:11PM |
Registered: 8 years ago Posts: 49 |
|
Re: Who can compile an u-boot bin for me? January 12, 2016 11:21PM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto Wrote:
-------------------------------------------------------
> bodhi,
>
> my NAND is completely empty. As explained earlier
> I accidentally erased the WHOLE NAND. There is
> nothing left, so nothing to lose.
> Can I transfer the u-boot file via serial
> connection?
Of course, but if you booted into Debian/Arch or any Linux OS then the complete instruction is already in the u-boot thread (including u-boot default envs).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bodhi,
>
> my NAND is completely empty. As explained earlier
> I accidentally erased the WHOLE NAND. There is
> nothing left, so nothing to lose.
> Can I transfer the u-boot file via serial
> connection?
Of course, but if you booted into Debian/Arch or any Linux OS then the complete instruction is already in the u-boot thread (including u-boot default envs).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 13, 2016 09:56AM |
Registered: 8 years ago Posts: 49 |
But how should I boot a Linux OS if I have not even a working Ethernet connection? ...
I now managed to transfer the u-boot file via serial, flashed it to NAND but after reset nothing happens. Is there anything else I have to do after flashing? What I did:
wait for the transfer to complete...
Edited 2 time(s). Last edit at 01/14/2016 01:24PM by Reto.
I now managed to transfer the u-boot file via serial, flashed it to NAND but after reset nothing happens. Is there anything else I have to do after flashing? What I did:
mw 0x0800000 0xffff 0x100000 nand erase 0x0 0x100000 loadb 0x0800000 115200
wait for the transfer to complete...
nand write 0x0800000 0x0 0x100000 reset
Edited 2 time(s). Last edit at 01/14/2016 01:24PM by Reto.
|
Re: Who can compile an u-boot bin for me? January 13, 2016 10:39AM |
Admin Registered: 13 years ago Posts: 18,543 |
It is perfectly OK to boot any Linux distro with only serial console. See here to proceed:
http://forum.doozan.com/read.php?3,25144,25145#msg-25145
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
http://forum.doozan.com/read.php?3,25144,25145#msg-25145
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 13, 2016 01:00PM |
Registered: 8 years ago Posts: 49 |
|
Re: Who can compile an u-boot bin for me? January 14, 2016 12:01AM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
You don't really need to do anything special. u-boot runs in RAM (even though it resides in NAND).
- Create the 3.16 rootfs on a USB stick and plug it in.
- Load the sheevaplug u-boot-2015.10-tld-1with kwboot like you did
- At the serial console, interrupt u-boot and check the internals default env (this is different from the default envs in the envs image)
- Go ahead and boot
And post the serial console bootlog here if you wish.
I'd expect it will boot into Debian, but will not run as the ix4-200d. For that, you need to use the kernel 4.2 with the ix4-200d DTB file (see the link I posted previously). However, this attempt would be a quick way to assure that you can flash u-boot, upgrade kernel... do anything you want from a Linux prompt.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You don't really need to do anything special. u-boot runs in RAM (even though it resides in NAND).
- Create the 3.16 rootfs on a USB stick and plug it in.
- Load the sheevaplug u-boot-2015.10-tld-1with kwboot like you did
- At the serial console, interrupt u-boot and check the internals default env (this is different from the default envs in the envs image)
printenv
- Go ahead and boot
boot
And post the serial console bootlog here if you wish.
I'd expect it will boot into Debian, but will not run as the ix4-200d. For that, you need to use the kernel 4.2 with the ix4-200d DTB file (see the link I posted previously). However, this attempt would be a quick way to assure that you can flash u-boot, upgrade kernel... do anything you want from a Linux prompt.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 14, 2016 06:58AM |
Registered: 8 years ago Posts: 49 |
Thanks, I am one step further. However I am unable to get the ramdisk. I tried the "dpkg -i linux-image-4.2.0-kirkwood-tld-1_1.0_armel.deb" command but it is not working. I guess this is because I am on an amd64 system here...
My environment:
Edited 1 time(s). Last edit at 01/14/2016 10:23AM by Reto.
My environment:
Sheevaplug> printenv arcNumber=2097 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=10 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 load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-sheevaplug.dtb load_uimage=ext2load usb 0:1 0x800000 /boot/uImage mainlineLinux=yes mtdids=nand0=orion_nand partition=nand0,2 rootdelay=10 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=run load_dtb; run load_uimage; bootm 0x800000 - 0x1c00000 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: 1437/131068 bytes
Edited 1 time(s). Last edit at 01/14/2016 10:23AM by Reto.
|
Re: Who can compile an u-boot bin for me? January 14, 2016 07:49AM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
You dont have to upgrade the kernel yet. Boot with the 3.16 rootfs first. And then upgrade the kernel while logging in Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You dont have to upgrade the kernel yet. Boot with the 3.16 rootfs first. And then upgrade the kernel while logging in Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 14, 2016 07:54AM |
Registered: 8 years ago Posts: 49 |
|
Re: Who can compile an u-boot bin for me? January 14, 2016 12:17PM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto Wrote:
-------------------------------------------------------
> Ok, I think I got it now. I have 3.16 rootfs
> booting. I am getting a (initramfs) prompt... is
> this normal?
Reto,
No, it means that the rootfs was not mount successfuly. It is because the rootfstype mismacthed. The internal u-boot env for this was set as ext2. So:
- Reboot with kwboot again.
- At the serial console, interrupt u-boot and
- Go ahead and boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Ok, I think I got it now. I have 3.16 rootfs
> booting. I am getting a (initramfs) prompt... is
> this normal?
Reto,
No, it means that the rootfs was not mount successfuly. It is because the rootfstype mismacthed. The internal u-boot env for this was set as ext2. So:
- Reboot with kwboot again.
- At the serial console, interrupt u-boot and
setenv rootfstype ext3
- Go ahead and boot
boot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 15, 2016 09:37AM |
Registered: 8 years ago Posts: 49 |
Damn! Of course! Now it is booting from USB!!! :-)
Next step would be to try to flash u-boot to NAND by following this guide, right? http://forum.doozan.com/read.php?3,12381
I tried it but unfortunately it is not working. There is no output on the serial console after a cold start...
There are some differences to your guide in the mtds though. Could this be the problem?
Do I have to change the mtds first, and if yes how? Or do I have do change the flash erase/write commands?
Thanks,
Reto
Next step would be to try to flash u-boot to NAND by following this guide, right? http://forum.doozan.com/read.php?3,12381
I tried it but unfortunately it is not working. There is no output on the serial console after a cold start...
There are some differences to your guide in the mtds though. Could this be the problem?
# MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000
dev: size erasesize name mtd0: 00100000 00004000 "u-boot" mtd1: 00400000 00004000 "uImage" mtd2: 01b00000 00004000 "rootfs"
Do I have to change the mtds first, and if yes how? Or do I have do change the flash erase/write commands?
Thanks,
Reto
|
Re: Who can compile an u-boot bin for me? January 15, 2016 01:01PM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
Yes, before flashing u-boot, the mtds definition must be corrected. Since you don't care about stock OS, NAND can be partitioned in the similar way as the sheevaplug. As long as mtd0 is 1MB then u-boot will be OK (the ix4-200d NAND size is different from the sheevaplug so the mtdparts below is sightly different).
- Reboot with kwboot again.
- At the serial console, interrupt u-boot and
- Go ahead and boot
- After booting into Debian, verify the /etc/fw_env.config
- And mtds should show 3 correct size mtds here (1MB, 4MB, 27MB for a total of 32MB)
At this point you can flash both u-boot image and u-boot env image as instructed. Remember to follow the instruction closely and copy/paste the commands.
If you like to confirm everything is OK, post the entire log of the session above here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/15/2016 01:05PM by bodhi.
Yes, before flashing u-boot, the mtds definition must be corrected. Since you don't care about stock OS, NAND can be partitioned in the similar way as the sheevaplug. As long as mtd0 is 1MB then u-boot will be OK (the ix4-200d NAND size is different from the sheevaplug so the mtdparts below is sightly different).
- Reboot with kwboot again.
- At the serial console, interrupt u-boot and
setenv rootfstype ext3 setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)'
- Go ahead and boot
boot
- After booting into Debian, verify the /etc/fw_env.config
cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000
- And mtds should show 3 correct size mtds here (1MB, 4MB, 27MB for a total of 32MB)
cat /proc/cmdline cat /proc/mtd
At this point you can flash both u-boot image and u-boot env image as instructed. Remember to follow the instruction closely and copy/paste the commands.
If you like to confirm everything is OK, post the entire log of the session above here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/15/2016 01:05PM by bodhi.
|
Re: Who can compile an u-boot bin for me? January 19, 2016 02:08AM |
Registered: 8 years ago Posts: 49 |
Bodhi,
I am having no luck. Absolutely no output on the serial port... :-( What I did:
I see some differences in the erase results. Is this due to different unit sizes?
I am having no luck. Absolutely no output on the serial port... :-( What I did:
root@debian:/tools# ./flash_erase /dev/mtd0 0 4 Erase Total 4 Units Performing Flash Erase of length 16384 at offset 0xc000 done root@debian:/tools# ./nandwrite /dev/mtd0 uboot.2015.10-tld-1.sheevaplug.mtd0.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x4000 Writing data to block 2 at offset 0x8000 Writing data to block 3 at offset 0xc000 Writing data to block 4 at offset 0x10000 Writing data to block 5 at offset 0x14000 Writing data to block 6 at offset 0x18000 Writing data to block 7 at offset 0x1c000 Writing data to block 8 at offset 0x20000 Writing data to block 9 at offset 0x24000 Writing data to block 10 at offset 0x28000 Writing data to block 11 at offset 0x2c000 Writing data to block 12 at offset 0x30000 Writing data to block 13 at offset 0x34000 Writing data to block 14 at offset 0x38000 Writing data to block 15 at offset 0x3c000 Writing data to block 16 at offset 0x40000 Writing data to block 17 at offset 0x44000 Writing data to block 18 at offset 0x48000 Writing data to block 19 at offset 0x4c000 Writing data to block 20 at offset 0x50000 Writing data to block 21 at offset 0x54000 Writing data to block 22 at offset 0x58000 Writing data to block 23 at offset 0x5c000 Writing data to block 24 at offset 0x60000 Writing data to block 25 at offset 0x64000 Writing data to block 26 at offset 0x68000 Writing data to block 27 at offset 0x6c000 Writing data to block 28 at offset 0x70000 Writing data to block 29 at offset 0x74000 Writing data to block 30 at offset 0x78000 Writing data to block 31 at offset 0x7c000 root@debian:/tools# ./flash_erase /dev/mtd0 0xc0000 1 Erase Total 1 Units Performing Flash Erase of length 16384 at offset 0xc0000 done root@debian:/tools# ./nandwrite -s 786432 /dev/mtd0 uboot.environment Writing data to block 48 at offset 0xc0000 Writing data to block 49 at offset 0xc4000 Writing data to block 50 at offset 0xc8000 Writing data to block 51 at offset 0xcc000 Writing data to block 52 at offset 0xd0000 Writing data to block 53 at offset 0xd4000 Writing data to block 54 at offset 0xd8000 Writing data to block 55 at offset 0xdc000 root@debian:/tools# fw_setenv arcNumber 2097 root@debian:/tools# fw_setenv machid root@debian:/tools# fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)' root@debian:/tools# fw_printenv ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking 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; 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_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 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 arcNumber=2097 mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)
I see some differences in the erase results. Is this due to different unit sizes?
|
Re: Who can compile an u-boot bin for me? January 19, 2016 04:18AM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
The problem was due to mtdparts still defined incorrectly. You did not verify your mtdparts as instructed above. So repeat this procedure.
- Reboot with kwboot again.
- At the serial console, interrupt u-boot and
- Go ahead and boot
- After booting into Debian, verify the /etc/fw_env.config
- And print out mtds definition
Stop here and post the entire log of the session above (everything in your serial console log from the kwboot command).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 01/19/2016 04:21AM by bodhi.
The problem was due to mtdparts still defined incorrectly. You did not verify your mtdparts as instructed above. So repeat this procedure.
- Reboot with kwboot again.
- At the serial console, interrupt u-boot and
setenv rootfstype ext3 setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)'
- Go ahead and boot
boot
- After booting into Debian, verify the /etc/fw_env.config
cat /etc/fw_env.config
- And print out mtds definition
cat /proc/cmdline cat /proc/mtd
Stop here and post the entire log of the session above (everything in your serial console log from the kwboot command).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 01/19/2016 04:21AM by bodhi.
|
Re: Who can compile an u-boot bin for me? January 19, 2016 07:18AM |
Registered: 8 years ago Posts: 49 |
I'm sorry, I thought it looked ok... My bad...
Note: I changed the file system on my USB device to ext2
Note: I changed the file system on my USB device to ext2
linux-k858:/home/aos/kwboot-tool # ./kwboot -t /dev/ttyUSB0 -b uboot.2015.10-tld-1.sheevaplug.mtd0.kwb -p
Sending boot message. Please reboot the target...\
Sending boot image...
0 % [......................................................................]
1 % [......................................................................]
3 % [......................................................................]
5 % [......................................................................]
6 % [......................................................................]
8 % [......................................................................]
10 % [......................................................................]
11 % [......................................................................]
13 % [......................................................................]
15 % [......................................................................]
17 % [......................................................................]
18 % [......................................................................]
20 % [......................................................................]
22 % [......................................................................]
23 % [......................................................................]
25 % [......................................................................]
27 % [......................................................................]
29 % [......................................................................]
30 % [......................................................................]
32 % [......................................................................]
34 % [......................................................................]
35 % [......................................................................]
37 % [......................................................................]
39 % [......................................................................]
41 % [......................................................................]
42 % [......................................................................]
44 % [......................................................................]
46 % [......................................................................]
47 % [......................................................................]
49 % [......................................................................]
51 % [......................................................................]
53 % [......................................................................]
54 % [......................................................................]
56 % [......................................................................]
58 % [......................................................................]
59 % [......................................................................]
61 % [......................................................................]
63 % [......................................................................]
64 % [......................................................................]
66 % [......................................................................]
68 % [......................................................................]
70 % [......................................................................]
71 % [......................................................................]
73 % [......................................................................]
75 % [......................................................................]
76 % [......................................................................]
78 % [......................................................................]
80 % [......................................................................]
82 % [......................................................................]
83 % [......................................................................]
85 % [......................................................................]
87 % [......................................................................]
88 % [......................................................................]
90 % [......................................................................]
92 % [......................................................................]
94 % [......................................................................]
95 % [......................................................................]
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
U-Boot 2015.10-tld-1 (Nov 17 2015 - 23:01:16 -0800)
Marvell-Sheevaplug
SoC: Kirkwood 88F6281_A1
DRAM: 512 MiB (ECC not enabled)
WARNING: Caches not enabled
NAND: 32 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.
PHY reset timed out
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
Sheevaplug> setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)'
Sheevaplug> boot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
incorrect device type in data
Partition data not found!
1 bytes read in 112 ms (0 Bytes/s)
Found bootable drive on usb 0:1
2756040 bytes read in 194 ms (13.5 MiB/s)
6032465 bytes read in 409 ms (14.1 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.16.0-kirkwood-tld-2
Created: 2014-09-01 23:18:31 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2755976 Bytes = 2.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.16.0-kirkwood-tld-2
Created: 2014-09-01 23:18:48 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6032401 Bytes = 5.8 MiB
Load Address: 00000000
Entry Point: 00000000
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] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.16.0-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Marvell SheevaPlug Reference Board
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 505588K/524288K available (5441K kernel code, 397K rwdata, 1840K rodata, 257K init, 299K bss, 18700K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc07248b0 (7283 kB)
[ 0.000000] .init : 0xc0725000 - 0xc0765444 ( 258 kB)
[ 0.000000] .data : 0xc0766000 - 0xc07c975c ( 398 kB)
[ 0.000000] .bss : 0xc07c975c - 0xc08144dc ( 300 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:114
[ 0.000011] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[ 6.971542] Console: colour dummy device 80x30
[ 6.971569] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[ 7.061330] pid_max: default: 32768 minimum: 301
[ 7.061451] Security Framework initialized
[ 7.061519] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.061538] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.062392] Initializing cgroup subsys devices
[ 7.062454] Initializing cgroup subsys freezer
[ 7.062481] Initializing cgroup subsys net_cls
[ 7.062528] Initializing cgroup subsys blkio
[ 7.062623] CPU: Testing write buffer coherency: ok
[ 7.063071] Setting up static identity map for 0x5273f0 - 0x527448
[ 7.065374] devtmpfs: initialized
[ 7.069261] prandom: seed boundary self test passed
[ 7.073323] prandom: 100 self tests passed
[ 7.073353] pinctrl core: initialized pinctrl subsystem
[ 7.073858] regulator-dummy: no parameters
[ 7.074320] NET: Registered protocol family 16
[ 7.074767] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 7.075985] cpuidle: using governor ladder
[ 7.076011] cpuidle: using governor menu
[ 7.076149] Kirkwood: MV88F6281-A1, TCLK=200000000.
[ 7.076172] Feroceon L2: Enabling L2
[ 7.076211] Feroceon L2: Cache support initialised.
[ 7.112851] vgaarb: loaded
[ 7.113207] usbcore: registered new interface driver usbfs
[ 7.113284] usbcore: registered new interface driver hub
[ 7.113406] usbcore: registered new device driver usb
[ 7.114380] Switched to clocksource orion_clocksource
[ 7.152858] NET: Registered protocol family 2
[ 7.153817] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 7.153874] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 7.153926] TCP: Hash tables configured (established 4096 bind 4096)
[ 7.153993] TCP: reno registered
[ 7.154007] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 7.154029] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 7.154235] NET: Registered protocol family 1
[ 7.154606] RPC: Registered named UNIX socket transport module.
[ 7.154618] RPC: Registered udp transport module.
[ 7.154625] RPC: Registered tcp transport module.
[ 7.154632] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 7.154930] Unpacking initramfs...
[ 7.654812] Freeing initrd memory: 5884K (c1101000 - c16c0000)
[ 7.654945] NetWinder Floating Point Emulator V0.97 (double precision)
[ 7.656082] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 7.656151] audit: initializing netlink subsys (disabled)
[ 7.656203] audit: type=2000 audit(0.680:1): initialized
[ 7.657002] zbud: loaded
[ 7.657266] VFS: Disk quotas dquot_6.5.2
[ 7.657317] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 7.657875] NFS: Registering the id_resolver key type
[ 7.657938] Key type id_resolver registered
[ 7.657947] Key type id_legacy registered
[ 7.657972] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 7.657987] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 7.658152] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 7.658458] msgmni has been set to 998
[ 7.658615] Key type big_key registered
[ 7.660963] alg: No test for stdrng (krng)
[ 7.661080] bounce: pool size: 64 pages
[ 7.661145] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 7.661164] io scheduler noop registered
[ 7.661178] io scheduler deadline registered
[ 7.661341] io scheduler cfq registered (default)
[ 7.661765] mv_xor mv_xor.0: Marvell shared XOR driver
[ 7.694457] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 7.734445] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 7.734620] mv_xor mv_xor.1: Marvell shared XOR driver
[ 7.774445] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 7.814444] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 7.814874] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 7.815870] console [ttyS0] disabled
[ 7.835964] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[ 8.384254] console [ttyS0] enabled
[ 8.388995] nand: device found, Manufacturer ID: 0xec, Chip ID: 0x75
[ 8.395405] nand: Samsung NAND 32MiB 3,3V 8-bit
[ 8.399956] nand: 32MiB, SLC, page size: 512, OOB size: 16
[ 8.405487] Scanning device for bad blocks
[ 8.757590] 3 cmdlinepart partitions found on MTD device orion_nand
[ 8.763884] Creating 3 MTD partitions on "orion_nand":
[ 8.769068] 0x000000000000-0x000000100000 : "u-boot"
[ 8.774472] 0x000000100000-0x000000500000 : "uImage"
[ 8.779854] 0x000000500000-0x000002000000 : "rootfs"
[ 8.786177] libphy: Fixed MDIO Bus: probed
[ 8.808348] libphy: orion_mdio_bus: probed
[ 8.812584] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 8.819663] libphy: PHY orion-mdio-mii:00 not found
[ 8.824639] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 8.832975] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 8.839585] ehci-pci: EHCI PCI platform driver
[ 8.844125] ehci-orion: EHCI orion driver
[ 8.848269] orion-ehci orion-ehci.0: EHCI Host Controller
[ 8.853715] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 8.861483] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 8.884417] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 8.890551] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 8.897395] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 8.904669] usb usb1: Product: EHCI Host Controller
[ 8.909571] usb usb1: Manufacturer: Linux 3.16.0-kirkwood-tld-2 ehci_hcd
[ 8.916321] usb usb1: SerialNumber: orion-ehci.0
[ 8.921685] hub 1-0:1.0: USB hub found
[ 8.925535] hub 1-0:1.0: 1 port detected
[ 8.930335] mousedev: PS/2 mouse device common for all mice
[ 8.936470] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[ 8.942490] i2c /dev entries driver
[ 8.946964] hidraw: raw HID events driver (C) Jiri Kosina
[ 8.952738] drop_monitor: Initializing network drop monitor service
[ 8.959323] TCP: cubic registered
[ 8.962666] NET: Registered protocol family 17
[ 8.967286] Key type dns_resolver registered
[ 8.972282] registered taskstats version 1
[ 8.977225] libphy: PHY orion-mdio-mii:00 not found
[ 8.982153] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 8.990651] rtc-mv rtc-mv: setting system clock to 2016-01-19 13:14:25 UTC (1453209265)
[ 9.000611] Freeing unused kernel memory: 256K (c0725000 - c0765000)
Loading, please wait...
[ 9.075274] udevd[57]: starting version 175
[ 9.228269] mvsdio mvsdio: no pins associated
[ 9.244539] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 9.281010] libphy: PHY orion-mdio-mii:00 not found
[ 9.289514] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 9.406762] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 9.413519] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 9.422743] usb 1-1: Product: USB2.0 Hub
[ 9.428185] hub 1-1:1.0: USB hub found
[ 9.432247] hub 1-1:1.0: 4 ports detected
[ 9.438709] libphy: PHY orion-mdio-mii:00 not found
[ 9.443647] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 9.465210] libphy: PHY orion-mdio-mii:00 not found
[ 9.470161] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 9.714753] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[ 9.825624] usb 1-1.2: New USB device found, idVendor=125f, idProduct=de7a
[ 9.832544] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9.839921] usb 1-1.2: Product: ADATA USB Flash Drive
[ 9.845017] usb 1-1.2: Manufacturer: ADATA
[ 9.849134] usb 1-1.2: SerialNumber: 14B1311102300064
[ 9.858085] libphy: PHY orion-mdio-mii:00 not found
[ 9.863015] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 9.889834] SCSI subsystem initialized
[ 9.898157] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 9.904890] scsi0 : usb-storage 1-1.2:1.0
[ 9.909763] libphy: PHY orion-mdio-mii:00 not found
[ 9.915705] usbcore: registered new interface driver usb-storage
[ 9.922968] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 9.933021] usbcore: registered new interface driver uas
[ 10.905353] scsi 0:0:0:0: Direct-Access ADATA USB Flash Drive 1.00 PQ: 0 ANSI: 6
[ 10.942943] libphy: PHY orion-mdio-mii:00 not found
[ 10.948680] sd 0:0:0:0: [sda] 123480064 512-byte logical blocks: (63.2 GB/58.8 GiB)
[ 10.957195] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[ 10.965908] sd 0:0:0:0: [sda] Write Protect is off
[ 10.971149] sd 0:0:0:0: [sda] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[ 10.985650] sda: sda1
[ 10.991025] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 11.007860] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[ 20.696310] udevd[235]: starting version 175
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[....] Waiting for /dev to be fully populated...[ 21.160786] alg: hash: Test 3 failed for mv-sha1
[ 21.165526] 00000000: 10 bf d7 00 71 0b bb 83 3a 26 d0 97 13 05 99 f5
[ 21.171992] 00000010: 3a 92 53 3c
[ 21.223345] alg: hash: Test 1 failed for mv-hmac-sha1
[ 21.232216] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24
[ 21.244512] 00000010: b7 c3 16 0c
[ 21.252458] libphy: PHY orion-mdio-mii:00 not found
[ 21.261127] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
done.
[ ok ] Activating swap...done.
[....] Checking root file system...[ 22.297807] random: nonblocking pool is initialized
fsck from util-linux 2.20.1
rootfs: clean, 13252/3859072 files, 377930/15435004 blocks
done.
[ ok ] Loading kernel modules...done.
[ ok ] Cleaning up temporary files... /lib/init/rw.
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.20.1
done.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[....] Configuring network interfaces...[ 26.855982] NET: Registered protocol family 10
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Cannot find device "eth0"
Bind socket to interface: No such device
Failed to bring up eth0.
done.
[ ok ] Starting rpcbind daemon....
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1605 (syslogd)
. ok
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
[ ok ] Starting system message bus: dbus.
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting rpcbind daemon...[....] Already running..
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
1603 (klogd)
. ok
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemonTimeout reached while wating for return value
Could not receive return value from daemon process.
(warning).
Debian GNU/Linux 7 debian ttyS0
debian login: root
Password:
Last login: Mon Jan 18 23:31:33 PST 2016 on ttyS0
Linux debian 3.16.0-kirkwood-tld-2 #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014 armv5tel
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@debian:~# cat /etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000
root@debian:~# cat /proc/cmdline
console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)
root@debian:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00004000 "u-boot"
mtd1: 00400000 00004000 "uImage"
mtd2: 01b00000 00004000 "rootfs"
root@debian:~#
|
Re: Who can compile an u-boot bin for me? January 19, 2016 02:20PM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
It does look OK as far as mtd0 is concerned.
However, the instruction assume the NAND partition definition is like other Kirkwood plugs, where the block size is 128K.
So the block erase size is different. It means the u-boot flash instruction and the fw_env.config need to be adjusted. We'll need to confirm if the NAND erase block size is really 16K (0x4000). I think, to be sure you will need to see the mtd definition after booting to stock OS. If we can confirm that it is the right size, then I will post new instruction for flashing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It does look OK as far as mtd0 is concerned.
root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 root@debian:~# cat /proc/cmdline console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs) root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00004000 "u-boot"
However, the instruction assume the NAND partition definition is like other Kirkwood plugs, where the block size is 128K.
cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot"
So the block erase size is different. It means the u-boot flash instruction and the fw_env.config need to be adjusted. We'll need to confirm if the NAND erase block size is really 16K (0x4000). I think, to be sure you will need to see the mtd definition after booting to stock OS. If we can confirm that it is the right size, then I will post new instruction for flashing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 19, 2016 02:49PM |
Registered: 8 years ago Posts: 49 |
|
Re: Who can compile an u-boot bin for me? January 19, 2016 11:52PM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
Boot with kwboot again, interrupt u-boot and
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Boot with kwboot again, interrupt u-boot and
flinfo
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 20, 2016 01:36AM |
Registered: 8 years ago Posts: 49 |
|
Re: Who can compile an u-boot bin for me? January 20, 2016 04:55AM |
Admin Registered: 13 years ago Posts: 18,543 |
See if anything from this thread can confirm the size:
http://forum.doozan.com/read.php?2,22623,22623#msg-22623
If not, we'll gonna flash it based on current information. Your NAND is empty anyway! it can't hurt.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
http://forum.doozan.com/read.php?2,22623,22623#msg-22623
If not, we'll gonna flash it based on current information. Your NAND is empty anyway! it can't hurt.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Who can compile an u-boot bin for me? January 20, 2016 05:04AM |
Registered: 8 years ago Posts: 49 |
|
Re: Who can compile an u-boot bin for me? January 20, 2016 05:22AM |
Admin Registered: 13 years ago Posts: 18,543 |
Reto,
Let's try this:
And please post output here before reboot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/20/2016 05:47AM by bodhi.
Let's try this:
flash_erase /dev/mtd0 0 32 nandwrite /dev/mtd0 uboot.2015-tld-1.sheevaplug.mtd0.kwb flash_erase /dev/mtd0 0xc0000 8 nandwrite -s 786432 /dev/mtd0 uboot.2014.07-tld-3.environment.img
And please post output here before reboot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 01/20/2016 05:47AM by bodhi.
|
Re: Who can compile an u-boot bin for me? January 20, 2016 06:00AM |
Registered: 8 years ago Posts: 49 |
My result:
root@debian:/tools# ./flash_erase /dev/mtd0 0 32 Erase Total 32 Units Performing Flash Erase of length 16384 at offset 0x7c000 done root@debian:/tools# ./nandwrite /dev/mtd0 uboot.2015.10-tld-1.sheevaplug.mtd0.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x4000 Writing data to block 2 at offset 0x8000 Writing data to block 3 at offset 0xc000 Writing data to block 4 at offset 0x10000 Writing data to block 5 at offset 0x14000 Writing data to block 6 at offset 0x18000 Writing data to block 7 at offset 0x1c000 Writing data to block 8 at offset 0x20000 Writing data to block 9 at offset 0x24000 Writing data to block 10 at offset 0x28000 Writing data to block 11 at offset 0x2c000 Writing data to block 12 at offset 0x30000 Writing data to block 13 at offset 0x34000 Writing data to block 14 at offset 0x38000 Writing data to block 15 at offset 0x3c000 Writing data to block 16 at offset 0x40000 Writing data to block 17 at offset 0x44000 Writing data to block 18 at offset 0x48000 Writing data to block 19 at offset 0x4c000 Writing data to block 20 at offset 0x50000 Writing data to block 21 at offset 0x54000 Writing data to block 22 at offset 0x58000 Writing data to block 23 at offset 0x5c000 Writing data to block 24 at offset 0x60000 Writing data to block 25 at offset 0x64000 Writing data to block 26 at offset 0x68000 Writing data to block 27 at offset 0x6c000 Writing data to block 28 at offset 0x70000 Writing data to block 29 at offset 0x74000 Writing data to block 30 at offset 0x78000 Writing data to block 31 at offset 0x7c000 root@debian:/tools# ./flash_erase /dev/mtd0 0xc0000 8 Erase Total 8 Units Performing Flash Erase of length 16384 at offset 0xdc000 done root@debian:/tools# ./nandwrite -s 786432 /dev/mtd0 uboot.2014.07-tld-3.environment.img Writing data to block 48 at offset 0xc0000 Writing data to block 49 at offset 0xc4000 Writing data to block 50 at offset 0xc8000 Writing data to block 51 at offset 0xcc000 Writing data to block 52 at offset 0xd0000 Writing data to block 53 at offset 0xd4000 Writing data to block 54 at offset 0xd8000 Writing data to block 55 at offset 0xdc000 root@debian:/tools# fw_setenv arcNumber 2097 root@debian:/tools# fw_setenv machid root@debian:/tools# fw_printenv 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; 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_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 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 arcNumber=2097
