[Issue 1000693] flash.c assertion failure

[bugzilla-daemon@ecoscentric.com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000693





--- Comment #3 from Bart Veer <bartv@ecoscentric.com>  2009-03-03 14:59:42 ---
Adding a flash driver in user space is not a common requirement, but
the synthetic target can be rather more dynamic than a physical board.
I can think of other scenarios where it might be desirable, for
example a board with the SPI signals on an expansion connector and
hooked up to an external dataflash. Some people may prefer to instantiate
the dataflash device in application space rather than update the platform
HAL and the target definition.

So, adding CYGHWR_IO_FLASH_DEVICE_USERSPACE is probably the sensible
way to go. The flash3.c test would then need a #ifdef on that option.
Unfortunately that means the test won't actually be run very often -
only when the application developer has explicitly enabled that
option.

I am not sure why you think _USERSPACE should implement
CYGHWR_IO_FLASH_DEVICE twice? Are you worried about the case where
there are zero flash devices in the target definition and >=2 flash
devices in user space? If so, having two implements properties would
indeed be the safe solution.

Bart


-- 
Configure issuemail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.