Hi everyone.
The procedure for enabling your flash drivers is still baffling me.
I have a configuration in configtool which shows that I have FLASH
device drivers and, within that my board specific FLASH memory support.
I can successfully build and I know that my files (MYBOARD_flash.c and
.h)
Hi:
Can anyone pl let me know what kind of high -level ethernet driver support
needs to be provided by a target for eCos application with TCP/IP stack.
Are there any kind of additional interface implementations/code that would
be added to support networking in eCos application, assuming
Hi All,
Can anybody tell me, what is the minmal size
of ecos kernel. I'm trying to port ecos on LPC2124
based board.
If anybody has done the same, pls help.
regards,
Static
__
Yahoo! Mail
Stay connected, organized, and protected. Take
On Tue, Aug 30, 2005 at 03:57:37PM +0100, Matt Sartori wrote:
Hmm. The symbol appears in two object files:
devs_flash_arm_str710fz2_flash.o whose first entry is
l df *ABS* flash.c
and further down that object file's table is
ld
On Tue, Aug 30, 2005 at 04:13:01PM +0100, Matt Sartori wrote:
Thanks again, Andrew, for prodding me in the right direction. This was
indeed the problem; an old dependency mixed with a bit of false
assumption (that clicking the clean button in the configtool would
actually remove any such stale
I have made some minor mods, thanks to Anthony Tonizzo and Andrew Lunn.
1. Now only uses branch island if, and only if the call is over 26bits.
2. Uses absolute address instead of function name.
3. Enabled by CDL option.
I have not yet got around to making it platform independent, I did not
Hi there,
Wondering if anyone knows what is the current status of the following
discussion on Multiple partition on a FLASH device.
Has the FLASH driver been updated to include mutexs to prevent
simultaneous access to the same FLASH device?
Or some other implementations were introduced to
Hi there,
It seems that when mounting a large jffs2 partition (5M) the system
seems to take a long time about 30 seconds. This also happens when we do
a directory listing of the mount point for the first time. Seems to be
due to reading the inodes of the fs.
Is this delay part of the overheads