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

I`ve rechecked the USB stick under Oracle VM running Ubuntu. For some reason I couldn't paste the console output through the clipboard hence the screenshot.
My ARCH installation is lost, somehow my USB stick become corrupted after doing USB->image backup under windows, e2fsck showed tons of errors. So I`ve reformatted the whole thing to become Ubuntu on Pogo E02.

Sunspot,

I've splitted this into its own topic. Please repost in the new thread below.

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



Edited 1 time(s). Last edit at 02/22/2016 05:05PM by bodhi.

Hi Bodhi,

I have a question regarding to the B part.
B. Flashing default u-boot envs image

Can I skip it as I want to keep using my current env? you helped me alot for this when I was flashing 2014.07 version and I screwed up the env.
You helped me fix it that's why I am afraid I will screw it up again on this. lol

Thanks



Edited 1 time(s). Last edit at 02/25/2016 08:28AM by codier.

codier ,

> Can I skip it as I want to keep using my current
> env? you helped me alot for this when I was
> flashing 2014.07 version and I screwed up the
> env.

If you are running 2014.07 u-boot, already flashed its default envs, then there is no need to flash the new defaults. it will work fine!

BTW, that version is not that much different from the new 2015.10 version. You don't have to upgrade u-boot if you don't need the new features.

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

I see,

The main reason is I want to upgrade my kernel from 3.17 to 4.4. Do I need to upgrade my uboot in this case?

bodhi Wrote:
-------------------------------------------------------
> codier ,
>
> > Can I skip it as I want to keep using my
> current
> > env? you helped me alot for this when I was
> > flashing 2014.07 version and I screwed up the
> > env.
>
> If you are running 2014.07 u-boot, already flashed
> its default envs, then there is no need to flash
> the new defaults. it will work fine!
>
> BTW, that version is not that much different from
> the new 2015.10 version. You don't have to upgrade
> u-boot if you don't need the new features.

codier,

> The main reason is I want to upgrade my kernel
> from 3.17 to 4.4. Do I need to upgrade my uboot in
> this case?

No need to. Just be carfeful with the jump from 3.17 to 4.4. Backup your rootfs first!

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

hi all,

I would like to revive the problem about Sandisk Usb recognized only the fisrt time at boot and no more.
I realized about this problem after having spent a lot a lot a lot of time changing options into the u-boot environments and partitioning the usb key in one partition , two partitions , ext2, et3, ext4, inserted in the 1ft usb slot or in the 2nd and searching in the web... :( :( :( . I had some frustrated days...

Before asking for a question in the forums I usually read them and try to solve by myself, and I understood too late that the problem is known...

Anyway, I have some datas and I think they could help a bit for the problem but I'm not skilled anought to go to the solution :((( bt myself

Because Installed Debian for an I2x-200 using the netinstall images, and I succesfully installed it onto the sandisk stick, and instead I unsuccesfully tried later using the Ready images from your work, I realized that the trouble isn't about the sandisk stick but something in the kernel (yes you know that , but I'm just telling the full history). So not only my NSA325 has troubles with the sandisk but also the i2x-200, with the uInitrd from your work. I tryed your latest 4.4.0 images and they worked whan I used a different usb sticks.

So I tried the command 'usb info' after the first 'usb reset' and after others 'usb reset' and what I can see that after the reset the system loose to recognize the usb hub where the sandisk stick is connected and after that the usb key isn't recognized anymore.

Yes, my understanding can be wrong: I'm not so skilled, I just said it, but I hope it can help you brothers solving the question.

I don't know how to open an uInitrd image to look into and search for anything different about drivers or settings, comparing the working one and the yours. If it helps I can upload all two.

Because the command 'usb reset' sent another time over the fist time, for any combinations among ix2-200, and nsa325 and the two uInitrd produce always the stopping of the recognize behind the Hub, USB Revision 2.0
Marvell EHCI, could it be that in the newer uImage the system send a wrong usb reset? My be some common addresses for Sandisk stick and the Marvell?


Please excuse me if I completely shot out from the target




this is the log for the ix2-200 using usb reset over the fist time

Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub,  USB Revision 2.0
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x058f  Product 0x6254 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered Remote Wakeup 100mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms

3: Mass Storage,  USB Revision 2.10
 - SanDisk Ultra Fit 4C531001360419105094
 - Class: (from Interface) Mass Storage
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0781  Product 0x5583 Version 1.0
   Configuration: 1
   - Interfaces: 1 Bus Powered 224mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 2
     - Class Mass Storage, Transp. SCSI, Bulk only
     - Endpoint 1 In Bulk MaxPacket 512
     - Endpoint 2 Out Bulk MaxPacket 512

** Bad partition 1 **
** Bad partition 1 **
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
## Booting image at 00800000 ...
Bad Magic Number
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

** Bad partition 1 **
** Bad partition 1 **
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
## Booting image at 00800000 ...
Bad Magic Number
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

** Bad partition 1 **
** Bad partition 1 **
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
## Booting image at 00800000 ...
Bad Magic Number

and the same for yhe NSA325:

(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub,  USB Revision 2.0
 -  USB2.0 Hub
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x05e3  Product 0x0608 Version 133.50
   Configuration: 1
   - Interfaces: 1 Self Powered Remote Wakeup 100mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms

3: Mass Storage,  USB Revision 2.10
 - SanDisk Ultra Fit 4C531001360419105094
 - Class: (from Interface) Mass Storage
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0781  Product 0x5583 Version 1.0
   Configuration: 1
   - Interfaces: 1 Bus Powered 224mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 2
     - Class Mass Storage, Transp. SCSI, Bulk only
     - Endpoint 1 In Bulk MaxPacket 512
     - Endpoint 2 Out Bulk MaxPacket 512

** Bad partition 1 **
** Bad partition 1 **
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
## Booting image at 00800000 ...
Bad Magic Number
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

** Bad partition 1 **
** Bad partition 1 **
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
## Booting image at 00800000 ...
Bad Magic Number
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

** Bad partition 1 **
** Bad partition 1 **
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

desigabri,

What you need to do is to start the serial console, power up, interrupt serial console, and run these commands:

printenv
boot

Post here the entire serial console log (from the u-boot banner until the boot process stops).

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

I split the most recent post into its own topic.

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

I'm terrible sorry bodhi,
I solved my problems that was primarily due to my incompetence and secondary by my uncorrected understanding of your explanations.

Because I hadn't those problems with others usb stick, then I didn't realize that I didn't execute exactly all the indications. I'm lazy and not so happy to try again all the processes to verify every step made wrong or right but I try to summarize the events:

I worked on two different NAS: the NSA325, and the i2x-200and I had the same problems that I fixed in the same way

To have the "Sandisk Ultra Fit" usb stick working I have had to do:


IN U-BOOT:
1) add the the root label in bootargs_usb variable:
setenv bootargs_usb 'root=LABEL=rootfs console=ttyS0,115200'


FROM ANOTHER LINUX MACHINE IN THE ROOTFS OF THE USB STICK:

2) set the name of the root partition exactly to "rootfs"

3) add the the label editing the file /etc/fstab into the rootfs from another linux machine

"LABEL=rootfs / ext4 noatime,errors=remount-ro 0 1"

4) execute the "sync" command after the step in preparing the uImage

- - - - - - - - - - - - - - - - - - -

Using others usb sticks I named the root partition in other names (USB_ROOT, ROOT, USBROOT) and they worked fine. I'm pretty sure I needed set the label only in U-BOOT or in the etc/stab file, I don't remember for sure wich one. I believed there were the need to name these point in the same way but if I'm correct, then you need to set EXACTLY to "rootfs".

Today I tryed again all the passages and verified the need of these points, I hope I didn't forget any step, if it will be the case, then I'll add other informations later editing this message.

SO THANKS FOR YOU HELP



Edited 1 time(s). Last edit at 02/29/2016 11:50AM by desigabri.

Hi bodhi,

Is the rescue system still work with your 2015.10 U-boot?

the rescue system from here
http://forum.doozan.com/read.php?4,7915

Thanks

codier Wrote:
-------------------------------------------------------
> Hi bodhi,
>
> Is the rescue system still work with your 2015.10
> U-boot?
>
> the rescue system from here
> http://forum.doozan.com/read.php?4,7915
>
> Thanks

Yes it should work fine.

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

bodhi Wrote:
-------------------------------------------------------
> codier Wrote:
> --------------------------------------------------
> -----
> > Hi bodhi,
> >
> > Is the rescue system still work with your
> 2015.10
> > U-boot?
> >
> > the rescue system from here
> > http://forum.doozan.com/read.php?4,7915
> >
> > Thanks
>
> Yes it should work fine.

Thanks. I made decision to upgrade my U-boot.
The rescue system is not working with my 2014.07 at this moment, so I will upgrade U boot then flash rescue system.

Just want to confirm something first.
(1) Do we need to reflash the rescue system every time we flash/upgrade the U-boot?
(2) Will the rescue system boot up if no device attached to Dockstar (in my case is Dockstar) automatically?

Thanks

codier

> Just want to confirm something first.
> (1) Do we need to reflash the rescue system every
> time we flash/upgrade the U-boot?

No. But as always, you need to make sure that your u-boot envs stays the same. Meaning that if the rescue system is working, then the current set of envs is important, and should not be changed. If you flash the new default envs comes with the new u-boot then you wil need to retrofit the old settings to it.

> (2) Will the rescue system boot up if no device
> attached to Dockstar (in my case is Dockstar)
> automatically?
>

That's the purpose of the rescue system. But I can't garantee it, because I'm not using this rescue system. So you need to judge for yourself. If you have problem booting then I'll help get it working.

If you don't have serial console, then you must install it. Because it is very difficult to troubleshoot problem that comes from u-boot installation without serial console.

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

bodhi Wrote:
-------------------------------------------------------
> codier
>
> > Just want to confirm something first.
> > (1) Do we need to reflash the rescue system
> every
> > time we flash/upgrade the U-boot?
>
> No. But as always, you need to make sure that your
> u-boot envs stays the same. Meaning that if the
> rescue system is working, then the current
> set of envs is important, and should not be
> changed. If you flash the new default envs comes
> with the new u-boot then you wil need to retrofit
> the old settings to it.
>
> > (2) Will the rescue system boot up if no device
> > attached to Dockstar (in my case is Dockstar)
> > automatically?
> >
>
> That's the purpose of the rescue system. But I
> can't garantee it, because I'm not using this
> rescue system. So you need to judge for yourself.
> If you have problem booting then I'll help get it
> working.
>
> If you don't have serial console, then you must
> install it. Because it is very difficult to
> troubleshoot problem that comes from u-boot
> installation without serial console.

Thanks bodhi. I have my serial console ready. that's what you asked me to do it last time. lol

> Thanks bodhi. I have my serial console ready.
> that's what you asked me to do it last time. lol

Cool :)

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

I've move Jeremy's post to its own topic:http://forum.doozan.com/read.php?3,27262

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



Edited 1 time(s). Last edit at 04/02/2016 04:57PM by bodhi.

I've moved addy post to its own topic: http://forum.doozan.com/read.php?3,27272,27277#msg-27277

Everybody,

Please do make a new topic if you have booting problem.

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



Edited 1 time(s). Last edit at 04/02/2016 05:51PM by bodhi.

Hi bodhi,

I have few questions regarding to uEnv.txt

1) is this the environment that is the supplement of the the environment from U-boot?
2) Who has first priority? uEnv.txt or Uboot?
3) when there is/are same syntax in both place. who gets loaded?

Thanks



Edited 1 time(s). Last edit at 04/04/2016 03:24PM by codier.

codier Wrote:
-------------------------------------------------------
> Hi bodhi,
>
> I have few questions regarding to uEnv.txt
>
> 1) is this the environment that is the supplement
> of the the environment from U-boot?
> 2) Who has first priority? uEnv.txt or Uboot?
> 3) when there is/are same syntax in both place.
> who gets loaded?
>
> Thanks

Envs in uEnv.txt will replace the same ones in U-boot. Or it will create new envs.

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

Hi.

I flashed the env variables (and uboot) from the post to my dockstar, but boot delay is now set to 0. Problem is my rescue/pogo system does not load, and usb is not initializing by those env vars either. I try to break using space bar or ctrl+c to get to the uboot command prompt but it is not catched.

The uboot process starts and shows usual stuff for a dockstar, then I see "Hit any key to stop autoboot: 0", then it shows something like "Uboot2015.10>>>Uboot2015.10>>>Uboot2015.10>>>Uboot2015.10>>>Uboot2015.10>>>"
THen all I can do is restart the dockstar and it loops like this.

Is there a sure way to force uboot to go to command prompt at boot when boot delay is set to 0?

Thanks

Oliver,

Your serial console has a problem. Unplug, check the wire. Also check the dockstar header connection. Even with bootdelay=0, it still interruptable.

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



Edited 1 time(s). Last edit at 04/05/2016 01:29PM by bodhi.

Thanks for the quick answer.
That was it. I am actually using a linksys wrt54g as client under openwrt using minicom at the other end of the dockstar because the serial is compatible. My cabling is hanging and the cables are just touching the contact on the linksys board. One of the contact must have gone loose, and I did not know what to expect after upgrading to the new uboot.

Thanks for saving my Dockstar.

Hi bodhi,

this is just a confirmation for you that my second NSA320 is working fine with latest uboot.2015.10-tld-1.nsa320,
it was tested with uart booting before and than flashed to mtd0, together with your latest env
image, especially powering the phy for eth0 is working OK over all combinations of shutdown, poweroff, reboot, etc.,..

the only thing I did was twiddling a litte bit with the uenv variables to speed up the boot process,
because I wanted to have strict usb booting only, so some of the env if statements could be dropped,..

the other NSA320 box is still running with uboot.2014.07-tld-4.nsa320 and it is not much a difference in the behaviour,..
both are fine, because I was used to have an usb_init variable with mw.l f1010100 0020c000; usb reset
when booting usb I still use that on both of the boxes, but it looks like you integrated that into the uboot
so it could be dropped, or what do you think?

best wishes pbg4



Edited 2 time(s). Last edit at 04/07/2016 10:12AM by pbg4.

Hi pbg4,

Yes, the USB should work without that memory poke. For the NSA320 I would recomend upgrade. There are only minor features improvement, but I think that experienced users like you would like to have.

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

ok,

did this:

/usr/sbin/nandwrite -s 786432 /dev/mtd0 uboot.2014.07-tld-3.environment.img

but forgot to do this:

/usr/sbin/flash_erase /dev/mtd0 0xc0000 1

now stuck with:

Quote

Trivial File Transfer Protocol
Source File: C0A80164.img
Opcode: Read Request (1)

to get here, I installed goflexhome uboot 2015.10, I then installed uboot default environments 2014.07 over the top without wiping, I then grabbed debian 4.4.0 rootfs and it booted, I followed the guide of ssh key refresh and apt-get update and apt-get upgrade, and set the correct arcnumber and machid and ethernet address using setenv.

upon reboot the uboot environment variables will not find the usb stick and are asking for the kernel image via tftp...

shall I go find my serial cable?



Edited 2 time(s). Last edit at 05/11/2016 05:14PM by hecatae.

hecatae,

>
> upon reboot the uboot environment variables will
> not find the usb stick and are asking for the
> kernel image via tftp...
>
> shall I go find my serial cable?

Not yet! there is a recovery path here: use uEnv.txt as described in section D.

Quote

D. Add uEnv.txt to /boot directory

Create a text file in /boot directory with the content in the format that u-boot envs are listed.

Examples:

These 4 examples are only to demonstrate the syntax in uEnv.txt (they might or might not apply to your current settings):

- Load appropriate DTB file for the kernel to run GoFlex Net box.
- Use only USB drives for kernel and rootfs during booting
- Use SD card, USB and SATA for booting. The kernel and rootfs search order is as they are appeared on the list: mmc, usb, ide.
- Define that there are 8 storage devices (i.e. disk partitions).

cat /boot/uEnv.txt
dtb_file=/boot/dts/kirkwood-goflexnet.dtb
devices=usb
devices=mmc usb ide
disks=0 1 2 3 4 5 6 7

Copy the file uboot.2014.07-tld-3.environment (from the downloaded tarball) to uEnv.txt and place it in the /boot folder in your rootfs

- On a different Linux box, mount the USB rootfs to /media/sdb1, and

cd /media/sdb1/boot
cp -a uboot.2014.07-tld-3.environment uEnv.txt
sync

- Take is USB rootfs to the GFHome and boot with it.
- Note that if the uboot.2014.07-tld-3.environment is used as is, your box will be booted as GFNet because of the DTB env, but it is OK in your case. Or you could go ahead and edit the file to point to the GF Home DTB.
- Afer you booted into Debian, reflash the uboot.2014.07-tld-3.environment.img.

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

hecatae,

> now stuck with:
>
>

Quote

Trivial File Transfer Protocol
> Source File: C0A80164.img
> Opcode: Read Request (1)

I forgot to ask, where did you see this ?

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

in wireshark

edit: done as requested, still requesting that file via tftp, flashing green, then gives up and flashes orange.



Edited 1 time(s). Last edit at 05/12/2016 01:05PM by hecatae.

hecatae,

Yes, it's time for serial cable.

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