public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-1001775-13@http.bugzilla.ecoscentric.com/> (raw) 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.
next reply other threads:[~2013-02-27 13:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-27 13:57 bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2013-02-27 13:57 bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1001775-13@http.bugzilla.ecoscentric.com/ \ --to=bugzilla-daemon@ecoscentric.com \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).