[Bug 1001349] New: Usage of block locking in the flash library

[Bug 1001349] New: Usage of block locking in the flash library

[bugzilla-daemon]

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 on the CC list for the bug.

[Bug 1001349] Usage of block locking in the flash library

[bugzilla-daemon]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001349

Bernd Edlinger <bernd.edlinger@hotmail.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bernd.edlinger@hotmail.de

--- Comment #1 from Bernd Edlinger <bernd.edlinger@hotmail.de> 2012-08-16 09:30:47 BST ---
(In reply to comment #0)
I know these parts too.

The locking / unlocking is a kind of security feature there.

I would suggest that your boot loader unlocks only the sectors on your
flash device, were it is safe for your application to write on it later.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug 1001349] New: Usage of block locking in the flash library

[bugzilla-daemon]

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.