Welcome! Log In Create A New Profile

Advanced

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

Posted by bodhi 
Re: 2013.10 U-Boot for FDT and Non-FDT Kernel - GoFlex Net/GoFlex Home/Pogo E02
February 22, 2014 02:38AM
I've re-uploaded 2013.10-tld-2 u-Boot images for GoFlexNet, GoFlex Home and Pogo E02. And I also uploaded 2013.10-tld-2 u-Boot images for Dockstar and iConnect.

Please check 1st post for download links.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: 2013.10 U-Boot for FDT and Non-FDT Kernel - GoFlex Net/GoFlex Home/Pogo E02
February 22, 2014 06:00AM
Thanks for the quick fix. Works like a charm on my GoflexNet.
Re: 2013.10 U-Boot for FDT and Non-FDT Kernel - GoFlex Net/GoFlex Home/Pogo E02
February 25, 2014 06:46AM
The update works nicely for ext4 rootfs.

I have run in to an issue with one of my GFH units that I could use some advice on. The unit in question works perfectly with one exception, if I modify a parameter (i.e. boot order), then issue saveenv changes are saved. When I issue reset the unit hangs indefinitely. The other two units I updated do not exhibit this behavior. To recover, I power off the unit, remove the HDD, disconnect the NIC and restart the base unit. After some time flashing green goes to flashing orange then to solid green. I reconnect the NIC wait a few seconds and low and behold I have network connectivity to the rescue system (v 2.82). I then modify uboot parameters stderr stdin and stdout from nc to serial (not sure how I stumbled on to that but it works). I then power off the unit reattach the HDD and power up the unit. Netconsole works fine and the unit boots normally. The behavior is the same if using a USB to boot.

I've reverted back to the previous doozan uboot used with kirkwood. Worked perfectly. Ran the update to U-Boot 2013.10 (Feb 21 2014 - 19:48:46)-tld-2 again only to have the same issue with rebooting after modifying uboot.

If anyone has thoughts on this issue please let me know. The upside, the unit is usable and I have a work around albeit convoluted. :)
Re: 2013.10 U-Boot for FDT and Non-FDT Kernel - GoFlex Net/GoFlex Home/Pogo E02
February 25, 2014 11:05PM
WorldwoWires Wrote:
-------------------------------------------------------
> The other two units I
> updated do not exhibit this behavior.

Do these have the same u-Boot? if they do, then for the hanged unit, you should post the dmesg log before, and the u-Boot log while it booted until hanged (with printenv right after the serial console if you did connect that way).

Was the hanged GFH running with UBIT before you install the new u-Boot?

There are many possible causes, we will need the log to see what's going on.

-bodhi
===========================
Forum Wiki
bodhi's corner
If I did not mention it before, there were NO errors updating any of these units.

The unit that hangs was NOT running UBIT before installing the new u-Boot. The previous version was
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709

The 3 units updated are running: U-Boot 2013.10 (Feb 21 2014 - 19:48:46)-tld-2.

For the unit that hangs, this is all that gets logged before I power down:
GoFlexHome> saveenv
s a v e e n v
Saving Environment to NAND...
Erasing NAND...
Erasing at 0xc0000 -- 100% complete.
Writing to NAND... OK
GoFlexHome> reset
r e s e t
resetting ...

The following is what gets logged with network cable attached BEFORE modifying any u-Boot parameters:

U-Boot 2013.10 (Feb 21 2014 - 19:48:46)-tld-2
Seagate GoFlex Home

SoC: Kirkwood 88F6281_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: nc
Out: nc
Err: nc

Flashes green for a few minutes then flashes orange for a few minutes then goes solid green. At which point the recovery system comes up. Attached are the last few lines of dmesg.

[ 19.574318] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 19.580355] UBIFS: mounted read-only
[ 19.583949] UBIFS: file system size: 30836736 bytes (30114 KiB, 29 MiB, 239 LEBs)
[ 19.591657] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[ 19.599010] UBIFS: media format: w4/r0 (latest is w4/r0)
[ 19.604875] UBIFS: default compressor: lzo
[ 19.608982] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 19.615025] VFS: Mounted root (ubifs filesystem) readonly on device 0:15.
[ 19.622240] devtmpfs: mounted
[ 19.625740] Freeing init memory: 168K
[ 19.904437] udevd (70): /proc/70/oom_adj is deprecated, please use /proc/70/oom_score_adj instead.
[ 321.147626] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled

From this you can see where I reconnect the network cable.

At this point I modify u-Boot with the following:

/usr/sbin/fw_setenv stderr 'serial'
/usr/sbin/fw_setenv stdin 'serial'
/usr/sbin/fw_setenv stdout 'serial'

The modified u-Boot is as follows:

arcNumber=3338
baudrate=115200
bootcmd=run sata_bootcmd; run usb_bootcmd; run rescue_bootcmd; reset
bootdelay=5
console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:2A:B7:E6
ipaddr=10.10.10.6
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_start=setenv stdin nc; setenv stdout nc; setenv stderr nc; version
nc_test=ping $ncip
ncip=10.10.10.5
ncipk=10.10.10.4
partition=nand0,2
preboot=run nc_test nc_start
rescue_bootcmd=run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
sata_boot=ide reset; mw 0x800000 0 1; ext2load ide $sata_device 0x800000 /boot/uImage; if ext2load ide $sata_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_bootcmd=run sata_set_bootargs; run sata_boot
sata_custom_params=ignore_loglevel netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/ elevator=bfq
sata_device=0:1
sata_root=/dev/sda1
sata_rootdelay=10
sata_rootfstype=ext4
sata_set_bootargs=setenv bootargs console=$console root=$sata_root rootdelay=$sata_rootdelay rootfstype=$sata_rootfstype $mtdparts $sata_custom_params
serverip=10.10.10.3
usb_boot=usb start; mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_set_bootargs; run usb_boot
usb_custom_params=ignore_loglevel netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/ elevator=bfq
usb_device=0:1
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext3
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
stderr=serial
stdin=serial
stdout=serial


reboot

Everything starts up normally. What I did not see is:

egiga0
Using egiga0 device
host 10.10.10.5 is alive

which gets logged on reset on the other units.

Let me know what else you need log wise.

Thank you in advance.



Edited 1 time(s). Last edit at 02/26/2014 02:43PM by WorldwoWires.
WorldwoWires,

I am not sure what you are trying to do? why saveenv in netconsole prompt? can you boot with USB into debian with this box? if you can then do fw_setenv inside Debian, would that work? (you do not need to saveenv in uBoot, if you can boot into Debian). This is crucial to avoid mistakes, alway boot with a temporary set of uBoot envs, and then if everything went OK, redo it in Debian with fw_setenv.

How about doing this:
- boot back to Debian like you were able to before
- In Debian, install new uBoot.
- Verify netconsole envs are still intact.
- Before rebooting, get the output of fw_printenv and save it to the USB/SATA drive. Also, output of uname -a
- Start netconsole server on the other box
- Reboot this box, and interrupt netconsole, setenv whatever you like, get the final version of printenv output and save it. Don't do saveenv.
- boot with the USB/SATA boot drive still attached.

If it does not boot into Debian then post the final version of printenv output and post here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Thanks again for the reply. Before doing anything further, this is the GFH environment as it stands currently:

Current u-Boot: U-Boot 2013.10 (Feb 21 2014 - 19:48:46)-tld-2

Current u-Boot Environment:

arcNumber=3338
baudrate=115200
bootcmd=run sata_bootcmd; run usb_bootcmd; run rescue_bootcmd; reset
bootdelay=5
console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:2A:B7:E6
ipaddr=10.10.10.6
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_start=setenv stdin nc; setenv stdout nc; setenv stderr nc; version
nc_test=ping $ncip
ncip=10.10.10.5
ncipk=10.10.10.4
partition=nand0,2
preboot=run nc_test nc_start
rescue_bootcmd=run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
sata_boot=ide reset; mw 0x800000 0 1; ext2load ide $sata_device 0x800000 /boot/uImage; if ext2load ide $sata_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_bootcmd=run sata_set_bootargs; run sata_boot
sata_custom_params=ignore_loglevel netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/ elevator=bfq
sata_device=0:1
sata_root=/dev/sda1
sata_rootdelay=10
sata_rootfstype=ext4
sata_set_bootargs=setenv bootargs console=$console root=$sata_root rootdelay=$sata_rootdelay rootfstype=$sata_rootfstype $mtdparts $sata_custom_params
serverip=10.10.10.3
stderr=nc
stdin=nc
stdout=nc
usb_boot=usb start; mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_set_bootargs; run usb_boot
usb_custom_params=ignore_loglevel netconsole=6665@10.10.10.3/eth0,6666@10.10.10.4/ elevator=bfq
usb_device=0:1
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext3
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params


It is my understanding, in order to save environment variable changes from an interrupted netconsole session one must use saveenv.

fw_printenv and fw_setenv are not available.

The only change I ever typically make is to the bootcmd . Changing the boot order.

If this is a procedure that you don't use to make environment changes please let me know. This is how I've always made changes to the u-Boot environment and it works perfectly on my other GFH units.

If I should be making environment changes from within Arch Linux with fw_setenv, please let me know.

That being said, for THIS unit only, when I issue reset after making a change to the u-Boot environment, at this point it hangs. All that is logged is:

GoFlexHome> reset
r e s e t
resetting ...

My assumption is there is something wonky when reestablishing the network connection.

If it's a matter of procedure, I don't have a problem with changing the way I make changes. In any event, there is still some weird issue with this particular GFH unit. All three have identical u-Boot environments with the exception of the ethaddr.


Hopefully this provides clarification to what I am doing and how I go about it.

Thanks again.
WorldwoWires,

> It is my understanding, in order to save
> environment variable changes from an interrupted
> netconsole session one must use saveenv.
>
> fw_printenv and fw_setenv are not available.

You can install uboot-envtools while in Debian/Arch to make fw_setenv and fw_printenv available.

>
> If I should be making environment changes from
> within Arch Linux with fw_setenv, please let me
> know.

It's definite Yes! doing so is better because you would know the u-boot envs you have changed are working correctly before committing to save them.

The only thing I'd comment about your setup is you're running Arch, therefore without initrd. So you can't use disk label to help the booting process. For example
setenv sata_root LABEL=rootfs
It is a bittle more cumbersome, so you should have ony 1 disk that contains a rootfs. Also in your case, it is set to sda1. So if the non-rootfs disk was spun up faster then it would get sda1, and the booting is stuck.

I'm not saying anything is wrong. Just some point to consider when you have problem booting with SATA.

-bodhi
===========================
Forum Wiki
bodhi's corner
Thank you for the suggestion! I'm all about procedure and if there is a better way to do it, I'm all for it! Using uboot-env tools is much simpler and straightforward. Plus it eliminates the weird NIC issue that would occur modifying uBoot via netconsole. Still an issue but for now not an issue.

I use LABEL on my GoFlex Net device that I mirrored. This is also the only device regularly booting from USB.

The only other issue I would like to resolve is mounting an EXT4 partition from the rescue system. A project for a different day.

Thanks again for the assistance.
I've uploaded the 2013.10-tld-2 u-Boot image for the Netgear Stora. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner
Hi there,

I have a Pogoplug E02 and everything went fine following the installation steps.
Pogoplug:/tmp$ cat /etc/fw_env.config 
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0		0xc0000		0x20000		0x20000
Pogoplug:/tmp$ cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "root"
mtd3: 05b00000 00020000 "data"
Pogoplug:/tmp$ /usr/sbin/flash_erase /dev/mtd0 0 4                            
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000 done
Pogoplug:/tmp$ nandwrite /dev/mtd0 uboot.2013.10.tld-2.pogo_e02.mtd0.kwb 
Writing data to block 0
Writing data to block 20000
Writing data to block 40000
Writing data to block 60000

But when I run fw_printenv after nandflash i get

Pogoplug:/tmp$ /usr/sbin/fw_printenv                                    
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200

Please help, 'cause I don't want to mess up my Pogoplug ...
jadefalcon100,

The installation assumes the current U-Boot on your Pogoplug is what Jeff's script installed.That has the U-Boot env already at 0xC0000. So there would be no CRC error.

- Which U-Boot version did you have before the installation?
- Can you connect with netconsole or serial console before, and now?

EDITED: typo.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 03/16/2014 07:21PM by bodhi.
Hi Bodhi,

I had Jeff's original uboot installed (the one from the script on http://projects.doozan.com/debian/)
Don't ask me about the Version Number. ;-)

NetConsole worked fine before flashing, I haven't tried booting after flashing because of your warning not to boot after something went wrong.
Additionally I don't have a serial cable for SC.

Maybe I missed a point in my first post. I think I ran "flash_eraseall /dev/mtd0 0 4" instead of "flash_erase" with something like "[...] 87% complete [...]" because I forgot the "/usr/sbin/" prefix. Does I matter somehow?

Kind Regards,
Jade
jadefalcon100 Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> I had Jeff's original uboot installed (the one
> from the script on
> http://pro
> jects.doozan.com/debian/
)
> Don't ask me about the Version Number. ;-)
>
> NetConsole worked fine before flashing, I haven't
> tried booting after flashing because of your
> warning not to boot after something went wrong.
> Additionally I don't have a serial cable for SC.
>
> Maybe I missed a point in my first post. I think I
> ran "flash_eraseall /dev/mtd0 0 4" instead
> of "flash_erase" with something like "[...] 87%
> complete [...]" because I forgot the "/usr/sbin/"
> prefix. Does I matter somehow?
>
> Kind Regards,
> Jade

Jade,
I'm afraid so, you've erased your u-boot envs with that typo! /usr/bin was not a problem, flash_eraseall wiped out the entire mtd0, which is where u-boot envs are stored. So it was wise that you did not reboot :) I will find the post where I have the instruction to recover from this problem.

-bodhi
===========================
Forum Wiki
bodhi's corner
Here is the thread:
http://forum.doozan.com/read.php?3,7477,10982#msg-10982

Look for this section:

- Flash uboot.environment to 0xC0000

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 03/17/2014 12:53PM by bodhi.
It worked. Flashing uboot.environment removed the bad CRC!

Thank you very much!!!

Jade
jadefalcon100 Wrote:
-------------------------------------------------------
> It worked. Flashing uboot.environment removed the
> bad CRC!
>
> Thank you very much!!!
>
> Jade

Damn.

After flashing I added the net console commands into env and rebooted the plug
But netconsole is quiet and the front led is not blinking.
The only sign of life is the ethernet port blinking three times every 5 seconds.

Any suggestions?

EDIT: After checking fw_printing I think ethaddr is missing...
Any hope of recovery? :'(



Edited 1 time(s). Last edit at 03/17/2014 03:03PM by jadefalcon100.
Jade,

If the ethaddr is not defined, then the kernel won't bring up ethernet network. But the kernel should boot OK. Just that you don't have network connection. The best way to recover is to connect serial console.

Since we can count on the fact that the uBoot image flashing was successful, and you have a sane u-Boot envs, except for MAC address, there might be a "soft" way to recover (I'm thinking out loud here): Perhaps a patched kernel which temporarily assigns a local MAC address if it is all 0's, would allow the ethernet to be brought up OK.

In any case, if you want to take this opportunity of get serial console working then do that because it would be the best way. Because it would take very little effort to connect serial console on the Pogo E02. It always has the serial header already installed (to my knowledge). It would take time to purchase, unless you can borrow one or have a Nokia CA42 cable already.

See this thread for serial console:
http://forum.doozan.com/read.php?8,13263

-bodhi
===========================
Forum Wiki
bodhi's corner
Jade,

Which kernel version are you running on this Pogo E02 rootfs?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Newer U-Boot for FDT and Non-FDT Kernel
March 18, 2014 04:19PM
Hi. I have Iomega ix4-200d device. I've just broke original u-boot and now playing with device. I write u-boot from similar device and able to boot via uart and console. I have hardware issues (wrong memory reported, may-be other).
I tested images you provide and device loads it via uart. But, they all had non-compatible hardware hardcoded, i think.


Here some info i've found:
it's has same HW as ix2-200, which is much popular. (except memory size and cpu freq)
Here is GPL stuff
Here is some info about similar ix2-200

Can you please make u-boot for my device?
Re: Newer U-Boot for FDT and Non-FDT Kernel
March 18, 2014 11:18PM
vasichkin Wrote:
-------------------------------------------------------
> Hi. I have Iomega ix4-200d device. I've just broke
> original u-boot and now playing with device. I
> write u-boot from similar device and able to boot
> via uart and console. I have hardware issues
> (wrong memory reported, may-be other).
> I tested images you provide and device loads it
> via uart. But, they all had non-compatible
> hardware hardcoded, i think.

It's true. U-Boot must be built for specific hardware device. However, the StorCenter is also a Kirwood 88F6281, so you can UART-boot with other U-Boot Kirkwood 88F6281. Of course it will not bring up correct memory, SATA ports, and/or ethernet in some cases.

>
>
> Here some info i've found:
> it's has same HW as ix2-200, which is much
> popular. (except memory size and cpu freq)
> [url=https://lenovo-na-en.custhelp.com/app/answers
> /detail/a_id/22898/related/1]Here is GPL
> stuff[/url]
> [url=http://iomega.nas-central.org/wiki/Category:I
> x2-200]Here is some info about similar
> ix2-200[/url]
>
> Can you please make u-boot for my device?

What you should do is Google for the patch, i.e. board file. If you can find an old version of the patch, I will then retrofit it for current U-Boot. Without some starting point, it will be quite time consuming to create a new patch. I'm afraid I don't have enough free time to do that!

-bodhi
===========================
[color=#3333FF][url=http://forum.doozan.com/read.php?2,23630]Forum Wiki[/url][/color]
[url=https://mibodhi.blogspot.com]bodhi's corner[/url]
Re: Newer U-Boot for FDT and Non-FDT Kernel
March 19, 2014 06:57AM
bodhi Wrote:

> What you should do is Google for the patch, i.e.
> board file. If you can find an old version of the
> patch, I will then retrofit it for current U-Boot.
> Without some starting point, it will be quite time
> consuming to create a new patch. I'm afraid I
> don't have enough free time to do that!

Hi. Thank you for your attention.
Here what i found:
I found thread on this forum
kernel patch to support sensors and buttons ix2-200
Kernel patch for ix4-200d
In GPL archive i've found that u-boot is building as "make rd88f6281a_config LE=1 NBOOT=1" (u-boot sources is there)

I think i need generic u-boot image for rd88f6281a with fixed memory and cpu freq. After that i can load linux kernel and run dabian as usual. Am i right?
BTW, what should search for? Is it patch for u-boot or for kernel?
you were right, Bodhi.

the Plug bootet normally, but halted at the very beginnig of the boot sequence in the moment he did not find a mac address.

So interrupting with serial console did the trick.
I entered the mac address with setenv and saved the environment.

The reboot worked fine and everything is back online.

thanks for your help!!!

Jade

BTW: I'm now running kirkwood 3.13.1 + rootfs from your other post
jade,

> The reboot worked fine and everything is back
> online.
>

Cool!

>
> BTW: I'm now running kirkwood 3.13.1 + rootfs from
> your other post

Were you running this rootfs when you can't boot because of the ethaddr is missing?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Newer U-Boot for FDT and Non-FDT Kernel
March 20, 2014 01:24AM
vasichkin,

> I
> found thread on this forum

> kernel
> patch to support sensors and buttons
> ix2-200

> [url=http://lists.infradead.org/pipermail/linux-ar
> m-kernel/2009-November/003906.html]Kernel patch
> for ix4-200d[/url]

These are kernel patches.

> In GPL archive i've found that u-boot is building
> as "make rd88f6281a_config LE=1 NBOOT=1" (u-boot
> sources is there)

I'll take a look.

>
> I think i need generic u-boot image for rd88f6281a
> with fixed memory and cpu freq. After that i can
> load linux kernel and run dabian as usual. Am i
> right?

It could work. But you will need to research the info. Do you have the U-boot booting log for your box?

> BTW, what should search for? Is it patch for
> u-boot or for kernel?

Should be u-Boot patch.

-bodhi
===========================
[color=#3333FF][url=http://forum.doozan.com/read.php?2,23630]Forum Wiki[/url][/color]
[url=https://mibodhi.blogspot.com]bodhi's corner[/url]
Re: Newer U-Boot for FDT and Non-FDT Kernel
March 20, 2014 04:56AM
I've got luck to compile U-boot from here (GPL sources)
It contains modified sources of u-boot 1.1.4.
I was able to load compiled u-boot, but it still reports less RAM than i have (128 instead of 512).
u-boot booting log differs from image to image (less or more informative). Original one is not informative at all. I'll post it later.
Re: Newer U-Boot for FDT and Non-FDT Kernel
March 20, 2014 01:51PM
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Mar 20 2014 - 14:47:53) Marvell version: 3.5.9

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM (DDR2) CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0, egiga1 [PRIME]
Recovery imgage will be treated in multi mode
USB:   scanning bus for devices... 3 USB Device(s) found
1 Storage Device(s) found
Trying to load image from USB flash drive using FAT FS
reading /multiware.img

** Unable to read "/multiware.img" from usb 0:1 **
Trying to load image from USB flash drive using ext2 FS partition 0
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:0 **
Trying to load image from USB flash drive using ext2 FS partition 1
.........................
Re: Newer U-Boot for FDT and Non-FDT Kernel
March 20, 2014 11:32PM
vasichkin,

Do you have the boot log with original U-Boot? did it show the correct RAM?

-bodhi
===========================
Forum Wiki
bodhi's corner
Hi.
The problem is that i do not have original u-boot and i can't find u-boot output from ix4-200d anywhere (ix2-200 available).
Latest news: i compiled sources and get some images. After test i found image that suits device best (u-boot-rd88f6281a_400rd_nand.bin).
I also installed linux as described here
All seems to be working except some issues:
I see only one network card (should be two) and it it's found to be fast ethernet (should be gigabit)
I'm going to compile kernel now
Here is boot log output:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: DB-88F6281A-BP LE

U-Boot 1.1.4 (Mar 20 2014 - 15:16:11) Marvell version: 3.5.9

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A1CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM (DDR2) CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled

Error!, MV88F6282 doesn't support LCD module when booting from NAND!

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Marvell>> boot

NAND read: device 0 offset 0x100000, size 0x300000
 3145728 bytes read: OK

NAND read: device 0 offset 0x540000, size 0x1000000
 16777216 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.32-5
   Created:      2014-03-13  21:24:23 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1435632 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs
   Created:      2014-03-13  21:22:19 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6530013 Bytes =  6.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-48squeeze4) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Tue Sep 24 15:11:05 UTC 2013
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell DB-88F6281-BP Development Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:0x300000@0x100000(uImage),0x1000000@0x540000(uInitrd) root=/dev/mapper/storbox-root
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 256MB 256MB = 512MB total
[    0.000000] Memory: 508800KB available (3512K code, 583K data, 124K init, 0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000000] Console: colour dummy device 80x30
[   21.474961] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[   21.714925] Security Framework initialized
[   21.714944] SELinux:  Disabled at boot.
[   21.714971] Mount-cache hash table entries: 512
[   21.715262] Initializing cgroup subsys ns
[   21.715277] Initializing cgroup subsys cpuacct
[   21.715287] Initializing cgroup subsys devices
[   21.715295] Initializing cgroup subsys freezer
[   21.715303] Initializing cgroup subsys net_cls
[   21.715361] CPU: Testing write buffer coherency: ok
[   21.716084] devtmpfs: initialized
[   21.717765] regulator: core version 0.5
[   21.717965] NET: Registered protocol family 16
[   21.718455] Kirkwood: MV88F6281-A1, TCLK=200000000.
[   21.718467] Feroceon L2: Enabling L2
[   21.718500] Feroceon L2: Cache support initialised.
[   21.719295] Kirkwood PCIe port 0:
[   21.719302] link up
[   21.719309] PCI: bus0 uses PCIe port 0
[   21.719622] pci 0000:00:01.0: PME# supported from D0 D1 D3hot
[   21.719633] pci 0000:00:01.0: PME# disabled
[   21.719672] PCI: bus0: Fast back to back transfers disabled
[   21.720924] bio: create slab <bio-0> at 0
[   21.721196] vgaarb: loaded
[   21.721645] Switching to clocksource orion_clocksource
[   21.725417] NET: Registered protocol family 2
[   21.725649] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[   21.726403] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[   21.726756] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[   21.726935] TCP: Hash tables configured (established 16384 bind 16384)
[   21.726944] TCP reno registered
[   21.727098] NET: Registered protocol family 1
[   21.727270] Unpacking initramfs...
[   22.139525] Freeing initrd memory: 6376K
[   22.139618] NetWinder Floating Point Emulator V0.97 (double precision)
[   22.139858] audit: initializing netlink socket (disabled)
[   22.139891] type=2000 audit(0.650:1): initialized
[   22.146354] VFS: Disk quotas dquot_6.5.2
[   22.146623] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   22.146720] JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   22.147315] msgmni has been set to 1006
[   22.148928] alg: No test for stdrng (krng)
[   22.149044] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[   22.149056] io scheduler noop registered
[   22.149063] io scheduler anticipatory registered
[   22.149071] io scheduler deadline registered
[   22.149246] io scheduler cfq registered (default)
[   22.155274] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   22.155719] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   22.509799] console [ttyS0] enabled
[   22.513879] NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit)
[   22.522490] Scanning device for bad blocks
[   22.737412] 2 cmdlinepart partitions found on MTD device orion_nand
[   22.743724] Creating 2 MTD partitions on "orion_nand":
[   22.748891] 0x000000100000-0x000000400000 : "uImage"
[   22.754461] 0x000000540000-0x000001540000 : "uInitrd"
[   22.760632] mice: PS/2 mouse device common for all mice
[   22.766148] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[   22.772091] i2c /dev entries driver
[   22.775776] cpuidle: using governor ladder
[   22.780011] cpuidle: using governor menu
[   22.784036] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   22.790440] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   22.831708] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   22.871705] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   22.911704] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   22.951705] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   22.958370] TCP cubic registered
[   22.961616] NET: Registered protocol family 17
[   22.966433] registered taskstats version 1
[   22.971264] rtc-mv rtc-mv: setting system clock to 2014-03-22 13:19:13 UTC (1395494353)
[   22.979380] Initalizing network drop monitor service
[   22.984435] Freeing init memory: 124K
Loading, please wait...
[   23.062101] udev[44]: starting version 164
[   23.414148] SCSI subsystem initialized
[   23.463545] usbcore: registered new interface driver usbfs
[   23.479045] usbcore: registered new interface driver hub
[   23.491743] MV-643xx 10/100/1000 ethernet driver version 1.4
[   23.497778] usbcore: registered new device driver usb
[   23.585521] mv643xx_eth smi: probed
[   23.589246] mmc0: mvsdio driver initialized, using GPIO 38 for card detection
[   23.604638] net eth0: port 0 with MAC address 00:50:43:26:14:28
[   23.650044] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   23.656735] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   23.662091] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   23.691695] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   23.711679] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   23.734455] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   23.741281] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   23.748565] usb usb1: Product: Marvell Orion EHCI
[   23.753300] usb usb1: Manufacturer: Linux 2.6.32-5-kirkwood ehci_hcd
[   23.759687] usb usb1: SerialNumber: orion-ehci.0
[   23.765714] ahci 0000:00:01.0: controller can't do NCQ, turning off CAP_NCQ
[   23.772735] ahci 0000:00:01.0: controller can't do PMP, turning off CAP_PMP
[   23.779726] ahci 0000:00:01.0: MV_AHCI HACK: port_map 7 -> 3
[   23.785423] ahci 0000:00:01.0: Disabling your PATA port. Use the boot option 'ahci.marvell_enable=0' to avoid this.
[   23.796463] usb usb1: configuration #1 chosen from 1 choice
[   23.802407] hub 1-0:1.0: USB hub found
[   23.806203] hub 1-0:1.0: 1 port detected
[   23.810346] sata_mv sata_mv.0: version 1.28
[   23.817597] ahci: SSS flag set, parallel bus scan disabled
[   23.823181] ahci 0000:00:01.0: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x3 impl IDE mode
[   23.831231] ahci 0000:00:01.0: flags: 64bit stag led slum part
[   23.840509] sata_mv sata_mv.0: slots 32 ports 2
[   23.852405] scsi0 : sata_mv
[   23.856157] scsi1 : sata_mv
[   23.859419] ata1: SATA max UDMA/133 irq 21
[   23.863590] ata2: SATA max UDMA/133 irq 21
[   23.869775] scsi2 : ahci
[   23.872962] scsi3 : ahci
[   23.876034] scsi4 : ahci
[   23.879042] ata3: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 9
[   23.886340] ata4: SATA max UDMA/133 abar m1024@0xe0000000 port 0xe0000180 irq 9
[   23.893702] ata5: DUMMY
[   24.121710] usb 1-1: new high speed USB device using orion-ehci and address 2
[   24.221694] ata1: SATA link down (SStatus 0 SControl F300)
[   24.273092] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   24.279828] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   24.287014] usb 1-1: Product: USB2.0 Hub
[   24.292239] usb 1-1: configuration #1 chosen from 1 choice
[   24.301020] hub 1-1:1.0: USB hub found
[   24.305225] hub 1-1:1.0: 4 ports detected
[   24.571785] ata2: SATA link down (SStatus 0 SControl F300)
[   24.641700] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   24.689916] ata3.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
[   24.695622] ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[   24.748269] ata3.00: configured for UDMA/133
[   24.752861] scsi 2:0:0:0: Direct-Access     ATA      ST3500630AS      3.AA PQ: 0 ANSI: 5
[   25.111702] ata4: SATA link down (SStatus 0 SControl 300)
[   25.149688] sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[   25.158187] sd 2:0:0:0: [sda] Write Protect is off
[   25.163138] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   25.172889]  sda: sda1 sda2 < sda5 >
[   25.200332] sd 2:0:0:0: [sda] Attached SCSI disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [   25.508333] device-mapper: uevent: version 1.0.3
[   25.515116] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
done.
Begin: Running /scripts/local-premount ... done.
[   25.899384] kjournald starting.  Commit interval 5 seconds
[   25.904959] EXT3-fs: mounted filesystem with ordered data mode.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevd[   26.853562] udev[192]: starting version 164
.
Synthesizing the initial hotplug events...done.
[   27.033967] udev[207]: renamed network interface eth0 to eth1
Waiting for /dev to be fully populated...done.
Setting up LVM Volume Groups  File-based locking initialisation failed.
  Reading all physical volumes.  This may take a while...
  Found volume group "storbox" using metadata type lvm2
  File-based locking initialisation failed.
  3 logical volume(s) in volume group "storbox" now active
.
Checking root file system...fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/mapper/storbox-root: clean, 24711/244320 files, 183373/975872 blocks
done.
[   28.355419] EXT3 FS on dm-0, internal journal
[   28.578142] loop: module loaded
Loading kernel modules...done.
Cleaning up ifupdown....
Setting up networking....
Activating lvm and md swap...[   28.802749] Adding 499704k swap on /dev/mapper/storbox-swap.  Priority:-1 extents:1 across:499704k
done.
Checking file systems...fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/sda1: clean, 19/124496 files, 32352/248832 blocks
done.
Mounting local filesystems...done.
Activating swapfile swap...done.
Cleaning up temporary files....
Configuring network interfaces...done.
Starting portmap daemon....
Starting NFS common utilities: statd.
Cleaning up temporary files....
Setting kernel variables ...done.
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Starting portmap daemon...Already running..
Starting NFS common utilities: statd.
Starting enhanced syslogd: rsyslogd.
[   30.744337] RPC: Registered udp transport module.
[   30.749134] RPC: Registered tcp transport module.
[   30.753896] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   30.916529] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   31.256186] NET: Registered protocol family 10
[   31.267431] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   31.279752] svc: failed to register lockdv1 RPC service (errno 97).
[   31.300054] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[   31.340133] NFSD: starting 90-second grace period
[   31.460671] eth1: link up, 100 Mb/s, full duplex, flow control disabled
[   31.467647] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Starting deferred execution scheduler: atd.
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsd mountd.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting Samba daemons: nmbd smbd.
Starting MTA:Starting internet superserver: inetd.
Starting OpenBSD Secure Shell server: sshd.
 exim4.
Starting the Winbind daemon: winbind.

Debian GNU/Linux 6.0 storbox ttyS0

storbox login:
Hi Bodhi,
I tried to flash the uboot of my old iConnect and everything seems fine - but unfortunately all my uboot enviroments are gone.

Here is the result of printenv over serial console:
iConnect> printenv
baudrate=115200
bootargs=root=/dev/nfs nfsroot=: ip=::::::off
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
ethact=egiga0
ethaddr=00:d0:b8:0d:f2:cf
stderr=serial
stdin=serial
stdout=serial

Environment size: 324/131068 bytes
iConnect>

Quick and dirty I added:
iConnect> setenv mainlineLinux yes
iConnect> setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2'
iConnect> setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
iConnect> setenv usb_bootcmd 'ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000'
Now my iConnect booting properly from usb...
...but are there any other important uboot enviroment values I have to recreate?
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: