Hi Jate
Thanks for your answers.
Indeed, the romfs.img is cat'ed to the linux image and it is copied at
the end of the bss section during startup procedure.
With GDB I have checked the memory and -rom1fs- is at the address of _ebss.
This point is correct.
Concerning the size of romfs, it is the third word of romfs, so _ebss
address+8.
I have just resolved this problem of size, it was just the value of
CONFIG_MTD_UCLINUX_ADDRESS
which was not correct. I set it correcty now and the output is better :-)
*************************************************
...
uclinux[mtd]: RAM probe address=0x800a14f4 size=0x19000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00019000 : "ROMfs"
...
*************************************************
Have you got an idea concerning the endless loop into the deamon
mtd_blktrans_thread?
Because this deamon schedules at each loop but it seems it doesn't find
a suitable task for switch back.
Do you know a reason which can produce this situation?
Perhaps I have missed something during configuration?
I haven't enabled INITRD support.
Could it be helpful at this point?
Thanks in advance.
S.Lambert
Jate Sujjavanich a écrit :
The uclinux driver is reporting a size of 0x18141000 or 403,968,000. I have a
feeling that your romfs is not that large, and the size is off because it's
reading the wrong data. I don't remember exactly, but I think the size may be
the at the start of the romfs image.
The uclinux driver is expecting the romfs image to be at ebss. In my 2.4.x
version, the kernel image has the romfs image appended directly to the end of
the kernel data section, and the startup code (crt0_ram.S?) copies the romfs
image to address ebss and zeros bss.
- Jate S
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Stephane Lambert
Sent: Friday, January 16, 2009 6:20 AM
To: uClinux development list
Subject: Re: [uClinux-dev] Problem with romfs
Hi,
yes CONFIG_ROMFS_FS is enabled.
I've tried to enabled CONFIG_MTD_BLOCK, and several things have been done:
************************************
...
uclinux[mtd]: RAM probe address=0x11414 size=0x18141000 Creating 1 MTD partitions on
"RAM":
0x00000000-0x18141000 : "ROMfs"
mtd: Giving out device 0 to ROMfs
uclinux[mtd]: set ROMfs to be root filesystem mtdblock_open ok
mtdblock: read on "ROMfs" at 0x0, size 0x200
mtdblock: read on "ROMfs" at 0x200, size 0x200
**************************************
At this point the kernel creates a new thread and executes the function
'mtd_blktrans_thread()'.
However, the system enters into an endless loop in this function. It seems not
able to come back to the previous process.
Have someone got an idea concerning this problem?
Thanks in advance.
S.Lambert
Jate Sujjavanich a écrit :
Errno 6 is "No such device or address". Is romfs compiled into the kernel?
- Jate
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected] To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
************************************************************************************
This footnote confirms that this email message has been scanned by PineApp
Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
