2017.07-2023.04 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug

@Bodhi,

I will try it then. Is there a list of features your kernel patch includes fo NSA325 devices?

I have one more question - booting your debian rootfs from USB (which I intend to use for updating the U-boot) shows me following bad blocks. However I don't know if it is safe to flash (if they are in the U-boot area - if I understand it)?

...
[    4.865759] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
[    4.872168] nand: Eon NAND 128MiB 3,3V 8-bit
[    4.876451] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    4.882145] Scanning device for bad blocks
[    4.891585] Bad eraseblock 100 at 0x000000c80000
[    4.901493] Bad eraseblock 200 at 0x000001900000
[    4.954432] Creating 9 MTD partitions on "orion_nand":
...

Thanks a lot,

Tomas



Edited 4 time(s). Last edit at 01/07/2015 04:56AM by safarik.

@Tomas,

> I will try it then. Is there a list of features
> your kernel patch includes fo NSA325 devices?
>

Not specific, they are common for all Kirkwood devices.

> [ 4.891585] Bad eraseblock 100 at
> 0x000000c80000
> [ 4.901493] Bad eraseblock 200 at
> 0x000001900000

These bad blocks are way out, not in first 1M, so it is safe to flash u-boot.

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

@bodhi,

I successfully updated the U-boot in my NSA-325v2 so I can firther experiment with kernels and debian installation.

U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_??
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0 
NSA325>

Thank you very much for your help and time,

Tomas

@Tomas,

Cool! Let us know your reslult.

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

I am running a patched 3.16.1 (NSA325v2) mainline Kernel (archlinuxarm patches) and debian wheezy from an usb-stick with the new u-boot. It took a while but it is working fine now. If you have question just ask.

regards balou

Hi,

few findings. Maybe you have some knowledge about it.

I tried booting debian wheezy kirkwood/netboot/marvell/openrd/ image and it boots to debian installer fine after setting U-boot variable machid to 690 (Marvell DB-88F6281-BP Development Board). Apparently arcNumber is not used anymore. Also if machid is not set linux kernel detects machine ID automatically correctly (0x0000118f for me).

Unfortunatelly network does not work. Debian image uses mv643xx_eth. And Bodhis image uses mv643xx_eth_port (which works correctly).

Also I am missing sw raid kernel module as I would like to setup raid. It seems that Bodhi kernel does have it. Also does anyone know if the U-boot version can boot from linux raid device?

It seems that modyfing Debian installer image with Bodhis kernel is still the easiest way to.

Also I am not sure it this still benlongs to this thread. Please redirect me in such case.

Thanks,

Tomas

@Tomas,

Also does anyone know if the U-boot version can boot from linux raid device?

No, U-Boot will not. If you want to use RAID, then the boot device should be USB, and then use RAID on SATA.

> Also I am not sure it this still benlongs to this
> thread. Please redirect me in such case.

Please post this topic on the kernel thread:
http://forum.doozan.com/read.php?2,12096

And any NSA325 specific issue in this thread:
http://forum.doozan.com/read.php?2,14351

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

Hi Bodhi,

maybe there is a small typo in your first post

B. Flashing default u-boot envs image

you wrote:
tar -xf uboot.2014.07-tld-2.environment.img.bodhi.tar

# this is wrong and you get error while untar
# the file you get on dropbox is:
# uboot.2014.07-tld-2.environment.bodhi.tar
# the right untar command should be:

tar -xf uboot.2014.07-tld-2.environment.bodhi.tar

pls check
greets joerg_999



Edited 3 time(s). Last edit at 01/10/2015 12:46PM by joerg_999.

Thanks joerg_999!

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

Hi Bodhi,

First of all, thanks for your effort on this project.
I followed your instruction but I couldn't boot into rescue again. Following is the info got from nc
Could you tell me what I did wrong or what I should do to fix it?

Thanks

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:10:10)
Seagate FreeAgent DockStar
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
Unknown command 'mmc' - try 'help'
Unknown command 'ide' - try 'help'

no USB devices available
Unknown command 'mmc' - try 'help'
Unknown command 'ide' - try 'help'
(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
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Unknown command 'mmc' - try 'help'
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Unknown command 'ide' - try 'help'
** Bad device ide 0 **
** Bad device ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...

U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:10:10)
Seagate FreeAgent DockStar
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 9
0
DockStar>

codier,

> I followed your instruction but I couldn't boot
> into rescue again.

Did you have rescue system running before? the u-boot envs setup for rescue system needs to the same as installed by Jeff's script. If you have flashed the new default envs, then the rescue system setup were erased.

- interrupt netconsle and get the envs listing:
printenv

- If you did replace the envs with new default envs then restore them on top of what you have:

These are rescue system related envs installed by Jeff's script:

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
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_installed=1
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
bootcmd=usb start; run force_rescue_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; reset

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

I think you are right. I were using 2014.07-tld-1.
I didn't put the original env back.

I have 2 dockstars. one can see it by using nc. I think because I add following env

fw_setenv if_netconsole 'ping $serverip'
fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'
fw_setenv preboot 'run if_netconsole start_netconsole'

the other one I didn't add above code so I can not even ping the device. Do I need to solder the serial cable to rescue it?

codier,


> I have 2 dockstars. one can see it by using nc. I
> think because I add following env
>
> fw_setenv if_netconsole 'ping $serverip'
> fw_setenv start_netconsole 'setenv ncip $serverip;
> setenv bootdelay 10; setenv stdin nc; setenv
> stdout nc; setenv stderr nc; version;'
> fw_setenv preboot 'run if_netconsole
> start_netconsole'
>
> the other one I didn't add above code so I can not
> even ping the device. Do I need to solder the
> serial cable to rescue it?

No need to. You can boot into Debian with USB, and use fw_setenv to set them. Use my rootfs from this thread (use version 3.16, which is simpler to setup).

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

Is it necessary to flash the default u-boot env when you update the U-Boot? All it seems to do for my Pogoplug v2 is brick it. I've done it in the past before and it bricked my pogo, and I did it again this time because I saw there was an updated U-Boot.

SIde note-

The reason I was updating again because I read in this thread about multi-drive configuration and maybe the new U-boot would sort out my multi hard drive booting problem. Pogoplug won't boot with more than 1 drive attached, even tried the whole label thing to no avail.
Hopefully it'll work after I fix the env parameters.



Edited 2 time(s). Last edit at 01/26/2015 06:34AM by hachigo.

hachigo,

> Is it necessary to flash the default u-boot env
> when you update the U-Boot? All it seems to do for
> my Pogoplug v2 is brick it.

No, it is not necessary. And the flashing instruction in the 1st post advised you not to do it if your current u-boot is from Jeff's script, or your u-boot env is already at 0xC0000 . Only flash it if you are installing from stock.

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



Edited 2 time(s). Last edit at 01/26/2015 06:50AM by bodhi.

Oh ok makes sense now. Thanks.

Hi Bodhi,

I already made your latest one which is 31 Oct 2014 version of 3.17
I will start from there and if I can boot in then I will my env. It's pain in the xxx as I really have hard time to use putty to check each env line.
is there any easy way to read the env?

Thanks

> No need to. You can boot into Debian with USB, and
> use fw_setenv to set them. Use
> my
> rootfs from this thread (use version 3.16,
> which is simpler to setup).

codier Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> I already made your latest one which is 31 Oct
> 2014 version of 3.17
> I will start from there and if I can boot in then
> I will my env. It's pain in the xxx as I really
> have hard time to use putty to check each env
> line.
> is there any easy way to read the env?
>
> Thanks
>
> > No need to. You can boot into Debian with USB,
> and
> > use fw_setenv to set them. Use
> >
> my
> > rootfs from this thread (use version
> 3.16,
> > which is simpler to setup).

I am not sure what you meant. Where are you at? Can you boot into Debian?

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

I mean fw_printenv.
Because I need to check the env so I am wonder if there is a easy way to compare the current env versus the old env.
In that case, I can compare the difference.

codier,

You need to tell us which Linux system you can boot into, or if you can't boot at all. For example, stock Pogo OS, Debian, Arch, rescue system .... They are slightly different when it comes to how to make fw_printenv and fw_setenv available... I am not sure I undertand what your current system is, and what you are trying to get to.

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

Hello,

I'm currently using the latest version of U-Boot for my Pogoplug v4 and am having a hard time figuring out why my SATA drive will not spin up. It is connected to the SATA port on the pogoplug(not USB).

I found that bootcmd_ide starts off with "ide reset". Stopping the auto-boot and typing "ide reset" manually results in

Reset IDE: ide_preinit failed

running "ide info" results in

IDE device 0: device type unknown
IDE device 1: device type unknown

There is only one SATA port on my pogoplug.

Should I try reflashing the current U-Boot to see if it fixes it or something else? FWIW: I cannot access the drive once in Linux either. It does not spin up or anything.

Oh speaking of that error, I googled it and saw that it's an issue where U-Boot is configured to look for two sata ports. If fixed in the source, it works fine but when I looked at the U-Boot source on github, it seemed fine. Not sure what the deal is.

Hi Bodhi,

Sorry for the confusion. I can use a USB to boot up. But I can not boot into rescue anymore.
Below is my fw_printenv
Could you tell me where I messed up?

Thanks

root@LinuxA:/# fw_printenv
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
baudrate=115200
bootcmd=run bootcmd_uenv; 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
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
partition=nand0,2
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
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
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; mmc rescan; ide reset; setenv uenv_loaded 0; for devtype in usb mmc 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 test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
arcNumber=2998
ethaddr=00:10:75:1A:3D:0C
serverip=192.168.2.106
ipaddr=192.168.2.108

Edited 1 time(s). Last edit at 01/27/2015 09:54PM by codier.

@codier

Looks like you did replace the envs with new default envs so you need to restore them on top of what you have:

These are rescue system related envs installed by Jeff's script. Use fw_setenv to set each of these at comand line.

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
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_installed=1
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi

And adjust the bootcmd back to booting with rescues option:

bootcmd=run bootcmd_uenv; run force_rescue_bootcmd; run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; run rescue_bootcmd; reset

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



Edited 1 time(s). Last edit at 01/27/2015 11:34PM by bodhi.

Mangix Wrote:
-------------------------------------------------------
> Hello,
>
> I'm currently using the latest version of U-Boot
> for my Pogoplug v4 and am having a hard time
> figuring out why my SATA drive will not spin up.
> It is connected to the SATA port on the
> pogoplug(not USB).
>
> I found that bootcmd_ide starts off with "ide
> reset". Stopping the auto-boot and typing "ide
> reset" manually results in
>
>

Reset IDE: ide_preinit failed

This indicates the HDD is not detected by u-boot at all. What type and model of this HDD and is it running normally on another computer?

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

It's a Seagate drive. It works fine. But as I said it does not even power on. Also, it's a 3.5 inch drive.

Mangix,

Quote

But as I said it does not even power on. Also, it's a 3.5 inch drive.

How do you connect it to the Pogo V4? using an enclosure? or a direct cable? if it's an 3.5" HDD, it needs its own power source.

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



Edited 2 time(s). Last edit at 01/28/2015 08:02AM by bodhi.

I bought a sata extension cable. It works in my computer but not on the pogoplug. It really sounds like the boot loader is not initializing it.

Mangix Wrote:
-------------------------------------------------------
> I bought a sata extension cable. It works in my
> computer but not on the pogoplug.

What type of Sata cable? It would be best to post link to the picture or spec.

> It really sounds
> like the boot loader is not initializing it.

I'd doubt that would be the case. I think it is most likely power issue. You could try with a bare 2.5" hdd to confirm.

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

Just tested a regular 2.5 inch drive. It works. Looks like this unit is not compatible with 3.5 inch drives :(.

It is. Separate power source is needed. 2 choices:

1. eSata enclosure
or
2. a cable directly connect to the port but the HDD draws power source from outside.


EDITED: wrong link for the cable (I can't seem to find the correct one on my bookmarks)

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



Edited 3 time(s). Last edit at 01/29/2015 04:33AM by bodhi.