to add to this, printenv works correctly from u-boot serial console.

jman,

> but i don't have any of the
> commands for reading/writing nand in my /usr/sbin
> folder.

See requirements 4 for the download links for those NAND tools. After flashing U-boot, there should be no ECC error.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for the help, it worked like a charm.

Hi,

I am trying to follow this instruction to update my B01 that currently on Arch.

Under Arch,
[root@alarm ~]# 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?

Also, I don't have /etc/fw_env.config file. But I have serial connection. I got this:

CE>> printenv
bootdelay=2
baudrate=115200
autoload=n
netmask=255.255.0.0
bootfile="uImage"
kernflmode=s
load_nand=nboot 60500000 0 200000
load_nand2=nboot 60500000 0 800000
boot=bootm 60500000
boot_nand=run load_nand boot || run load_nand2 boot
ethaddr=00:25:31:02:79:D9
cesvcid=JWSV43VKEXF2PQWPJDD3ZMM6Z6
ceboardver=PPV3
serverip=192.168.1.20
ipaddr=192.168.1.122
bootargs_stock=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes
load_custom_nand=nboot 60500000 0 500000
load_custom_nand2=nboot 60500000 0 B00000
boot_custom=run load_custom_nand boot || run load_custom_nand2 boot
bootcmd=run boot_custom
stdin=serial
stdout=serial
stderr=serial
bootargs=root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait mem=128M poweroutage=yes

Environment size: 887/131068 bytes

Currently, my B01 cannot boot unless plug in the Arch drive. the green LED flashing. U-Boot is ver 1.1.2. Can I flash the 2013.10 version in Arch?

Another question: I am going to install Debian Wheezy with bodhi's rootfs. Does it has FDT support? do I need to do step 9 and 10?

Thanks.

zzbao,

> This is different from the instruction (mtd0 ->
> boot, mtd1 -> data). can I proceed?

Yes.

> Also, I don't have /etc/fw_env.config file. But I
> have serial connection. I got this:

The rootfs already has this file.

> Currently, my B01 cannot boot unless plug in the
> Arch drive. the green LED flashing. U-Boot is ver
> 1.1.2. Can I flash the 2013.10 version in Arch?

Yes. See Requirement 4 for link to download NAND tools.

> Another question: I am going to install Debian
> Wheezy with bodhi's rootfs. Does it has FDT
> support? do I need to do step 9 and 10?
>

Yes, it is FDT. So step 9 and 10 are relevant.

So create the rootfs on a USB stick first, following the instruction in the rootfs/kernel thread. And then flash u-boot in Arch, following the instruction in the 1st post. Shutdown and boot with the new stick.

While installing u-boot, if there is any error or things don't go exactly as described in the instruction, don't reboot, and post the log here!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/01/2014 05:55PM by bodhi.

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 kernel to install the new kernel. So I have failed into cracks as I cannot boot B01 any more. Is there a way I can just copy the whole debian system on a USB drive on a ubuntu machine and then plug it in pogo b01, change some uboot env to boot up debian?

Can I use Ext4 for this drive? I guess the label should be "rootfs"?

zzbao,

> but after reboot, I cannot boot with my previous
> Arch drive any more because uboot env changed.

The envs were setup for Debian.

>
> go through your Oxnas kernel builds and rootfs, It
> looks like I need to have b01 boot up in previous
> debian kernel to install the new kernel. So I have
> failed into cracks as I cannot boot B01 any more.
> Is there a way I can just copy the whole debian
> system on a USB drive on a ubuntu machine and then
> plug it in pogo b01, change some uboot env to boot
> up debian?
>

Yes, prepare this rootfs in Ubuntu (rootfs file system is not architecture dependent). You can also boot Arch providing you change the bootm command to boot only uImage. If not sure how, list your env here after interrupting u-boot in serial console.

> Can I use Ext4 for this drive? I guess the label
> should be "rootfs"?

Yes, if you set the usbrootfstype env to Ext4. Should be rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 got in serial:

U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
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
1608496 bytes read in 365 ms (4.2 MiB/s)
6880879 bytes read in 912 ms (7.2 MiB/s)
7033 bytes read in 248 ms (27.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: kernel 3.2.0-4-kirkwood
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1608432 Bytes = 1.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: ramdisk 3.2.0-4-kirkwood
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6880815 Bytes = 6.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 6779a000, end 67e29e2f ... OK
Loading Device Tree to 67795000, end 67799b78 ... OK

Led: GREEN

Starting kernel ...


U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27)
Boot device: NAND
Attempting to set PLLA to 800 MHz ...
plla_ctrl0 : 0000030a
plla_ctrl1 : 00400000
plla_ctrl2 : 007f0068
plla_ctrl3 : 00000193

PLLA Set


U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNA .-->>from here it just reboot again like before. Keep cycling the boot sequence.

Here is my uboot env:

OX820 # printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_usb
bootdelay=10
console=console=ttyS0,115200n8
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext4load usb 0:1 0x62c00000 /boot/dts/ox820-pogoplug-classic.dtb
dt_load_initrd=ext4load usb 0:1 0x60e00000 /boot/uInitrd
dt_load_uimage=ext4load usb 0:1 0x60500000 /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dtb_addr=0x62c00000
ethact=mii0
ethaddr=00:25:31:02:79:d9
if_netconsole=ping $serverip
ipaddr=192.168.1.35
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot_nc=run if_netconsole start_netconsole
serverip=192.168.1.15
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_rootfstype=ext4
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10

Environment size: 1212/131068 bytes

Please help me. Should I try other rootfs?

My rootfs is compatible to the ALARM kernel and stock uboot in flash. You can see in you log is that a kirkwood kernel is loaded. You should use the rootfs form bodhi instead of mine Because you have already his new uboot. You can find it here in this forum.

zzbao,

Try this rootfs:
http://forum.doozan.com/read.php?2,16044

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 corresponding file from your 3.15.3. It boots! Then I followed your instruction through serial connection to update the kernel to 3.15.3. Thank you very much!

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: [sdc] 2001888 512-byte logical blocks: (1.02 GB/977 MiB)
[    3.942338] sd 2:0:0:0: [sdc] Write Protect is off
[    3.948160] sd 2:0:0:0: [sdc] No Caching mode page found
[    3.960074] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[    3.974356]  sdc: sdc1
[    3.981240] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[    4.183508]  sdb: sdb1 sdb2
[    4.193564] sd 1:0:0:0: [sdb] Attached SCSI disk
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.
[   13.309491] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
modprobe: module atkbd not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
modprobe: module ohci-hcd not found in modules.dep


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

my rootfs is on a 20G 2.5" HD with 2 partitions (the first one has rootfs), it is assigned as sdb1, sdb2. 2nd drive (probably sdc) is a vfat 1G USB drive for testing boot. The 3rd drive is a Sata 1T HD for data, connected through sata cable directly.

Interestingly, if I use a Sata/USB adaptor to connect the Sata drive, debian boots up fine and I can access the drive.

I know that the sata drive get recognized first during booting. Some systems boot up from Sata connection. Does this version of uboot support connecting a sata drive used for data only?

zzbao Wrote:
-------------------------------------------------------
> Does this version of uboot support
> connecting a sata drive used for data only?

No! But if you put the right stage1 bootloader and the right uboot to your SATA drive it might boot with them. You can't use the files which are provided here for Flash install. Moreover you must put the stage1 bootloader to your drive as it is done by OXNAS-SATA-Boot skript from ALARM forum. The uboot can be put to the filesystem of the first partition (Fat32 or ext4 depends on the stage1 loader).

I tested the following setups:
sda1: just für boot files like u-boot.img, u-boot.env, uImage, uInitrd (ext4 or fat32)
sda2: rootfs (ext3 or ext4)
sda3: linux swap partition
sda4: data (ext4)

or
sda1: rootfs including boot files (ext4)
sda2: linux swap partition
sda3: data (ext4)

For both setups you can use the same stage1 bootloader (u-boot-spl.bin) which reads the boot files from and stores boot environment to the first ext4 partition of the SATA drive. The device must support 512 Byte sector size either natively or by simulation.

u-boot files for SATA booting: http://pogoplug.square7.ch/ox820-sata-uboot.tar.gz (environment must be adapted with the serial console to boot the uImage and uInitrd files) - uImage, uInitrd and dtb file are for Pogoplug Pro - you might replace them with the right files of your kernel

Preparing SATA drive and storing u-boot-spl.bin alias stage1 to it: http://archlinuxarm.org/forum/viewtopic.php?f=55&t=2146&sid=f4dc4863e3a93822a4f9e925b3cbda45

You must execute the steps from the ALARM script until stage1 file (u-boot-spl.bin from my package must be used instead the provided stage1 file) is stored to the HDD.

You must adapt the following lines of the boot environment:

dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot
ide_set_bootargs=setenv bootargs root=/dev/sda1 rootfstype=ext4 console=ttyS0,115200 mem=128M

-shv



Edited 11 time(s). Last edit at 02/09/2017 02:24AM by shv.

I think we are talking apple and orange here!

Quote
zzbao
I know that the sata drive get recognized first during booting. Some systems boot up from Sata connection. Does this version of uboot support connecting a sata drive used for data only?

Quote
shv
But if you put the right stage1 bootloader and the right uboot to your SATA drive it might boot with them

@zzbbao,

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 from that drive. So pls get the listing of your envs and post here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi,
I was never able to boot from flash if a SATA device was connected. The device detected the SATA drive and tried to boot from it and never started booting from flash. I am not sure if I had to wait longer but it seamed to last forever even with new SATA drives. Maybe the drive must be prepared somehow to stop the SATA boot processing and jump to flash booting but I don't know how.

If you are using an initrd, you should be okay. The problem comes from the SATA always coming up prior to usb, thus taking /dev/sda

shv,

As Warhead said, there should be no problem booting USB when SATA is also attached, if the initrd is used (i.e. a roofs label is used for booting). While it's true that when the system is powered on, the boot ROM will find the SATA drive before it finds the USB drive, if the SATA drive is a normal drive then it will not consider booting from it, it will select NAND option and then boot USB (if the SATA drive does not have the first 2048 bytes formatted in a special way for booting from ROM, then it is a normal drive).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Oh, I had no inference about the boot media. If the SATA is attached at boot, at all, it will take /dev/sda. If your SATA drive have the magic on it, you will need to configure the drive's environment appropriately, and ensure that the uboot on it has USB capability.

WarheadsSE Wrote:
-------------------------------------------------------
> Oh, I had no inference about the boot media. If
> the SATA is attached at boot, at all, it will take
> /dev/sda. If your SATA drive have the magic on it,
> you will need to configure the drive's environment
> appropriately, and ensure that the uboot on it has
> USB capability.

Yup. Totally agreed. I wanted to explain to shv in the above why booting USB drive while SATA drive attached will work: if the SATA drive has no magic dust (from WarheadsSE :) then it is a normal drive. So NAND u-boot will be used. And now it's up to how the u-boot envs are defined that either drives could be used to load uImage.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

If I want to remove the magic dust I must use the following command?

perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x200;
EOF

If I have some time I will try to boot from FLASH with a "clean" SATA drive attached.

Sounds about* right.






* That will likely work, but I have not tested it, and generally have simply zero'd the drive's first 1M prior, then repartitioned. That obviously might not be what you want to do.

Booting from internal FLASH with removed magic dust was possible. But the partition structure of the device was also destroyed.

Ouch! seems like this sector should be backup during installation and restored when you want to remove the booting capability.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

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 from that drive. So pls get the listing of your envs and post here.

That's good news for me! Here is my envs:

 
root@pogob01:~# fw_printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_usb
bootdelay=10
console=console=ttyS0,115200n8
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext4load usb 0:1 0x62c00000 /boot/dts/ox820-pogoplug-classic.dtb
dt_load_initrd=ext4load usb 0:1 0x60e00000 /boot/uInitrd
dt_load_uimage=ext4load usb 0:1 0x60500000 /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dtb_addr=0x62c00000
ethact=mii0
ethaddr=00:xx:xx:xx:xx:xx
if_netconsole=ping $serverip
ipaddr=192.168.1.35
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot_nc=run if_netconsole start_netconsole
serverip=192.168.1.15
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_rootfstype=ext4
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10

Yes, the SATA drive got sda and my rootfs got sdb. u-boot found the rootfs from sdb1, but there is error during boot up:

[   13.309491] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
modprobe: module atkbd not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
modprobe: module ohci-hcd not found in modules.dep


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

zzbao

To tell u-boot to select the correct rootfs on the USB drive. Do these:

1. Boot without the HDD, in Debian, name the partition label for the USB drive rootfs:

tune2fs -L rootfs /dev/sda1

2 .Change usb bootargs to:

fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10'

3. Shutdown

sync
shutdown -h now

4. Plug in the HDD, and power up.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello Bodhi,

after I am already using the uboot on my SATA disk. Now I want to try to flash it. Can you please provide a uboot-spl.img for 850MHz? Can you please write how to backup flash areas to be able to use them for recovery if neccessary some time?

-shv

Shv,

This u-boot-spl is for 800Mhz. Is this pogo capable of going up to 850 Mhz? has anybody done this and determined that it is stable?

See the instruction (step 3) for how to dump mtd0 to a file, the same command can be used for other mtds.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Bodhi,
yes, 850MHz works stable. I am using this frequency since more than 1,5 years 24/7.

-shv

Shv,

OK. I'll take a look.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@shv,

I've rebuilt the u-boot-spl image with 850Mhz clock. Just for my understanding, did you overclock it to 850 Mhz using WarheadsSE's stage1 image for that?

And also, are you running the new NAND u-boot with 800Mhz stage1 right now?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/07/2014 07:24PM by bodhi.