public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001850] New: Flash Driver for Cypress FM25VXX FRAM Date: Thu, 23 May 2013 01:48:00 -0000 [thread overview] Message-ID: <bug-1001850-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001850 Bug ID: 1001850 Summary: Flash Driver for Cypress FM25VXX FRAM Product: eCos Version: unknown Target: freescale_twr_k60n512 (Freescale Kinetis TWR-K60N512) Architecture/Host Cortex-M OS: Status: UNCONFIRMED Severity: enhancement Priority: low Component: Flash Assignee: unassigned@bugs.ecos.sourceware.org Reporter: mjones@linear.com CC: ecos-bugs@ecos.sourceware.org Created attachment 2239 --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2239&action=edit Cypress Flash support for FM25VXX FRAM on Kinetis This is a working driver for Cypress FM25VXX FRAM for Kinetis K60 FXM. Several things to note about its current status: - Supports 256kB, 512KB, 1MB devices (tested with 512KB device) - FRAM has no blocks, so the flash API is implemented as a single block device. - Erase is implemented by writing 0xFF. It is not very time efficient, but it is very memory efficient. If one really wants to erase, it will be much faster to write 0xFF from your own larger buffer. - It has a CDL setting to control the write block size if desired. - It works with SPI polled mode, but does not completely work with SPI DMA mode. A write followed by a read produces read data that has one 0x00 byte at the beginning. This seems to be related to the underlying SPI code. - The test code has been run in other application files and should work, but the erase will be very slow. You can comment the erase and it should run. The code is just a tweaked version of SST25 test code. - Normal READ mode tested. FAST READ mode not tested. - It has been used with an existing application and is reliable in polled mode with normal READ mode. - With the SPI speed set to 25Mhz, the actual frequency is 12.5Mhz. Increasing SPI setting has no effect. Issues that need resolving: - DMA function - SPI frequency - Block erase strategy - More testing -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-05-23 1:48 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-23 1:48 bugzilla-daemon [this message] 2013-06-01 13:45 ` [Bug 1001850] " bugzilla-daemon 2013-06-01 13:54 ` bugzilla-daemon 2013-06-09 2:35 ` bugzilla-daemon 2013-06-09 2:35 ` bugzilla-daemon 2013-06-09 2:37 ` bugzilla-daemon 2013-06-26 16:55 ` bugzilla-daemon 2013-06-26 16:56 ` bugzilla-daemon 2013-05-23 1:48 [Bug 1001850] New: " 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-1001850-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --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).