IX4-200D CLOUD BAD MAGIC NUMBER

Post Reply
vincieh
Posts: 6
Joined: Wed May 27, 2015 12:43 pm

IX4-200D CLOUD BAD MAGIC NUMBER

Post by vincieh » Thu May 28, 2015 9:04 pm

Hi All

I have a ix4-200d cloud edition and the bios update from usb failed. I too have repeated reboots . I have read many posts forum and have been successfully able to console into the machine. Ive followed everybody's commands for tftpboot, etc. everytime I get the bad magic error after about 5%. ive tried the files from ix4-200d-3.2.6.17887-recovery

IPLEASE! PLEASE! PLEASE! any assistance would be greatly appreciated. ive spend hours surfing the web and I don't think there is much of anything that I haven't tried that ive found so far

__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** uboot_ver:v1.1.1 **

** MARVELL BOARD: IX4-110 LE

U-Boot 1.1.4 (Mar 10 2011 - 15:01:57) Marvell version: 3.4.18

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

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM 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
Found 0x20 i2c device
Set Power State as Always On
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB
Found ADT7473, program LED ...(led_volt=90) OK
Found ADT7473, program thermal/Fan ...(pwm_min=0) (pwm_max=130) (therm=67) (temp_min=60) OK

Marvell Serial ATA Adapter
Integrated Sata device found


CPU : Marvell Feroceon (Rev 1)
Found initrd at 0x2d8000

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is RGMII

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
SCSI: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode
flags: 64bit ncq stag led pmp slum part
scanning bus for devices...
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0xb0000, size 0x228000

Reading data from 0x2d7e00 -- 100% complete.
2260992 bytes read: OK

NAND read: device 0 offset 0x2d8000, size 0x2f0000

Reading data from 0x2fd800 -- 5% complete.reading NAND page at offset 0x304000 failed
3080192 bytes read: ERROR
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8
Created: 2012-02-13 21:48:28 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2077080 Bytes = 2 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 12000000 ...
Bad Magic Number▒

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: IX4-200D CLOUD BAD MAGIC NUMBER

Post by Mijzelf » Fri May 29, 2015 9:44 am

'Bad Magic Number' means here that the uImage header found at address 12000000 in flash has a wrong magic number, which probably means that either you didn't write a valid uImage to this address, or it is overwritten by some other action. What are the exact commands you used to flash the firmware?

vincieh
Posts: 6
Joined: Wed May 27, 2015 12:43 pm

Re: IX4-200D CLOUD BAD MAGIC NUMBER

Post by vincieh » Fri May 29, 2015 6:06 pm

hi.

Thanks for the reply. I used flash image ix4-200d-3.2.6.17887-recovery

and originally used the following commands

resetenv
tftpboot 0x2000000 zImage
tftpboot 0x12000000 initrd
nand erase 0x2d4000 0x2f000
nand erase 0xb0000 0x224000
nand write.e 0x12000000 0x2d4000 0x2f0000
nand write.e 0x2000000 0x0b0000 0x224000
reset

One of the posts seem to suggest that the space reserved for initrd may not be enough for the file size.

I started playing with the next values to have enough space for the number of bytes needed for initrd and zimage

I now tried:
resetenv
tftpboot 0x2000000 zImage
tftpboot 0x12000000 initrd
nand erase 0x2d4000 0x2e4047
nand erase 0xb0000 0x1fb1d8
nand write.e 0x12000000 0x2d4000 0x2e4047
nand write.e 0x2000000 0x0b0000 0x1fb1d8
reset

with that approach I get 100% read but same error

__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** uboot_ver:v1.1.1 **

** MARVELL BOARD: IX4-110 LE

U-Boot 1.1.4 (Mar 10 2011 - 15:01:57) Marvell version: 3.4.18

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

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM 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
Found 0x20 i2c device
Set Power State as Always On
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB
Found ADT7473, program LED ...(led_volt=90) OK
Found ADT7473, program thermal/Fan ...(pwm_min=0) (pwm_max=130) (therm=67) (temp_min=60) OK

Marvell Serial ATA Adapter
Integrated Sata device found


CPU : Marvell Feroceon (Rev 1)
Found initrd at 0x2d8000

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is RGMII

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
SCSI: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode
flags: 64bit ncq stag led pmp slum part
scanning bus for devices...
Device 0: (0:0) Vendor: ATA Prod.: ST3500312CS Rev: SC13
Type: Hard Disk
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 1
(pwm_max=130) (therm=67) (temp_min=60) OK

Marvell Serial ATA Adapter
Integrated Sata device found


CPU : Marvell Feroceon (Rev 1)
Found initrd at 0x2d8000

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is RGMII

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
SCSI: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode
flags: 64bit ncq stag led pmp slum part
scanning bus for devices...
Device 0: (0:0) Vendor: ATA Prod.: ST3500312CS Rev: SC13
Type: Hard Disk
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0xb0000, size 0x228000

Reading data from 0x2d7e00 -- 100% complete.
2260992 bytes read: OK

NAND read: device 0 offset 0x2d8000, size 0x300000

Reading data from 0x5d7e00 -- 100% complete.
3145728 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8
Created: 2012-02-13 21:48:28 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2077080 Bytes = 2 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 12000000 ...
Bad Magic Number▒

Mijzelf
Posts: 6199
Joined: Mon Jun 16, 2008 10:45 am

Re: IX4-200D CLOUD BAD MAGIC NUMBER

Post by Mijzelf » Sat May 30, 2015 9:20 am

bootlog wrote:NAND read: device 0 offset 0x2d8000, size 0x300000
vincieh wrote:nand erase 0x2d4000 0x2f000
nand write.e 0x12000000 0x2d4000 0x2f0000
You are flashing it at another address as where u-boot tries to read it. And u-boot also uses a bigger size. (That size is not really important, as long as it's 'big enough'. The uImage header is read *after* it is copied to ram, and contains the real size.)

Now you have two possibilities:
  • Change the address for the initrd in the u-boot environment. (printenv, setenv and saveenv are the keywords, together with 'help')
  • Flash the images on the place where u-boot expects them.
Don't know where you got your flash instructions. If they are explicitely for the ix4-200D, then some point in time Iomega changed the flash division. And of course there is a reason for that. The flash is 32MB, and u-boot reads it up to 0x2b8000+0x300000=0x5b8000=5996544 ~6MB.
The other 26MB is used to contain the firmware which is meant to be installed on the harddisk. I guess that for the CE edition this was narrow, for which reason 'they' removed some slackspace from the lower addresses. Although that won't give more than a few hundred kB.

vincieh
Posts: 6
Joined: Wed May 27, 2015 12:43 pm

Re: IX4-200D CLOUD BAD MAGIC NUMBER

Post by vincieh » Sat May 30, 2015 10:11 am

Hi

Thanks for this

The instructions I received was not specifically for the cloud edition but was for how to flash to CE.

I couldn't fid anything specifically for the cloud edition here.

Your suggestion worked spot on.

For the benefit of others who may have had my issue:

resetenv
tftpboot 0x2000000 zImage
tftpboot 0x12000000 initrd
nand erase 0x2d8000 0x2e4047
nand erase 0xb0000 0x1fb1d8
nand write.e 0x12000000 0x2d8000 0x2e4047
nand write.e 0x2000000 0x0b0000 0x1fb1d8
reset

Post Reply