From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10739 invoked by alias); 27 Feb 2013 13:57:50 -0000 Received: (qmail 10700 invoked by uid 22791); 27 Feb 2013 13:57:46 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 27 Feb 2013 13:57:36 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 462314680015 for ; Wed, 27 Feb 2013 13:57:35 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGGruFsN176D; Wed, 27 Feb 2013 13:57:33 +0000 (GMT) From: bugzilla-daemon@ecoscentric.com To: ecos-bugs@ecos.sourceware.org Subject: [Issue 1001775] New: Flash Safe service uses cyg_flash_lock & cyg_flash_unlock despite they may be not available in the configuration. Date: Wed, 27 Feb 2013 13:57:00 -0000 X-Bugzilla-Reason: QAcontact CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Flash X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: vkirsan@mera.ru X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: normal X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter qa_contact cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugzilla.ecoscentric.com/ Auto-Submitted: auto-generated MIME-Version: 1.0 Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-bugs-owner@sourceware.org X-SW-Source: 2013/txt/msg00101.txt.bz2 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 QA Contact for the issue. You are on the CC list for the issue.