[How-To] Boot Entirely from SATA

[fixsony]

Sorry I am a newbie in linux. In `disk_create` script I changed the address /dev/sdb. MY question what is (you may run the script via `./disk_create`) From my understanding I double clicked on disk_create and run as terminal. Is this correct? All other steps are understandable, but this step (run the script via `./disk_create`) Is very unclear to me. Please help me.

[0123456789]

$this->bbcode_second_pass_quote('fixsony', 'S')orry I am a newbie in linux. ... MY question what is (you may run the script via `./disk_create`)...

[obaltus]

Hello,

Can this procedure also be applied on the Iomega HMHND CE which shares the same SoC?


Thank you,

[WarheadsSE]

Yes, but note that as of this moment, the LEDs are not supported, and that you MUST use the uImage.nopci. I would trial this on a separate disk than the one that comes in the HMNDCE, prior to going all in. The formatting & partition breakdown is much different than with the HMNDCE stock image.

[obaltus]

Great. Thank you for your quick answer.

[obaltus]

Hello,

I think, I have followed the instruction correctly. But I am getting a bad magic number when uboot tries to load the kernel image on my Iomega HMNHD CE.

Did I miss something?
Btw: Overclocking does not work on IOMEGA hardware

Here is the console output;

$this->bbcode_second_pass_code('', 'Stage-1 Bootloader Mon Nov 14 22:15:13 EST 2011
Attempting to set PLLA to 700MHz ...
plla_ctrl0 : 0x0000000A
plla_ctrl1 : 0x000E0000
plla_ctrl2 : 0x001B01A0
plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001FB34
Hdr CRC: 0x2229BDCD
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: ST32000542AS Firm: CC38 Ser#: 5XW2RHFR
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
Device 1: not available
Environment successfully read from disk 0 primary image


U-Boot 1.1.2 (Dec 31 2011 - 15:24:45)

U-Boot code: 60E00000 -> 60E1FB34 BSS: -> 60E5435C
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:No NAND device found!!!
0 MiB
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value

IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 3 2 1 0

IDE device 0: Model: ST32000542AS Firm: CC38 Ser#: 5XW2RHFR
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
... is now current device

IDE read: device 0 block # 1290, count 5700 ... 5700 blocks read: OK

IDE read: device 0 block # 16674, count 5700 ... 5700 blocks read: OK
## Booting image at 60500000 ...
Image Name: Linux-2.6.31.14
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2189152 Bytes = 2.1 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... Bad Data CRC
Light LED

IDE device 0: Model: ST32000542AS Firm: CC38 Ser#: 5XW2RHFR
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
... is now current device

IDE read: device 0 block # 58344, count 5700 ... 5700 blocks read: OK

IDE read: device 0 block # 16674, count 5700 ... 5700 blocks read: OK
Extinguish LED
## Booting image at 60500000 ...
Bad Magic Number
Unknown command 'lightled' - try 'help'
$ ')

[WarheadsSE]

Well.. I see 700mhz which is 100mhz more than stock. I can generate a 600Mhz if you want.

I need to make you a 256MB uboot anyways.

[WarheadsSE]

Also.. why the heck is it trying to read the blocks? I have it configured as a partition!

[obaltus]

No 700MhZ is quite nice If you can supply a uboot version that handles the 256MB, it would be cool.
Do you think that the problem is related to the hardware? Or maybe to some mistakes I made during the procedure?

[WarheadsSE]

Interrupt the boot sequence, and get me a printenv