Hi Dave,
many thanks again for your reply.
Now i am trying again to load image.bin all from the RAM. In particualr,
i run colilo bootloader, then i copy flash to ram with colilo command
"c" and run it from the ram.
Also, i discovered that "block device" support was disabled in make
menuconfig, and also a file system was missing.
Now i added block device and JFS file system.
The boot message is now a little different:
Linux version 2.6.25-uc0 (ang...@miri) (gcc version 4.1.1) #29 Sun Dec 6
12:07:20 CET 2009
uClinux/COLDFIRE(m5307)
COLDFIRE port done by Greg Ungerer, g...@snapgear.com
Modified for M5307 by Dave Miller, dmil...@intellistor.com
Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
Kernel command line:
PID hash table entries: 64 (order: 6, 256 bytes)
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory available: 13900k/16384k RAM, (1150k kernel code, 152k data)
Mount-cache hash table entries: 512
net_namespace: 152 bytes
NET: Registered protocol family 16
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 512 bind 1024)
TCP reno registered
JFS: nTxBlock = 108, nTxLock = 868
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
ColdFire internal UART serial driver
ttyS0 at MMIO 0x100001c0 (irq = 73) is a ColdFire UART
console [ttyS0] enabled
ttyS1 at MMIO 0x10000200 (irq = 74) is a ColdFire UART
dm9000 Ethernet Driver, V1.30
TCP cubic registered
NET: Registered protocol family 17
VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
Many thanks,
Angelo
Dave Meador ha scritto:
Hi Angelo,
You should be able to boot up out of memory first before worrying
about loading via flash. If you can't load from RAM you will surely
have problems loading from flash. Since you are loading image.bin you
are on the right track.
I recently had a problem similar to yours recently where I could not
boot up all the way and it was because my genromfs was too old. I
upgraded to genromfs v0.5 and everything worked after that.
What version of genromfs do you have?
I upgraded by running the following command as root:
yum install genromfs
To answer your question about the three files:
linux.bin - the linux kernel binary only
romfs.bin - the root filesystem image only
image.bin - linux.bin+romfs.bin ... linux loads then looks for the
romfs.bin signature at the end of the linux image and loads the root
filesystem
Regards,
Dave
angelo wrote:
Hi David and All,
many thanks,
i think i have some confusion still.
The log attached is related at the loading of linux.bin.
In the images folder i find:
ang...@miri:~/uClinux-dist/images$ ls
total 4693
drwxr-xr-x 2 angelo angelo 208 Aug 1 12:04 .
drwxr-xr-x 20 angelo angelo 824 Nov 22 10:38 ..
-rw-r--r-- 1 angelo angelo 1513472 Dec 5 15:07 image.bin
-rwxr-xr-x 1 angelo angelo 1767976 Aug 1 12:04 image.elf
-rwxr-xr-x 1 angelo angelo 1011712 Aug 1 12:04 linux.bin
-rw-r--r-- 1 angelo angelo 572 Aug 1 12:04 romfs-inst.log
-rw-r--r-- 1 angelo angelo 500736 Aug 1 12:04 romfs.img
ang...@miri:~/uClinux-dist/images$
Anyway. i don't have written in the flash image.bin and romfs.img.
I have a custom board, with 4 Megabytes 16bit word flash.
Plese could you explain or show me some link about what are exactly
these 3 files ? And eventually, how should i write them in the flash ?
many thanks.
Angelo
David Meador ha scritto:
Hi Angelo,
The last log entry tells me that you may not have a rootfs included
in your boot image because the kernel cannot find the "init" program:
Kernel panic - not syncing: No init found. Try passing init= option
to kernel
There are three binary components built and placed into
./uClinux-dev/images/... the linux.bin and romfs.bin, and image.bin.
Are you attempting to boot image.bin -- and not linux.bin?
Are you sure that you build a romfs.bin as part of your image.bin?
Double check in make menuconfig.
-Dave
On 12/04/2009 02:21 PM, angelo wrote:
Hello All,
i am trying to execute a first ucLinux kernel for MCF5307 i have
just compiled. This is the result.
Linux version 2.6.25-uc0 (ang...@miri) (gcc version 4.1.1) #27 Sat
Aug 1 12:03:13 CEST 2009
uClinux/COLDFIRE(m5307)
COLDFIRE port done by Greg Ungerer, g...@snapgear.com
Modified for M5307 by Dave Miller, dmil...@intellistor.com
Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
Built 1 zonelists in Zone order, mobility grouping off. Total
pages: 4064
Kernel command line:
PID hash table entries: 64 (order: 6, 256 bytes)
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory available: 14172k/16384k RAM, (878k kernel code, 150k data)
Mount-cache hash table entries: 512
net_namespace: 152 bytes
NET: Registered protocol family 16
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 512 bind 1024)
TCP reno registered
ColdFire internal UART serial driver
ttyS0 at MMIO 0x100001c0 (irq = 73) is a ColdFire UART
console [ttyS0] enabled
ttyS1 at MMIO 0x10000200 (irq = 74) is a ColdFire UART
dm9000 Ethernet Driver, V1.30
TCP cubic registered
NET: Registered protocol family 17
Freeing unused kernel memory: 52k freed (0x1e9000 - 0x1f5000)
Kernel panic - not syncing: No init found. Try passing init=
option to kernel.
Any help is really appreciated.
many thanks
Angelo
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
