[Issue 1001775] New: Flash Safe service uses cyg_flash_lock & cyg_flash_unlock despite they may be not available in the configuration.

[bugzilla-daemon@ecoscentric.com]

Please do not reply to this email, use the link below.

https://bugzilla.ecoscentric.com/show_bug.cgi?id=1001775

          Issue ID: 1001775
           Summary: Flash Safe service uses cyg_flash_lock &
                    cyg_flash_unlock despite they may be not available in
                    the configuration.
           Product: eCos
           Version: 1.2.5
            Target: All
  Architecture/Host HostOS: Win XP/7
                OS:
            Status: UNCONFIRMED
          Severity: minor
          Priority: normal
         Component: Flash
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: vkirsan@mera.ru
        QA Contact: ecos-bugs@ecos.sourceware.org
                CC: ecos-bugs@ecos.sourceware.org

I'm not sure if I have chosen the version of eCos and the component rightly.
I'm using eCosPro 3.1.25 and the component I'm reporting a bug on is Flash Safe
service (CYGPKG_FLASHSAFE).

Symptoms:

- Application binary fails to compile with the following messages from ld:

C:\eCosPro\workspace\ipTNA3i_config\ecos_install/lib\libtarget.a(services_flashsafe_flashsafe.o):
In function `cyg_flashsafe_commit':
c:/eCosPro/ecos-3.1.25/packages/services/flashsafe/v3_1_25/src/flashsafe.c:532:
undefined reference to `cyg_flash_lock'
C:\eCosPro\workspace\ipTNA3i_config\ecos_install/lib\libtarget.a(services_flashsafe_flashsafe.o):
In function `cyg_flashsafe_open':
c:/eCosPro/ecos-3.1.25/packages/services/flashsafe/v3_1_25/src/flashsafe.c:366:
undefined reference to `cyg_flash_unlock'
c:/eCosPro/ecos-3.1.25/packages/services/flashsafe/v3_1_25/src/flashsafe.c:366:
undefined reference to `cyg_flash_unlock'
collect2: ld returned 1 exit status

Speculations:

After a short examination of the documentation and the source code I found out
that my flash (am29xxxxx_v2 driver) doesn't support block locking (doesn't
implement CYGHWR_IO_FLASH_BLOCK_LOCKING interface). But Flash Safe, using this
facility of block locking, doesn't check if the implementation of the interface
is present or not.

Maybe there should be the additional dependency on
CYGHWR_IO_FLASH_BLOCK_LOCKING  added in CYGPKG_FLASHSAFE so that the designer
could now from the beginning whether one can use Flash Safe or not with one's
flash memory?

-- 
You are receiving this mail because:
You are the assignee for the issue.