Welcome! Log In Create A New Profile

Advanced

GoFlexHome u-boot 2017-07-tld-1

Posted by balanga 
GoFlexHome u-boot 2017-07-tld-1
November 12, 2017 02:56PM
I'm trying to update u-boot on a GoFlexHome dock according to instructions here:-

https://forum.doozan.com/read.php?3,12381

I've downloaded uboot.2017.07-tld-1.goflexhome.bodhi.tar from https://bitly.com/2zQWP4Y , and made sure I made the appropriate tools.

/etc/fw_env.config has been copied

running cat /proc/mtd gives me:-

dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd2: 0ff00000 00020000 "rootfs"

rather than what it suggested:-

dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 0db00000 00020000 "data"

...so I'm not at sure how to proceed.
Re: GoFlexHome u-boot 2017-07-tld-1
November 12, 2017 05:26PM
balanga,

Quote

> I'm trying to update u-boot on a GoFlexHome dock
> according to instructions here:-
>
> https://forum.doozan.com/read.php?3,12381
>
> I've downloaded
> uboot.2017.07-tld-1.goflexhome.bodhi.tar from
> https://bitly.com/2zQWP4Y , and made sure I made
> the appropriate tools.
>
> /etc/fw_env.config has been copied
>
> running cat /proc/mtd gives me:-
>
> dev: size erasesize name
> mtd0: 00100000 00020000 "u-boot"
> mtd2: 0ff00000 00020000 "rootfs"
>
> rather than what it suggested:-
>
> dev: size erasesize name
> mtd0: 00100000 00020000 "u-boot"
> mtd1: 00400000 00020000 "uImage"
> mtd2: 02000000 00020000 "rootfs"
> mtd3: 0db00000 00020000 "data"
>
> ...so I'm not at sure how to proceed.

Ignore the difference. The only thing that matters is mtd0, which is identical.

> mtd0: 00100000 00020000 "u-boot" 
> mtd0: 00100000 00020000 "u-boot"

Without going into much detailed explanation why Arch mtds definition is that way. Recall in previous thread, I mentioned that you should ignore mtd1,2,3,4,... They are not relevant to booting Debian or Arch rootfs on USB.

So keep continuing with next steps!

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



Edited 1 time(s). Last edit at 11/12/2017 05:27PM by bodhi.
Re: GoFlexHome u-boot 2017-07-tld-1
November 13, 2017 03:01AM
OK thanks for the reassurance. Carrying on...at the end of section 8e in A. Flashing Instruction: https://forum.doozan.com/read.php?3,12381

fw_setenv mtdparts 'xxxxxxxxx'
fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'

I'm unclear as to what the value for mtdparts should be...
Re: GoFlexHome u-boot 2017-07-tld-1
November 13, 2017 04:26AM
balanga,

Since you have decided not to use Arch u-boot, don't use Arch definition of 2 mtds. You might as well set it to the traditional definition of 4 mtd partitions:
fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)'

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: GoFlexHome u-boot 2017-07-tld-1
November 13, 2017 10:54AM
OK I've managed to update U-Boot now. Is it possible for the unit to boot up without needing a USB stick or SATA drive, ie to have rootfs in NAND?
Re: GoFlexHome u-boot 2017-07-tld-1
November 13, 2017 12:25PM
Just wondered if everything starts up as expected...



U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 -0700)
Seagate GoFlex Home
Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0 
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 Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	15278144  	41e49ae4-01	83 Boot

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
747 bytes read in 830 ms (0 Bytes/s)

no IDE devices available
Unknown command 'mmc' - try 'help'
importing envs ...
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 661 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3154896 bytes read in 1129 ms (2.7 MiB/s)
loading uInitrd ...
7179935 bytes read in 1169 ms (5.9 MiB/s)
loading DTB /boot/dts/kirkwood-goflexhome.dtb ...
10605 bytes read in 2721 ms (2.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   5:55:25 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3154832 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000

Starting kernel ...

Re: GoFlexHome u-boot 2017-07-tld-1
November 13, 2017 04:15PM
balanga,

Quote

> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31
> -0700)
> Seagate GoFlex Home

> Found bootable drive on usb 0

> loading uImage ...
> 3154896 bytes read in 1129 ms (2.7 MiB/s)
> loading uInitrd ...
> 7179935 bytes read in 1169 ms (5.9 MiB/s)
> loading DTB /boot/dts/kirkwood-goflexhome.dtb ...
> 10605 bytes read in 2721 ms (2.9 KiB/s)

> ## Booting kernel from Legacy Image at 00800000
> ...
> Image Name: Linux-4.4.0-kirkwood-tld-1
> Created: 2016-02-19 5:55:25 UTC
> Image Type: ARM Linux Kernel Image
> (uncompressed)
> Data Size: 3154832 Bytes = 3 MiB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 01100000 ...
> Image Name: initramfs-4.4.0-kirkwood-tld-1
> Created: 2016-02-19 7:33:04 UTC
> Image Type: ARM Linux RAMDisk Image (gzip
> compressed)
> Data Size: 7179871 Bytes = 6.8 MiB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 01c00000
> Booting using the fdt blob at 0x1c00000
>
> Starting kernel ...
>

Congrat! it looks good.

Now you can either find its IP in your router, and login with it. Or you can also try
ping debian.local

And if found, login as
ssh root@debian.local

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: GoFlexHome u-boot 2017-07-tld-1
November 13, 2017 04:15PM
By the way, you are running an old rootfs (4.4). But it is an LTS kernel so it's OK. However, then you upgrade this rootfs to the latest kernel, you will need to adjust fstab a little bit to conform to the new rules regarding rootfs device.

Your root device should look like this in /etc/fstab:

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

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

Your Email:


Subject:


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