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 
Puhvogel,

Your orginal uBoot envs are still intact, but the new U-Boot use a different location (0xC0000). That's why it seemsto be gone. I did mention this in the instruction for iConnect. If you you want to start with a good set of U-Boot env, see this thread: http://forum.doozan.com/read.php?3,7477,10982#msg-10982

Look for the section
- Flash uboot.environment to 0xC0000

In Jeff's installation script, this set of U-Boot envs is flashed separately, and it is a good starting point for booting with USB. OTOH, you can also just copy/paste your old U-Boot envs in Debian (using fw_setenv), if you have a log that list all your old envs.

When I have time, I'll patch U-Boot for iConnect to set default envs that are good enough for booting USB.

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



Edited 2 time(s). Last edit at 03/26/2014 01:06AM by bodhi.
I've uploaded 2014.01 U-Boot image for Pogo E02:
uboot.2014.01-tld-1.pogo_e02.bodhi.tar
md5:
8288a63432cb4fb0168d2baac8530333

This version incorporated a patch to provide a way to increase the USB ready retry period. This hopefully will help those who use large USB HDDs such as a 4TB WesternDigital or Seagate Desk, also possibly help with booting-problem USB thumb drives.

To enable the feature, set the following U-Boot env either in Linux or U-Boot. The period could be any unsigned integer, so increase the period as needed to a number where you are comfortable that the USB drive is working, and then add a few seconds to be sure. For example, to set 5 second period:
fw_setenv usb_ready_retry 5

Note that this number is the maximum period that U-Boot is trying to detect the disks status as ready (i.e. U-Boot time out after trying for 5 seconds).

If this feature is indeed helpful to solve booting/rebooting problem on the Pogo E02, then I will put it up on the first post.

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



Edited 1 time(s). Last edit at 03/27/2014 07:23PM by bodhi.
I've uploaded 2014.01-tld-1 u-Boot images for GoFlexNet, GoFlex Home, Pogo E02, Dockstar, iConnect, and Netgear Stora. Please see 1st post for download links.

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

I have a question, anybody have a Lacie D2-Network nas ? Because i have one and i whant a new U-boot ^^.

This is same kind of board, same CPU 256Mo of ram one internal sata, one esata, one USB host and one USB guest, just a small eeprom for U-boot.

Thanks.
Val532,

It is in the mainline U-Boot, so it is possible:
Active  arm         arm926ejs      kirkwood    LaCie           net2big_v2          d2net_v2                             lacie_kw:D2NET_V2

1. Is it the correct one, i.e. d2net v2 ? probably is the same. However, V2 might indicate some memory differences.
2. Do you have serial console and can you boot with UART (kwboot)?
3. What is the output of your fw_setenv? (looking for mtdparts, arcNumber…)

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

So, it's the V2 model and yes i have a serial cable (in fact i allready have a working Debian 7 on it), for the output of fw_setenv you need to wait, my device is unreachable for the moment (i lost the network on it ^^). So i post the output of fw_setenv later.
Hi bodhi,

thanks for the new uBoot version.

Unfortunately i bricked one of my dockstart by simply flashing it from the old uBoot.
So I tried on my second, this time launching it from inside us boot

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
u-boot>>
u-boot>>
u-boot>> usb start
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
u-boot>> fatload usb 0:1 0x800000 uboot.2014.01-tld-1.dockstar.mtd0.kwb
reading uboot.2014.01-tld-1.dockstar.mtd0.kwb

524288 bytes read
u-boot>> go 0x800200
## Starting application at 0x00800200 ...
prefetch abort
pc : [<00000000>]          lr : [<00000000>]
sp : 00000000  ip : 00000000     fp : 00000000
r10: 00000000  r9 : 00000000     r8 : 00000000
r7 : 00000000  r6 : 00000000     r5 : 00800cb0  r4 : 07e32f68
r3 : 00000000  r2 : 00800200     r1 : 07e3666c  r0 : 00000002
Flags: nzcv  IRQs on  FIQs on  Mode USER_26
Resetting CPU ...

resetting ...


U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
u-boot>>

The same happens with the 2013.10

I'm sure I'm doing something wrong, but can not figure out what.

When I use JTAG to load the image into the bricked Dockstar I only get this (this log was captured from the working Dockstar, but they behave the same):

Open On-Chip Debugger
> init
> halt
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
> dockstar_init
> load_image uboot.2013.10.tld-2.dockstar.mtd0.kwb 0x800000
524288 bytes written at address 0x00800000
downloaded 524288 bytes in 84.164177s (6.083 KiB/s)
> resume 0x800200
target state: halted
target halted in ARM state due to debug-request, current mode: Abort
cpsr: 0x800000d7 pc: 0xffff0010
MMU: disabled, D-Cache: disabled, I-Cache: disabled
>

All help appreciated.
Goetz.
Goetz,

You have U-Boot 2011.12 installed. And you tried to run a different and newer U-Boot image from memory, I don't think it will work (U-Boot is designed to run from a reset/initial state).

When you said "bricked", does the bricked Dockstar U-Boot load at all? can you stop it at serial console?

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

fw_printenv does not work on my setup, because i do not have a config file for ^^.
Val532 Wrote:
-------------------------------------------------------
> @bodhi
>
> fw_printenv does not work on my setup, because i
> do not have a config file for ^^.


Use printenv at serial console :)

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

I would like to know if this uBoot supports DTS. The reason I'm asking is because I'm trying to use Fedora 18 for ARM with my Pogo E02 and I'm having issues with the latest kernel.

To explain a bit more, I have no problem booting Fedora 18 image available here:

https://fedoraproject.org/wiki/Architectures/ARM/F18/Installation#Using_Fedora_on_a_Kirkwood_Device

Only after updating the system it's just not booting anymore. After reading a bit about this issue, I found that 3.7+ Kernel need uBoot to support DTS.

https://fedoraproject.org/wiki/Architectures/ARM/F18/Installation#Updating_to_the_3.7.2B_Kernel

Here's my uBoot version:

U-Boot 2014.01-tld-1 (Mar 17 2014 - 21:43:49)
Pogo E02

Here's my environment settings:

arcNumber=3542
baudrate=115200
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootwait
bootcmd=usb start; ${loadImage}; ${loadInitrd} ; bootm 0x6400000 0x7400000
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:9E:BC
fdt_high=0x2C000000
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
if_netconsole=ping $serverip
initrd_high=0x2C000000
ipaddr=192.168.1.100
led_error=orange blinking
led_exit=green off
led_init=green blinking
loadImage=ext2load usb 0:1 0x6400000 uImage
loadInitrd=ext2load usb 0:1 0x7400000 uInitrd
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
ncip=192.168.1.2
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
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
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.1.2
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=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_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan; setenv usb_root LABEL=ROOTFS
usb_root=/dev/sda1
usb_rootdelay=30
usb_rootfstype=ext4
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2767/131068 bytes

I tried to replace the kernel with the old one that used to work but it is the same...

Also, when I check /var/log/messages, the last message is when I rebooted after updating so it's not helping finding the problem. That means that the system probably stops right after loading kernel and initrd. I verified that with netconsole and the kernel and initrd are loading fine.

I'm out of options...

Thanks for helping!



Edited 1 time(s). Last edit at 04/14/2014 06:24PM by pancho22.
Pancho,

Yes. This U-boot supports DTS. You need to load the dtb and include it in bootcmd. See instruction in the latest update in the 1st post (at the end).

Section: Booting with Debian FDT Kernel.

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



Edited 1 time(s). Last edit at 04/14/2014 07:09PM by bodhi.
Hi bodhi,

the bricked dockstar appears to be dead. When looking with JTAG it loads something, but crashes before any output appears on the serial console.

Do I've to do anything special when loading uboot with JTAG?

Thanks,
Goetz.
bodhi Wrote:
-------------------------------------------------------
> Val532 Wrote:
> --------------------------------------------------
> -----
> > @bodhi
> >
> > fw_printenv does not work on my setup, because
> i
> > do not have a config file for ^^.
>
>
> Use printenv at serial console :)

Hi,

So i managed to creat fw_env.config like :
# MTD device name   Device offset     Env. size     Flash sector size     Number of sectors
/dev/mtd0 0x70000 0x1000 0x1000

And the result of fw_printenv is :
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200
bootcmd=dhcp && run netconsole; if run usbload || run diskload; then bootm 0x800000 0x1200000; fi
bootdelay=10
bootfile=uImage
diskload=ide reset && ext2load ide 0:2 0x800000 boot/uImage && ext2load ide 0:2 0x1200000 boot/uInitrd
ethact=egiga0
ethaddr=00:d0:4b:93:33:21
filesize=188328
ipaddr=192.168.0.17
loadaddr=0x800000
netconsole=set stdin $stdin,nc; set stdout $stdout,nc; set stderr $stderr,nc;
serverip=192.168.0.19
stderr=serial,nc,nc,nc
stdin=serial,nc,nc,nc
stdout=serial,nc,nc,nc
usbload=usb start && fatload usb 0:1 $loadaddr /boot/$bootfile

Do you need something else ?

Thanks
Val532,

Quote

> So i managed to creat fw_env.config like :
> # MTD device name Device offset Env. size
> Flash sector size Number of sectors
> /dev/mtd0 0x70000 0x1000 0x1000

Is this the definition in the stock u-boot? it is quite small. I am looking for mtdparts definition in U-Boot envs, but it does not appear in the list you posted above. In Linux, what is your output of cat /proc/mtd ? you can also find it in dmesg. This is because we need to know what the mtd layout, to see if the new u-boot will fit. And where is the current u-boot envs so we don't overwrite it.

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

Sorry I have very little exeperience with JTAG (my new JTAG kit is still in one of the boxes somewhere in the closet)! perhaps others can help you with this.

-bodhi
===========================
Forum Wiki
bodhi's corner
bodhi Wrote:
-------------------------------------------------------
> Val532,
>
>
Quote

> > So i managed to creat fw_env.config like :
> > # MTD device name Device offset Env. size
>
> > Flash sector size Number of sectors
> > /dev/mtd0 0x70000 0x1000 0x1000
>
>
> Is this the definition in the stock u-boot? it is
> quite small. I am looking for mtdparts definition
> in U-Boot envs, but it does not appear in the list
> you posted above. In Linux, what is your output of
> cat /proc/mtd ? you can also find it in
> dmesg. This is because we need to know what the
> mtd layout, to see if the new u-boot will fit. And
> where is the current u-boot envs so we don't
> overwrite it.

Ok this is the result of the command :
dev:    size   erasesize  name
mtd0: 00080000 00001000 "u-boot"

if you whant i added a binary copy of mtd0.
Attachments:
open | download - mtd0.bin (512 KB)
Val,

I will build a u-boot image for you to test. But first, please check if you can boot with UART by dumping the Boot ROM: at serial console, execute the md command and post the output here.
md ff00003c

Also:

Was that the only output of cat /proc/mtd ? no other mtd 1,2,3…? (I did not see it defined in u-boot code for default env).

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



Edited 1 time(s). Last edit at 04/17/2014 02:25AM by bodhi.
bodhi Wrote:
-------------------------------------------------------
> Val,
>
> I will build a u-boot image for you to test. But
> first, please check if you can
>
> boot with UART
by dumping the Boot ROM: at
> serial console, execute the md command and post
> the output here.
>
> md ff00003c
>
>
> Also:
>
> Was that the only output of cat /proc/mtd ? no
> other mtd 1,2,3…? (I did not see it defined in
> u-boot code for default env).

Ok, but for the moment i can open my NAS to use the serial port.
And for mtd there is only one partition mtd0 because on this NAS only u-boot is on the EEPROM chip and is size is 512KB.
Val532,

Quote

> And for mtd there is only one partition mtd0
> because on this NAS only u-boot is on the EEPROM
> chip and is size is 512KB.

Got it. That's why the env is so small and stored at the end of 512K.

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

> Do I've to do anything special when loading uboot
> with JTAG?

Same as I responded to other poster here in Debian section:
http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirate

-bodhi
===========================
Forum Wiki
bodhi's corner
bodhi Wrote:
-------------------------------------------------------
> Goetz,
>
> > Do I've to do anything special when loading
> uboot
> > with JTAG?
>
> Same as I responded to other poster here in Debian
> section:
> http://plume.redox.ws/article13/dockstar-debrickin
> g-jtag-with-buspirate

By the way it's good to read that, i have a buspirate ^^. So if ever I have a problem, now i know how to fix it ^^.
Val532,

Here is the u-boot image for the Lacie D2Net_V2.

uboot.2014.01-tld-1.d2net_v2.bodhi.tar
md5:
7cbefcb8042c4fdc7711deefa846a97f

I don't have the Lacie, so cannot test it. So please do not flash to mtd0. Boot with UART first as instructed by davygravy.

Also, please post the entire boot log when you can connect UART and boot.

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

Thanks, i will test it this week-end, and when it's done i will post the result.
Can someone confirm that netconsole is working in uboot.2014.01-tld-1.dockstar? I can't seem to get it to work. I have three dockstars, two running a 2011 daveygravey uboot and the third recently updated to 2014.0.01. I have no trouble connecting to netconsole with the two dockstars with the 2011 uboot, but for the life of me can get the new uboot to connect. It does, however boot into my usb harddrive installed slackwarearm 14.1 without problems.

Also is there a way to verify uboot firmware version from the booted slackwarearm os.

Thanks for you help.
Hi laprjns,

netconsole does work in uboot.2014.01-tld-1 for dockstar. Is there anything peculiar about the 3rd setup hardware-wise, e.g. bridge, switch...?

To look at u-boot version without serial console:
grep -a --null-data U-Boot /dev/mtd0ro

-bodhi
===========================
Forum Wiki
bodhi's corner
I recently acquired another Dockstar.

I could not get SSH access easily, so I activated it on Pogoplug (software got upgraded to v.3.4.1), and got SSH access through the Pogoplug web interface.

I wanted to take mods in steps. First step: upgrade the uBoot (with above).

I was concerned with starting with Jeff's script (which uses a 2012 uBoot version), especially after having let my Pogoplug update (not sure what kernel version it is running, and I read about issues that prevent boot between newer linux kernel (what version of kernel is running in Pogoplug v.3.4.1?) and older uBoot), and so I decided to approach things manually.

After SSH'ing in, I took the following manual steps:

1. I installed the following binaries in /usr/bin (chmod 755): nanddump, nandwrite, flash_erase, blparam, fw_printenv (with ln -s to make fw_setenv);
2. I set appropriate uBoot variables using Jeff's original fw_env.config (chmod 644 in /etc/);
3. I added additional variables per the instructions in the first post of this thread; and
3. I setup netconsole per http://forum.doozan.com/read.php?3,14 (I could not test if it worked, but THANKFULLY, it did).

I then tried booting, and I get netconsole working, but I got the following bootloop:

U-Boot 2014.01-tld-1 (Mar 17 2014 - 22:04:15)
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: 6
U-Boot 2014.01-tld-1 (Mar 17 2014 - 22:04:15)
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

Then it spits out a whole lot about timing out in not finding boot image and using a boot image AXXXXXX.img.

I can access the netconsole (by hitting a key during the boot sequence), and when I do, I get the following uBoot environment:

DockStar> p r i n t e n v
arcNumber=2998
baudrate=115200
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=10
ethact=egiga0
ethaddr=00:10:75:1a:96:aa
if_netconsole=ping $serverip
ipaddr=10.0.31.71
ncip=10.0.31.30
preboot=run if_netconsole start_netconsole
serverip=10.0.31.30
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc

How do I need to modify the uBoot environment to boot up into the Pogoplug software?

I look forward to getting this stable so that I can move onto next steps.

Also, any recommendations for current state of NAND install of Debian are much appreciated.

Thanks in advance for any help.
dinlaca,

You have missed a crucial step by installing this U-Boot manually from stock U-Boot. The manual instruction indicated that the starting point is after you have already installed U-Boot with Jeff's script and now want to upgrade. Jeff's script installs U-Boot image and also flashes a good U-Boot envs image which include all the envs needed to boot with USB.

Quote

This assumes that your plug has been installed with Jeff's official installation script.

So basically, because you've started with stock U-Boot, you should have done this extra step right after flashing new U-Boot:

- Download Jeff's uBoot envs image at http://download.doozan.com/uboot/files/environment/uboot.environment.
- And then flash it to mtd0 at 0xC0000.
- See an example in this thread:
http://forum.doozan.com/read.php?2,11663


However, now it's more complicate to do that in netconsole, so you can just manually set the envs at netconsole using setenv. Here are my Dockstar envs:
arcNumber=2998
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:XX:XX:XX
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
if_netconsole=ping $serverip
ipaddr=192.168.0.220
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)
ncip=192.168.0.224
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot_nc=run if_netconsole start_netconsole
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
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.0.224
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=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_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan; setenv usb_root LABEL=rootfs
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext3
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
preboot=run preboot_nc
uboot_version=U-Boot 2014.01-tld-1 (Mar 17 2014 - 22:04:15)

And remember, don't do saveenv. Capture what envs you have set in a log file and then repeat that in Debian using fw_setenv and fw_printenv. This is to ensure that you will not be locked out by a mistake in typing.

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



Edited 1 time(s). Last edit at 04/23/2014 03:04AM by bodhi.
I have a dockstar with Gorgone's Debian Squeeze Heavy 2.6.37 installed. I'd like to update the u-boot, and the configuration looks correct in accordance with the checks you suggest in post 1. However, I don't have flash_erase installed. So I have two questions.

1. Should I be able to safely install with what I have on the dockstar?
2. How do I install flash_erase (and any other needed utilities)?

Thanks.
lyzby,

1. Your question is very hard to answer without seeing:
- u-boot version
- u-boot envs listing
- dmesg output

2. In Debian:
apt-get install mtd-utils

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



Edited 1 time(s). Last edit at 05/05/2014 10:04PM by bodhi.
Sorry, you can't reply to this topic. It has been closed.