It worked! Thank you very much bodhi! I just followed your step by step instruction and it worked right away.by zzbao - uBoot
I tried with one partition in ext4. but still not working. same problem, stop at "booting the kernel". here is the setting: autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run bootcmd_uenv; run bootcmd_sata; run dt_bootcmd_usb; reset bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; tby zzbao - uBoot
Hi, I am trying to boot from SATA port. But it freezes during booting. Here is the serial output: (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 Reset IDE: Bus 0: OK Device 0: Model: WDC WD2500BEVT-00A23T0 Firm: 01.01A01 Ser#: WD-WXB1A70X5232 Type: Hardby zzbao - uBoot
bodhi Wrote: > 2. Also, this is not right, since you have append the DTB to uImage. This is for booting with a separate DTB: > > usb_boot=run load_dtb; run load_uimage; if run > load_initrd; then bootm 0x800000 0x1100000 > 0x1c00000; else bootm 0x800000 - 0x1c00000; fi > change this to setenv usb_boot 'mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitby zzbao - Debian
I downloaded Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 followed the instructions to install it on a USB HD formated in ext4. my uboot env on pogo_e02 (uboot ver: U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)): arcNumber=3542 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_sby zzbao - Debian
Hi, I have a Pogo E02 flashed with old uboot (2011.12) from the Arch install. Now I try to change to new uboot and debian. but it has some bad blocks: # dmesg | grep -i 'bad' [ 14.706954] Scanning device for bad blocks [ 14.712020] Bad eraseblock 67 at 0x000000860000 [ 14.716820] Bad eraseblock 132 at 0x000001080000 [ 14.728687] Bad eraseblock 292 at 0x000002480000by zzbao - uBoot
Quote Yes it does boot either USB drive, or SATA drive as a normal rootfs. What shv said was for a specially prepared SATA drive to boot with U-boot image stored on the SATA drive. With this NAND u-boot, to boot from a USB drive while there is a SATA drive attached, what we needs to do is to set u-boot envs correctly so that the Pogo will boot the kernel on the USB drive, and mount the rootfs froby zzbao - uBoot
Hi, The boot drive works with other USB drivers, but if I plug in a SATA drive (ext4) with the Sata cable to the onboard Sata connector, it has this error during the boot: [ 3.933283] sd 2:0:0:0: 2001888 512-byte logical blocks: (1.02 GB/977 MiB) [ 3.942338] sd 2:0:0:0: Write Protect is off [ 3.948160] sd 2:0:0:0: No Caching mode page found [ 3.960074] sd 2:0:0:0: Asby zzbao - uBoot
Hi, bodhi, After saw shv's response, I realized I didn't have the right rootfs. So I read your poster again and found that I can have the 3.12.13 rootfs (I was thinking it was NOT rootfs, but a package like 3.15.3). So I put it on the USB drive, only changed fstab to use label. When B01 boots, it complains cannot find "classic" dtb in dts folder. So I used the correspondinby zzbao - uBoot
Thank you, bodhi. I found shv's rootfs. "debian-wheezy-pogoplugv3pro-shv.1.clean.tar.gz". On my ubuntu, I extract it to a EXT4 usb card and then modified network interfaces (MAC) and fstab. I changed type from ext2 to ext4 and commented out swap with use LABEL=rootfs in fstab. I also moved the dtb file to /boot/dts When I power up B01 with this USB drive, here is what I gotby zzbao - uBoot
Thanks! I think I got the uboot flashed: Pogo b01 is under Arch, I SSH from a ubuntu machine to carry out the commands. I followed step 5 to 10. every thing is the same as yours. but after reboot, I cannot boot with my previous Arch drive any more because uboot env changed. go through your Oxnas kernel builds and rootfs, It looks like I need to have b01 boot up in previous debian kerby zzbao - uBoot
Hi, I am trying to follow this instruction to update my B01 that currently on Arch. Under Arch, # cat /proc/mtd dev: size erasesize name mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit" mtd1: 00e00000 00020000 "boot" mtd2: 07200000 00020000 "rootfs" This is different from the instruction (mtd0 -> boot, mtd1 -> data). can I proceed? Alby zzbao - uBoot