[U-Boot-Users] Re: JFFS2: CRC Problem with Kernel Image

Martin, Vitali
2003-07-24T06:55:49Z

> How did the pImage file get to /dev/mtdblock1 in the first place?

bash-2.05# eraseall /dev/mtd1
bash-2.05# mount -t jffs2 /dev/mtdblock1 /mnt/
bash-2.05# cp /pImage /mnt/

> We had a problem a while back where using scp to copy an image ...

I'm using "cp" from the linux console, so I think there is no interrupt
problem.
Because I can copy pImage to JFFS2 filesystem and my image is still OK.

I checked the memory with "md 100000" in U-Boot and there seems to be
not the same data on the memory address 0x100 when I using "tftp 1000
pImage" and "fsload 10000 pImage". From address 0x101000 the data im the
RAM memory is different???

->tftp 10000 pImage
TFTP from server 172.22.20.193; our IP address is 172.22.10.33
Filename 'pImage'.
Load address: 0x10000
Loading: T ###################T #TX timeout
done
Bytes transferred = 520149 (7efd5 hex)
->md 100000 200000
00100000: 27051956 52c9c624 3f1d4bb5 0007ef95
'..VR..$?.K.....
00100010: 00000000 00000000 5171b599 05070201
........Qq......
00100020: 4c696e75 782d322e 342e3400 00000000
Linux-2.4.4.....
...
00101000: dfc958e0 5f66d603 e27f2fe3 0027f536
..X._f..../..'.6
00101010: c055f99e f5e16e85 bd761595 a9ce7bd2
.U....n..v....{.

->fsload 100000 pImage
### JFFS2 loading 'pImage' to 0x100000
### JFFS2 load complete: 520149 bytes loaded to 0x100000
->md 100000 200000
00100000: 27051956 52c9c624 3f1d4bb5 0007ef95
'..VR..$?.K.....
00100010: 00000000 00000000 5171b599 05070201
........Qq......
00100020: 4c696e75 782d322e 342e3400 00000000
Linux-2.4.4.....
...
00101000: dfc9c970 de53a432 188d2417 af469b2b
...p.S.2..$..F.+
00101010: 7dd3d9cf e1df4c64 65acdb75 83efc98b
}.....Lde..u....