GoFlexHome> run bootcmd_uenv starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... Use USB retry period from the environment: 15 second(s) 1 Storage Device(s) found Reset IDE: ide_preinit failed Unknown command 'mmc' - try 'help' Partition Map for USB device 0 -- Partition Typby balanga - uBoot
cat boot/uEnv.txt:- printenv fatdev=usb 0:1 loaderdev=usb 0:1 bootfile=ubldr fdtfile=db88f6281.dtb kernel_addr_r=0x01000000 loadaddr=0x02000000 pxefile_addr_r=0x00100000 ramdisk_addr_r=0x02100000 scriptaddr=0x00000000 bootcmd=usb start;fdt addr 0x100;fatload ${fatdev} ${loadaddr} ${bootfile} && bootelf ${loadaddr} uBoot log:- Script started on Wed Mar 13 16:16:42 2019 Cby balanga - uBoot
The problem may be due to my envs... If I install uboot.2016.05-tld-1.environment.bodhi.tar should I expect to boot OpenWrt? ISTR that I needed to add/change something in the process of getting it working.... My current envs are:- api_address=7b12860 arcNumber=3338 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede bootcmd_exec=if run load_uiby balanga - uBoot
bodhi, Maybe I didn't explain properly, my current /boot/uEnv.txt on a FAT partition on my USB stick contains:- ootfile=ubldr.bin loadaddr=0x02000000 fdt_file=db88f6281.dtb uenvcmd=echo Booting FreeBSD from SD Card: ; mmcinfo && fatload mmc 0 ${loadaddr} ${bootfile} && bootelf but it looks like uBoot does not seem to take any input from this file. Can you suggby balanga - uBoot
I have a FAT partition on a USB stick which is not being read using normal envs. Can't understand why... envs:- uenv_addr=0x810000 uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtby balanga - uBoot
bodhi Wrote: ------------------------------------------------------- > > Is there any way to temporarly disable nc? I'm > > finding it a pain to watch the boot process > start > > under minicom but don't get a prompt to stop > > autoboot. I have to watch the nc session > > elsewhere. Is it possible to change the process > so > > that ifby balanga - uBoot
bodi, bodhi Wrote: ------------------------------------------------------- > balanga, > > > > Now I wonder if it's possible to boot either > from > > the same USB stick :)... > > Of course it is possible! With envs adjustment to > look for the kernel and rootfs in the correct > partition. Basically you will have 2 partitions > each houseby balanga - uBoot
balanga Wrote: ------------------------------------------------------- > I managed to remount it rw using:- > > mount -o remount,rw /dev/sda1 / > > > but don't know how to make it persistant. I note > that fstab is empty:- > > # cat /etc/fstab > # Static information about the filesystems. > # See fstab(5) for details. > > # <file sysby balanga - uBoot
habibie, Many thanks for starting this topic, I've just managed to get Arch Linux booting with one of bodhi's uBoots following instructions here. Arch Linux boots fine, the only trouble is that the USB stick is mounted ro:- /dev/sda1 on / type ext3 (ro,relatime,data=ordered) I managed to remount it rw using:- mount -o remount,rw /dev/sda1 / but don't know how to mby balanga - uBoot
bodhi, balanga Wrote: ------------------------------------------------------- > bodhi, > > With lots of help from yourself I now have a > GoFlex Home which has u-boot > uboot.2017.05-tld-2.goflexhome.mtd0.kwb installed > in flash. OpenWrt is also installed in flash and > boots OK. Debian also boots up from USB, but I > haven't yet managed to get ArchLinuby balanga - uBoot
bodhi, With lots of help from yourself I now have a GoFlex Home which has u-boot uboot.2017.05-tld-2.goflexhome.mtd0.kwb installed in flash. OpenWrt is also installed in flash and boots OK. Debian also boots up from USB, but I haven't yet managed to get ArchLinux to boot. The envs (uboot.2016.05-tld-1.environment.bodhi.tar) have not yet been flashed and after comparing those variablesby balanga - uBoot
bodhi, bodhi Wrote: ------------------------------------------------------- > balanga, > > > -rwxr-xr-x 1 root root 512K Jul 26 2017 > uboot.2017.05-tld-2.goflexhome.mtd0.kwb > > > That has refreshed my memory and confirmed why it > worked when you flashed this u-boot! > > This version image is the same size as other > u-boots (512K) becauseby balanga - uBoot
bodhi Wrote: ------------------------------------------------------- > To confirm, please list this -tl-2 u-boot image so > I can see the timestanmp and size: > > > ls -lh <image> > ls -l <image> > # ls -lh uboot.2017.05-tld-2.goflexhome.mtd0.kwb -rwxr-xr-x 1 root root 512K Jul 26 2017 uboot.2017.05-tld-2.goflexhome.mtd0.kwb # ls -l uboot.2017.05by balanga - uBoot
bodhi Wrote: ------------------------------------------------------- > To confirm, please list this -tl-2 u-boot image so > I can see the timestanmp and size: > > > ls -lh <image> > ls -l <image> > bodhi, I'll post the above later... > And also post the link to the post where I > attached this u-boot. Took some time to find :)by balanga - uBoot
bodhi Wrote: ------------------------------------------------------- > balanga, > > That instruction is for Phogo V4. It is needed to > be modified for GoFlex Home. > > If you did exactly as the instruction stated, you > have overwritten the GF Home stock kernel in NAND! > so that's why it did not boot. > > Please post the log of what you did, asby balanga - Rescue System
bodhi Wrote: ------------------------------------------------------- > For each mtd on the list > > > cat /proc/mtd > > > > You would do > > > nanddump --noecc --omitoob -f mtd0.gfh > /dev/mtd0 > nanddump --noecc --omitoob -f mtd1.gfh > /dev/mtd1 > > > and so on. bodhi, What about a restore? I tried followinby balanga - Rescue System
In https://forum.doozan.com/read.php?3,16789,16789#msg-16789 it mentions restoring mtd0, but what about mtd1 and mtd2 which were saved at the same time as mtd0? Presumably the original instructions for the Pogoplug V4 can be adapted to a GoFlex Home... although I'm not sure if anything needs to be changed.by balanga - uBoot
My aim is to create a simple guide for installing OpenWrt on a GoFlex Home unit. If I kwboot from uboot.2017.07-tld-1 and use the envs from uboot.2016.05-tld-1.environment amended for GoFlex Home, ie. setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'. setenv partition 'nand0,0'. setenv set_bootargs_openwrt 'setenv bootargs console=tby balanga - Rescue System
bodhi, OK will do. Didn't mean to ignore your request.by balanga - uBoot
My aim is to create a simple guide for installing OpenWrt on a GoFlex Home unit. If I kwboot from uboot.2017.07-tld-1 and use the envs from uboot.2016.05-tld-1.environment amended for GoFlex Home, ie. setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'. setenv partition 'nand0,0'. setenv set_bootargs_openwrt 'setenv bootargs console=ttyS0by balanga - uBoot
bodhi Wrote: ------------------------------------------------------- > balanga, > So the envs below are from internal u-boot > definition. I've used the same set of envs for > both (image, and internal). bodhi, I'm still not sure of the source of environment variables... I want to test some procedures I've written and would like to start with a pristineby balanga - uBoot
Managed to get it working! Will try and document what I did.by balanga - Rescue System
I'm wondering what I should expect to be the output from cat /proc/mtd Mine currently shows:- root@OpenWrt:/# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 0ff00000 00020000 "ubi"by balanga - Rescue System
I am unable to access the USB drive using:- mount /dev/sda1 /mnt I get 'invalid argument'. It seems I need to:- opkg install kmod-usb-storage but there is no room to install it. How do I tell what is taking up the space? Maybe FLASH is not set up correctly...by balanga - Rescue System
Koen Wrote: ------------------------------------------------------- > The combined initramfs-uImage is a minimal openwrt > system that can be run from memory (RAM). To > install openwrt to the internal memory / nand you > will need to follow the instructions to do a > sysupgrade from command line. The general > procedure is described here: > https://openwrt.org/docs/gby balanga - Rescue System
bodhi Wrote: ------------------------------------------------------- > balanga, > > > but on reboot I needed to do the same thing. > How > > do I install this uImage and boot from it > > permanently? > > Sounds to me like you have not finished the > installation procedure completely. > > You can post this question in joerg's thread soby balanga - Rescue System
I managed to boot OpenWrt 18.06.2 by following this step:- 3. Run the following code for starting the process: # @bootloader run LEDE from usb pendrive usb reset; fatload usb 0 0x800000 lede-kirkwood-pogo_e02-initramfs-uImage; bootm 0x800000 changing the lede-kirkwood-pogo_e02-initramfs-uImage to openwrt-18.06.2-kirkwood-seagate_goflexhome-initramfs-uImage https://downloads.oby balanga - Rescue System
Has anyone tried to install OpenWrt 18.06.2?by balanga - Rescue System
bodhi Wrote: ------------------------------------------------------- > However, you can't flash this u-boot to NAND yet. > This u-boot is quite big comparing my official > released u-boots for GF Home. I will have to write > a few new instruction before you can flash it > permanently to NAND. > > In the mean time, you can use kwboot to run it > succssfully aby balanga - uBoot
If changing from 2017.07-tld-1 to 2017.05-tld-2 is there anything in particular to watch out for? ie environment changes. I guess any OS specific requirements should be changed in /boot/uEnv.txt... Is the uBoot change basically done via nandwrite /dev/mtd0 uboot.2017.05-tld-2.goflexhome.mtd0.kwb and the environment set from rwt uboot.2016.05-tld-1.environment.bodhi.tar ?l As foby balanga - uBoot