On Tue, 2002-10-15 at 07:28, Andrew Lunn wrote:
On Tue, Oct 15, 2002 at 03:26:22PM +0200, llandre wrote:
Is it possible to have the JFFS2 file system and eCos binary code on the
same physical chip?
The flash driver API functions copy themselves itself into RAM before
doing anything with the flash. Redboot uses this feature.
Firstly, it's not common to actually be executing from FLASH. RedBoot
does this, and an application can do so as well, but the more common
case is for programs to execute out of RAM.
I'm not sure I'd make that generalisation. XIP is an obvious way to reduce
costs in final production boards for applications where performance isn't
critical (assuming it's slower, which it isn't always).are designed to handle this case anyway by insisting that the access
routines are in RAM before running them.
What i don't know about is if this is thread safe. Does the flash code
disable interrupts while its doing dangerous things? You need to check
the code, or probably Gary knows.
This is an interesting observation. Currently nothing specific is being
done about interrupts. It probably should, so I'll think about it.
In fact, it definitely should if e.g. you are running out of Flash! I'll
raise a bugzilla bug for this unless you want to deal with it imminently -
it can at least be conditionalized on CYG_HAL_STARTUP_ROM.