This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Issue 1000965] New: Cannot enable access to off-chip flash onat91sam7se32
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Wed, 2 Jun 2010 16:33:31 +0100
- Subject: [Issue 1000965] New: Cannot enable access to off-chip flash onat91sam7se32
- Auto-submitted: auto-generated
Please do not reply to this email. Use the web interface provided at:
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000965
Summary: Cannot enable access to off-chip flash on at91sam7se32
Product: eCos
Version: 2.0
Platform: at91sam7sek_256 (AT91SAM7S-EK board with AT91SAM7S256)
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: normal
Component: Flash
AssignedTo: gary@mlbassoc.com
ReportedBy: stuart.ball@honeywell.com
QAContact: ecos-bugs@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=911)
--> (https://bugzilla.ecoscentric.com/attachment.cgi?id=911)
Exported ecc file
We are currently developing using eCos V2 on the Atmel at91sam7se32.
The base configuration used was V2.0 for the at91sam7s256, using the Posix
template as a starting point. We have tried to add in JFFS2 support on off-chip
flash, but are having difficulty accessing the off-chip flash fitted to our
board, in that eCos seems locked to on-chip flash only.
To try and enable this we have merged in files from eCos V3, in the appropriate
dev, fs, io, hal. I have attached the exporeted ecc file that we are using. It
does not populate the DEVTAB with the flash2 or jffs2-2, even though the
options are selected and no conflicts are highlighted.
It looks as though the value for CYGHWR_IO_FLASH_DEVICE is, currently, not set
properly, which is why it fails. How can this be changed and what new flash
files do we need to create/modify to interface to our off-chip flash memory and
where should they be placed?
--
Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.