This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001349] New: Usage of block locking in the flash library
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Tue, 27 Sep 2011 14:03:10 +0100
- Subject: [Bug 1001349] New: Usage of block locking in the flash library
- Auto-submitted: auto-generated
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001349
Summary: Usage of block locking in the flash library
Product: eCos
Version: unknown
Platform: All
OS/Version: ARM
Status: UNCONFIRMED
Severity: major
Priority: low
Component: Flash
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: brauner@tmg-karlsruhe.de
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
I am using the Intel flash 28F128P33 which requires block unlocking and locking
when erasing and programming.
I have seen that after configuration there are two functions flash_lock and
flash_unlock which are now activated.
The generic flash library does not use these functions. Is there any solution
that the flash library does automatically unlock and lock the blocks which are
to be written or erased ?
Or do I have to change my application to use the new functions.
The problem is that we have a huge software package which is not using these
functions, and our customer has designed a locking device in his hardware.
Would be nice to configure the Flash library to auto-unlock and -lock.
Thanks,
Dirk
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.