Welcome! Log In Create A New Profile

Advanced

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

Posted by bodhi 
Thanks for putting this together for us @bodhi, hope you are well ... I just upgraded successfully uboot to latest version on my GFN ... only issue is ethaddr :

root@GoFlexNet1:~/uboot# fw_setenv ethaddr 'XX:XX:XX:XX:XX:XX'
Can't overwrite "ethaddr"

Does setting the MAC address "correctly" matter ? ie can I just leave it with what it's set to ?

(next job is rootfs/kernel), so my uname -a is :

root@GoFlexNet1:~/uboot# uname -a
Linux GoFlexNet1 3.16.0-kirkwood-tld-3 #2 PREEMPT Sat Sep 27 02:01:41 PDT 2014 armv5tel GNU/Linux

(Wheezy)

I don't 100% understand the device tree stuff, but presumably once I try to boot new kernel from dropbox image, I will need to update the uboot to make it device tree aware ?
DonCharisma Wrote:
-------------------------------------------------------
> Thanks for putting this together for us @bodhi, ho
> pe you are well ... I just upgraded successfully u
> boot to latest version on my GFN ... only issue is
> ethaddr :
>
> root@GoFlexNet1:~/uboot# fw_setenv ethaddr 'XX:XX:
> XX:XX:XX:XX'
> Can't overwrite "ethaddr"
>
> Does setting the MAC address "correctly" matter ?
> ie can I just leave it with what it's set to ?
>
> (next job is rootfs/kernel), so my uname -a is :
>
> root@GoFlexNet1:~/uboot# uname -a
> Linux GoFlexNet1 3.16.0-kirkwood-tld-3 #2 PREEMPT
> Sat Sep 27 02:01:41 PDT 2014 armv5tel GNU/Linux
>
> (Wheezy)
>
> I don't 100% understand the device tree stuff, but
> presumably once I try to boot new kernel from drop
> box image, I will need to update the uboot to make
> it device tree aware ?

Hi Don :)

Good to see you posting again!

No need to worry, the latest uboot is FDT aware. The only thing to pay attention to is if you have flashed the default envs image that comes with the uboot image, it will automatically look for the DTB file in /boot/dts. This folder is populated when you install the kernel 4.10.0 (as instructed).

The default MAC address was randomly generated local MAC address, so it can be used w/o problem. But you should be able to change it after upgrading the ketnel to 4.10.0.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
bodhi Wrote:
-------------------------------------------------------
> DonCharisma Wrote:
> --------------------------------------------------
> -----
> > Thanks for putting this together for us @bodhi,
> ho
> > pe you are well ... I just upgraded successfully
> u
> > boot to latest version on my GFN ... only issue
> is
> > ethaddr :
> >
> > root@GoFlexNet1:~/uboot# fw_setenv ethaddr 'XX:X
> X:
> > XX:XX:XX:XX'
> > Can't overwrite "ethaddr"
> >
> > Does setting the MAC address "correctly" matter
> ?
> > ie can I just leave it with what it's set to ?
> >
> > (next job is rootfs/kernel), so my uname -a is :
> >
> > root@GoFlexNet1:~/uboot# uname -a
> > Linux GoFlexNet1 3.16.0-kirkwood-tld-3 #2 PREEMP
> T
> > Sat Sep 27 02:01:41 PDT 2014 armv5tel GNU/Linux
> >
> > (Wheezy)
> >
> > I don't 100% understand the device tree stuff, b
> ut
> > presumably once I try to boot new kernel from dr
> op
> > box image, I will need to update the uboot to ma
> ke
> > it device tree aware ?
>
> Hi Don :)
>
> Good to see you posting again!
>
> No need to worry, the latest uboot is FDT aware.
> The only thing to pay attention to is if you have
> flashed the default envs image that comes with the
> uboot image, it will automatically look for the DT
> B file in /boot/dts. This folder is populated when
> you install the kernel 4.10.0 (as instructed).
>
> The default MAC address was randomly generated loc
> al MAC address, so it can be used w/o problem. But
> you should be able to change it after upgrading th
> e ketnel to 4.10.0.

Hey bodhi ... good to be back and speak again, apologies for absence ;) ...

I flashed the default envs from the file you supplied, which I think caused the MAC to change ... will try changing it after upgrading debian/kernel ...

Only issue left now is that netconsole seems to be masking some of the serial output (immediately after starting netconsole in uboot), will try switching off netconsole as I'm preferring serial connection these days. Also noticed netconsole seems to slow the boot process as it does ping first to see if server up, so another reason for using serial :)

Cheers
Don,

> Only issue left now is that netconsole seems to be
> masking some of the serial output (immediately aft
> er starting netconsole in uboot), will try switchi
> ng off netconsole as I'm preferring serial connect
> ion these days. Also noticed netconsole seems to s
> low the boot process as it does ping first to see
> if server up, so another reason for using serial :
> )

netconsole will mask serial output if using the same terminal for both serial console and netconsole. To see full log, you need 2 terminal sessions. With 1 terminal, when netconsole start, serial output stops, and vice versa.

If you have set the ping count to 5 like I suggested in the instruction, you could reduce the ping count to 2 to speed it up. This is needed only in a noisy network so that we dont get false positive (the 1st ping usually not reliable in a noisy network).
fw_setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi'

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
bodhi Wrote:
-------------------------------------------------------
> Don,
>
> > Only issue left now is that netconsole seems to
> be
> > masking some of the serial output (immediately a
> ft
> > er starting netconsole in uboot), will try switc
> hi
> > ng off netconsole as I'm preferring serial conne
> ct
> > ion these days. Also noticed netconsole seems to
> s
> > low the boot process as it does ping first to se
> e
> > if server up, so another reason for using serial
> :
> > )
>
> netconsole will mask serial output if using the sa
> me terminal for both serial console and netconsole
> . To see full log, you need 2 terminal sessions. W
> ith 1 terminal, when netconsole start, serial outp
> ut stops, and vice versa.
>
> If you have set the ping count to 5 like I suggest
> ed in the instruction, you could reduce the ping c
> ount to 2 to speed it up. This is needed only in a
> noisy network so that we dont get false positive (
> the 1st ping usually not reliable in a noisy netwo
> rk).
>
> fw_setenv preboot_nc 'setenv nc_ready 0; for pings
> tat in 1 2 3 4 5; do; sleep 1; if run if_netconsol
> e; then setenv nc_ready 1; fi; done; if test $nc_r
> eady -eq 1; then run start_netconsole; fi'
>

Thanks bodhi, more investigation and I can see what you're saying. Sorry about repeated question in another thread !

I have solved this by :

fw_setenv preboot

ie, preboot doesn't now do anything, and of course messages now all go to serial

Don Charisma ... because anything is possible with Charisma

My blog - http://DonCharisma.org
Our commercial site - http://DonCharisma.com
I was updating all my pogoplugs to the latest U-boot and ran into a USB disk problem.

I have one drive that this uboot will just not work with, it throws timeout errors (see below). Google shows that a lot of people have this same problem, but nobody seems to have a solution yet. All of the other dozen drives I have work fine.
This is the boot drive, but that doesn't matter -- it gets these errors even when just scanning the USB bus if this drive is plugged in.

This drive works fine under Debian, it is only uboot that has trouble with it.

With the uboot.mtd0.pinkpogo.davygravy-2012-02-20.kwb, it works 95% of the time and only fails to boot occasionally. But with uboot.2016.05-tld-1.pogo_e02.mtd0.kwb it fails 99% of the time. I have tried other uboots, uboot-pogo_e02-archlinux-2014.kwb will not even recognize that drive.

Natually, I want to have a uboot that has ext4 support and the faster disk read than the davygravy one -- which is painfully slow.

I have experience writing linux drivers, and the ability to build a uboot, so I could try to find & fix the problem. Question is, is it worthwhile? And would you (bodhi) take the changes if I could fix it? And any hints or tips would be appreciated.

**** Here is a snippet of the console output *****
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700)
starting USB...
...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices... 2 Storage Device(s) found
1 bytes read in 330 ms (0 Bytes/s)
Found bootable drive on usb 0:1
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x1f8c80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
rayvt Wrote:
-------------------------------------------------------
> I was updating all my pogoplugs to the latest U-bo
> ot and ran into a USB disk problem.
>
> I have one drive that this uboot will just not wor
> k with, it throws timeout errors (see below). Goo
> gle shows that a lot of people have this same prob
> lem, but nobody seems to have a solution yet. All
> of the other dozen drives I have work fine.
> This is the boot drive, but that doesn't matter --
> it gets these errors even when just scanning the U
> SB bus if this drive is plugged in.
>
> This drive works fine under Debian, it is only ubo
> ot that has trouble with it.
>
> With the uboot.mtd0.pinkpogo.davygravy-2012-02-20.
> kwb, it works 95% of the time and only fails to bo
> ot occasionally. But with uboot.2016.05-tld-1.pog
> o_e02.mtd0.kwb it fails 99% of the time. I have t
> ried other uboots, uboot-pogo_e02-archlinux-2014.k
> wb will not even recognize that drive.
>
> Natually, I want to have a uboot that has ext4 sup
> port and the faster disk read than the davygravy o
> ne -- which is painfully slow.
>
> I have experience writing linux drivers, and the a
> bility to build a uboot, so I could try to find &
> fix the problem. Question is, is it worthwhile?
> And would you (bodhi) take the changes if I could
> fix it? And any hints or tips would be appreciate
> d.
>
> **** Here is a snippet of the console output ****
> *
> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700
> )
> starting USB...
> ...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... 4 USB Device(s) foun
> d
> scanning usb for storage devices... 2 Stora
> ge Device(s) found
> 1 bytes read in 330 ms (0 Bytes/s)
> Found bootable drive on usb 0:1
> EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x1f8c80
> EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x80008d80
> EHCI timed out on TD - token=0x80008d80

This problem is very common. There is no need to have new version.

- Did you try a different flash drive?
- Also try setting the env usb_ready_retry to 60 seconds in serial console:

setenv usb_ready_retry 60

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
I can't find any ide commands in this uBoot. I'm trying to boot from an SSD on a sata interface. Can this uBoot do that?
hotqj Wrote:
-------------------------------------------------------
> I can't find any ide commands in this uBoot. I'm t
> rying to boot from an SSD on a sata interface. Can
> this uBoot do that?

Yes, of course, the ide command is built in. But depending which u-boot. Which box do you have? Please post the serial console boot log when you try this command.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: