lenovo ix2-dl no boot bad data crc

Post Reply
ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

lenovo ix2-dl no boot bad data crc

Post by ruspray » Thu Nov 23, 2017 5:59 pm

did the https://www.servis-zlin.eu/clanky/obnov ... a-ix2-200/
now I see: __ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** ix2-nand ** ** uboot_ver:0.0.9 **

** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Mar 7 2014 - 17:48:48) Marvell version: 3.6.1 - EMC

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

Soc: 88F6282 A1 CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:1024 MB
Found ADT7473, program PWM1 ... OK
Flash: 0 kB

Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: ST3000VX000-1CU166 Firm: CV23 Ser#: W1F5C9XK
Type: Hard Disk
Supports 48-bit addressing
Capacity: 764436.4 MB = 746.5 GB (1565565872 x 512)
[0 1 0]: Enable DMA mode (6)
Device 1 @ 0 1:
Model: ST3000VX000-1CU166 Firm: CV23 Ser#: W1F5CBVY
Type: Hard Disk
Supports 48-bit addressing
Capacity: 764436.4 MB = 746.5 GB (1565565872 x 512)


CPU : Marvell Feroceon (Rev 1)
Found kernel at 0x100000
Could not found correct initrd

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
Marvell>> setenv ipaddr 192.168.100.10
Marvell>> setenv serverip 192.168.100.11
Marvell>> TFTPBoot 0x2000000 zImage
Unknown command 'TFTPBoot' - try 'help'
Marvell>> tftpboot 0x2000000 zImage
Using egiga0 device
TFTP from server 192.168.100.11; our IP address is 192.168.100.10
Filename 'zImage'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#############################################################
done
Bytes transferred = 3637872 (378270 hex)
Marvell>> tftpboot 0x5400000 initrd
Using egiga0 device
TFTP from server 192.168.100.11; our IP address is 192.168.100.10
Filename 'initrd'.
Load address: 0x5400000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################

done
Bytes transferred = 2994901 (2db2d5 hex)
Marvell>> nand erase 0x100000 0x300000

NAND erase: device 0 offset 0x100000, size 0x300000
Erasing at 0x3e0000 -- 100% complete.
OK
Marvell>> nand erase 0x540000 0x300000

NAND erase: device 0 offset 0x540000, size 0x300000
Erasing at 0x820000 -- 100% complete.
OK
Marvell>> nand erase 0x540000 0x300000

NAND erase: device 0 offset 0x540000, size 0x300000
Erasing at 0x820000 -- 100% complete.
OK
Marvell>> nand write.e 0x5400000 0x540000 0x300000

NAND write: device 0 offset 0x540000, size 0x300000

Writing data at 0x83f800 -- 100% complete.
3145728 bytes written: OK
Marvell>> nand write.e 0x2000000 0x100000 0x300000

NAND write: device 0 offset 0x100000, size 0x300000

Writing data at 0x3ff800 -- 100% complete.
3145728 bytes written: OK
Marvell>> boot

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

Reading data from 0x3ff800 -- 100% complete.
3145728 bytes read: OK

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

Reading data from 0x6ff800 -- 100% complete.
3145728 bytes read: OK
## Booting image at 00040000 ...
Image Name: Linux-3.2.40
Created: 2014-07-09 16:18:20 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3637808 Bytes = 3.5 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... Bad Data CRC

what am I doing wrong ?

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Thu Nov 23, 2017 6:00 pm

Marvell>> printenv
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
run_diag=yes
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethact=egiga0
kernel_size=0x300000
initrd_size=0x300000
loadzimage=nand read.e 0x40000 $(kernel_start) $(kernel_size)
loadinitrd=nand read.e 0x900000 $(initrd_start) $(initrd_size)
console=console=ttyS0,115200
bootargs_root=root=/dev/ram0
mk_mtdparts=setenv mtdparts mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),$(kernel_size)@$(kernel_start)(uImage),$(initrd_size)@$(initrd_start)(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash)
initrdimage=mfginitrd
mfgmodel=ix2
preroot_ver=0.0.2
fw_ver=4.1.102.29716
serial_number=5563Y01011G44600046J0L1
ethaddr=00:D0:B8:21:05:37
serialNo=1S70A69003NAS10006K3
modelname=70A69003NA
serialno=1,01WH/gcc9Fd5eEj+kdtLztw7B3sz0AXUqpnshBDIuZd9Vx08Y2sTF1yqcQlZ2swva0,1S70A69003NAS10006K3,
runintime=10800
ftpserver=192.168.43.4
testfile=100M
mfgtest_state=system_tested_ok
pre_path=IX2/1.1.1/download_runin.sh
pre_path_conf=IX2/1.1.1/download_runin.conf
pre_serverip=192.168.32.4
pre_user=ixxrunin
pre_passwd=123
pre_dirzi=IX2/1.1.1
bootcmd=run loadzimage; run loadinitrd; run mk_mtdparts; setenv bootargs $(console) $(bootargs_root) $(bootargs_end) $(mtdparts); bootm 0x40000 0x900000
initrd_start=0x400000
uboot_ver=0.0.9
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
kernel_start=0x100000
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
pcieTune1=no
filesize=2db2d5
fileaddr=5400000
netmask=255.255.255.0
ipaddr=192.168.100.10
serverip=192.168.100.11
mtdparts=mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),0x300000@0x100000(uImage),0x300000@0x400000(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash)
bootargs=console=ttyS0,115200 root=/dev/ram0 :::DB88FXX81:eth0:none mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),0x300000@0x100000(uImage),0x300000@0x400000(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash)

Environment size: 2659/131067 bytes

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

Re: lenovo ix2-dl no boot bad data crc

Post by Mijzelf » Fri Nov 24, 2017 7:14 am

First, an ix2-200 is a different beast as a ix2-dl, and I don't think a dl can boot a '200 kernel.

But that doesn't explain what you see. U-boot shouldn't complain, I only expect the kernel to eiher crash, or not be able to get the network up, or something like that.

In your case the problem is that an `200 kernel happens to be bigger than a 'dl kernel:

Code: Select all

Marvell>> tftpboot 0x2000000 zImage
<snip>
Bytes transferred = 3637872 (378270 hex)

Marvell>> nand write.e 0x2000000 0x100000 0x300000
<snip>
3145728 bytes written: OK
So your kernel (uImage) is 3637872 bytes in size, and you only write 3145728 bytes. No wonder that gives a CRC error.

(OK, something fishy is going on. The writer of that blog used the same size, so why did it fit for him?)

Now you shouldn't just write more bytes, there is no more space reserved for the kernel. You can try to repeat with kernel&initrd from ix2-ng-4.0.2.9960-recovery.zip.

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Fri Nov 24, 2017 9:52 am

I took where you advise me. ix2-ng-4.0.2.9960-recovery.zip
but wrote this:
tftpboot 0x2000000 zImage
tftpboot 0x5400000 initrd
nand erase 0x100000 0x300000
nand erase 0x540000 0x300000
nand write.e 0x2000000 0x100000 0x300000
nand write.e 0x5400000 0x540000 0x300000

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Fri Nov 24, 2017 10:00 am

replaced: zImage initrd
Now:
## Booting image at 00040000 ...
Image Name: Linux-2.6.31.8
Created: 2013-03-12 21:25:40 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2943440 Bytes = 2.8 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00900000 ...
Bad Magic Number
:?:

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

Re: lenovo ix2-dl no boot bad data crc

Post by Mijzelf » Fri Nov 24, 2017 11:15 am

According to your u-boot environment the NAND adresses are wrong:

Code: Select all

loadzimage=nand read.e 0x40000 $(kernel_start) $(kernel_size)
loadinitrd=nand read.e 0x900000 $(initrd_start) $(initrd_size)
So you should use 0x40000 and 0x900000 instead of 0x100000 and 0x540000. You have overwritten a part of your ubifs.

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Fri Nov 24, 2017 2:50 pm

Hit any key to stop autoboot: 0
Marvell>> setenv ipaddr 192.168.100.10
Marvell>> setenv serverip 192.168.100.11
Marvell>> tftpboot 0x2000000 zImage
Using egiga0 device
TFTP from server 192.168.100.11; our IP address is 192.168.100.10
Filename 'zImage'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#######################################################
done
Bytes transferred = 2943504 (2cea10 hex)
Marvell>> tftpboot 0x900000 initrd
Using egiga0 device
TFTP from server 192.168.100.11; our IP address is 192.168.100.10
Filename 'initrd'.
Load address: 0x900000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##################################
done
Bytes transferred = 2834433 (2b4001 hex)
Marvell>> nand erase 0x40000 0x300000

NAND erase: device 0 offset 0x40000, size 0x300000
Erasing at 0x320000 -- 100% complete.
OK
Marvell>> nand erase 0x900000 0x300000

NAND erase: device 0 offset 0x900000, size 0x300000
Erasing at 0xbe0000 -- 100% complete.
OK
Marvell>> nand write.e 0x2000000 0x40000 0x300000

NAND write: device 0 offset 0x40000, size 0x300000

Writing data at 0x33f800 -- 100% complete.
3145728 bytes written: OK
Marvell>> nand write.e 0x900000 0x900000 0x300000

NAND write: device 0 offset 0x900000, size 0x300000

Writing data at 0xbff800 -- 100% complete.
3145728 bytes written: OK
Marvell>> boot

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

Reading data from 0x3ff800 -- 100% complete.
3145728 bytes read: OK

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

Reading data from 0x6ff800 -- 100% complete.
3145728 bytes read: OK
## Booting image at 00040000 ...
Bad Magic Number
Marvell>>
Did not work out :(

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Fri Nov 24, 2017 3:16 pm

I used
tftpboot 0x2000000 zImage
tftpboot 0x900000 initrd
nand erase 0x40000 0x300000
nand erase 0x900000 0x300000
nand write.e 0x2000000 0x40000 0x300000
nand write.e 0x900000 0x900000 0x300000

what is wrong?

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

Re: lenovo ix2-dl no boot bad data crc

Post by Mijzelf » Fri Nov 24, 2017 3:43 pm

Oops!
Mijzelf wrote:According to your u-boot environment the NAND adresses are wrong:

Code: Select all

loadzimage=nand read.e 0x40000 $(kernel_start) $(kernel_size)
loadinitrd=nand read.e 0x900000 $(initrd_start) $(initrd_size)
So you should use 0x40000 and 0x900000 instead of 0x100000 and 0x540000. You have overwritten a part of your ubifs.
0x40000 and 0x900000 are the adresses in ram where the blobs are loaded. The NAND addresses are $(kernel_start) and $(initrd_start),

Code: Select all

initrd_start=0x400000
<snip>
kernel_start=0x100000

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Fri Nov 24, 2017 4:10 pm

tftpboot 0x2000000 zImage
tftpboot 0x900000 initrd
nand erase 0x100000 0x300000
nand erase 0x400000 0x300000
nand write.e 0x2000000 0x100000 0x300000
nand write.e 0x400000 0x400000 0x300000


that's right?

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Fri Nov 24, 2017 4:12 pm

I'm not strong at this just do not quite understand how goes the erasure from bigger to smaller

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

Re: lenovo ix2-dl no boot bad data crc

Post by Mijzelf » Fri Nov 24, 2017 5:46 pm

ruspray wrote:tftpboot 0x2000000 zImage
tftpboot 0x900000 initrd
nand erase 0x100000 0x300000
nand erase 0x400000 0x300000
nand write.e 0x2000000 0x100000 0x300000
nand write.e 0x400000 0x400000 0x300000


that's right?
No. The last line should be

Code: Select all

nand write.e 0x900000 0x400000 0x300000
I think.
ruspray wrote:I'm not strong at this just do not quite understand how goes the erasure from bigger to smaller
What do you mean?
The erase is 'nand erase startaddress size'

ruspray
Posts: 9
Joined: Thu Nov 23, 2017 5:48 pm

Re: lenovo ix2-dl no boot bad data crc

Post by ruspray » Sat Nov 25, 2017 8:51 am

generally there is no reaction to anything. buzzing fan burning all diodes in the terminal nothing is output
:cry: :cry: :cry:
I did not even have time to try a variant from the previous post

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

Re: lenovo ix2-dl no boot bad data crc

Post by Mijzelf » Sat Nov 25, 2017 10:26 am

I'm afraid my advice was wrong:
Mijzelf wrote:So you should use 0x40000 and 0x900000 instead of 0x100000 and 0x540000. You have overwritten a part of your ubifs.

Code: Select all

mk_mtdparts=setenv mtdparts mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),
0x40000 is in the midst of the u-boot partition of the nand (which is 0x80000 in size), and both env and env2 are erased. Don't know the purpose of env2. Sorry for that.

There are 2 possibilities left. JTAG or kwboot. Don't know the pinning for JTAG. Here you can find more on kwboot. It's basically a way to upload a new bootloader over the serial port, which you can use to flash another bootloader in nand.

Post Reply