I have a strange problem, when a try to boot linux in this board.
I am using:
CPU AT91SAM9260. 64MBytes of ram,
Bootstrap from Atmel. compiled with GCC arm-elf-gcc version 3.4.3
U-Boot version - 1.3.4. compiled with GCC arm-elf-gcc version 3.4.3
kernel 2.6.23. compiled with GCC arm-elf-gcc version 3.4.3
busybox 1.12.2 compiled with GCC arm-linux-gcc version 4.2.4
initrd made by me.
all software compiled with uclib, and it is recorded into a datasflash.
The kernel boots normal until it opens a /dev/console that opens ok
I put a several debugs messages(that appears into serial terminal), into kernel to know what happen when it try to open /sbin/init, and I got a message saying that /sbin/init opened OK, althought I did not receive any message from busybox at this moment.
But I did not get a prompt to login or another message, but if I write something into terminal, i got the ecos, so cpu are running some program.
As you can see I typed ls, ps -ef and try to execute a hello word that is into /sbin
My linux outputs:
Linux version 2.6.23 (email@example.com) (gcc version 3.4.3) #21 PREEMP
T Fri Nov 21 21:20:41 BRST 2008
CPU: ARM926EJ-S  revision 5 (ARMv5TEJ), cr=00053177
Machine: Olimex SAM9-L9260
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order. Total pages: 16256
Kernel command line: console=ttyS0,115200 mem=64M root=/dev/ram0 rw
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60568KB available (2680K code, 751K data, 108K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
tered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 750K
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 108K
DEBUG: Opening /dev/console
DEBUG: executing ramdisk_execute_command... <4> OK
DEBUG: calling /sbin/serttys0
DEBUG: try to run[/sbin/serttys0]
kernel_execve:EXECUTING [/sbin/serttys0]...<4>:Returned OK ret=
As you can see I typed ls, ps -ef and try to execute a hello word that is into /sbin, this hello word program runs when I use an arm simulator qemu with this ram disk image(initrd).
I am lost with this problem, because, the problem doesn't seem to be in kernel, or busybox and or into filesystem(initrd).
Has somebody any susgestions to me?
Any help will be coming well.