Atmel website | ARM Community | AVR freaks | Technical Support
Banner
 FAQ •  Search •  Register •  Login 

All times are UTC + 1 hour [ DST ]




Post new topic Reply to topic  [ 2 posts ] 
Author Message
 Post subject: Linux on at91sam9rl64
PostPosted: Wed Feb 13, 2008 6:45 pm 
Offline

Joined: Mon Oct 08, 2007 4:47 pm
Posts: 2
I have got trouble to run linux on at91sam9rl64 platform.
I build Bootstrap-V1.6 for at91sam9rlek.
I build u-boot 1.1.5 from linux4sam with u-boot 1.1.5 atmel patch.
I build kernel 2.6.22 from linux4sam with at91 patches.
I modified script from linux_solutions_pack_1_0 to download Bootstrap, u-boot, kernel and rootfs image.
When u-boot load kernel to sdram, it failed due to BAD DATA CRC.
Here is the log file:

U-Boot 1.1.5 (Feb 12 2008 - 13:04:37)

DRAM: 64 MB
NAND: No NAND device found!!!
No NAND device found!!!
0 MiB
DataFlash:AT45DB642
Nb pages: 8192
Page Size: 1056
Size= 8650752 bytes
Logical address: 0xC0000000
Area 0: C0000000 to C0003FFF (RO)
Area 1: C0004000 to C0007FFF
Area 2: C0008000 to C0037FFF (RO)
Area 3: C0038000 to C083FFFF
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
## Booting image at 22200000 ...
Image Name: linux-2.6.22-at91sam9rl64
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 972780 Bytes = 950 kB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... Bad Data CRC
U-Boot>


U-Boot> printenv
ethaddr=3a:1f:34:08:54:54
bootdelay=3
baudrate=115200
bootargs=mem=64M console=ttyS0,115200 root=/dev/mtdblock0 rw rootfstype=jffs2
bootcmd= cp.b 0xC0040000 0x22200000 ; bootm 0x22200000
stdin=serial
stdout=serial
stderr=serial

Environment size: 238/16380 bytes
U-Boot>

I do not understand why the file size displayed by printenv "0x000ED82C" is different from Data Size (972780 Bytes = 0x000ED7EC) from kernel header.
with u-boot, I checked first bytes in SDRAM at address 0x22200000, which are good. I do not find a way to dump all the kernel from sdram to make a diff with original one.

Some ideas about this BAD DATA CRC.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Feb 15, 2008 12:12 pm 
Offline

Joined: Mon Oct 08, 2007 4:47 pm
Posts: 2
It was due to a bad copy from data flash to SDRAM by u-boot. For now I solve the problem by loading kernel image to SDRAM with Samba tool.
I have got the same problem with the root file system now, the copy in Nand flash is wrong and this with tcl script or Samba tool.
Does somebody already have Nand flash copy issue with samba?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC + 1 hour [ DST ]


Who is online

Users browsing this forum: Google [Bot] and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: