Spansion S29NS/WS-R to
Numonyx™ StrataFlash® Cellular
Memory M Family Migration Guide

Application Note 309204




       ...
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH NUMONYX™ PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Contents

1.0    Introduction .....
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Revision History

      Date of
...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




1.0            Introduction
    ...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




2.0                Flash Memory ...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




2.2            Performance Speci...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




3.0                Hardware Desi...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




4.0            Flash Software De...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




4.2                Programming O...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Table 5:       Numonyx M Family ...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Note:              Three read cy...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Table 10: Command Set Comparison...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




         WC = Word Count.
      ...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




4.6            Configuration Reg...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




5.0                Flash File Sy...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Table 14: Numonyx M family Flash...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




7.1.1              Numonyx™ Flas...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Appendix A Additional Informatio...
Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide




Application Note                ...
Upcoming SlideShare
Loading in...5
×

Spansion S29NS/WS-R to Numonyx™ StrataFlash

1,048

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,048
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Spansion S29NS/WS-R to Numonyx™ StrataFlash

  1. 1. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Application Note 309204 309204-01
  2. 2. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH NUMONYX™ PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN NUMONYX'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, NUMONYX ASSUMES NO LIABILITY WHATSOEVER, AND NUMONYX DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF NUMONYX PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Numonyx products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. Numonyx B.V. may make changes to specifications and product descriptions at any time, without notice. Numonyx B.V. may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.” Numonyx reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. Contact your local Numonyx sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Numonyx literature may be obtained by visiting the Numonyx website at http://www.numonyx.com. Numonyx, the Numonyx logo, and StrataFlash are trademarks or registered trademarks of Numonyx B.V. or its subsidiaries in other countries. *Other names and brands may be claimed as the property of others. Copyright © 2009, Numonyx B.V., All Rights Reserved. Application Note February 2009 2 309204-01
  3. 3. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Contents 1.0 Introduction .............................................................................................................. 5 2.0 Flash Memory Device Comparison.............................................................................. 6 2.1 Features ............................................................................................................ 6 2.2 Performance Specifications ................................................................................... 7 3.0 Hardware Design Considerations ............................................................................... 8 3.1 AC Read Specifications ......................................................................................... 8 3.2 AC Write Specifications ........................................................................................ 8 3.3 Power and Voltage Regulation ............................................................................... 8 3.4 Device Packaging and Ballout................................................................................ 8 4.0 Flash Software Design Considerations ....................................................................... 9 4.1 Memory Partitioning ............................................................................................ 9 4.2 Programming Operations.................................................................................... 10 4.2.1 Programming Regions ............................................................................. 10 4.2.2 Programming Mode vs. Programming Method............................................. 10 4.2.3 Programming Region State Table.............................................................. 11 4.3 Device Identification .......................................................................................... 11 4.4 Device Command Codes ..................................................................................... 12 4.5 Status Register ................................................................................................. 14 4.6 Configuration Registers ...................................................................................... 15 5.0 Flash File System Considerations............................................................................. 16 6.0 Design Tools ............................................................................................................ 17 7.0 Miscellaneous Enablement Options .......................................................................... 17 7.1 Numonyx Software ............................................................................................ 17 7.1.1 Numonyx™ Flash Data Integrator (Numonyx™ FDI) .................................... 18 7.2 Third Party File Systems..................................................................................... 18 7.3 Chipset Vendor Software .................................................................................... 18 7.4 Linux Support ................................................................................................... 18 7.5 Consulting ........................................................................................................ 18 A Additional Information ............................................................................................ 19 February 2009 Application Note 309204-01 3
  4. 4. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Revision History Date of Revision Description Revision February 2009 01 Initial Release Application Note February 2009 4 309204-01
  5. 5. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 1.0 Introduction This application note provides guidance to migrating from a system designed with a Spansion S29NS/WS-R flash memory device to Numonyx™ StrataFlash® Cellular Memory M family device, while retaining the Spansion layout. Note: Unless otherwise indicated, throughout the rest of this document, the Numonyx™ StrataFlash® Cellular Memory M family device is referred to as the Numonyx M family device. The Spansion S29NS/WS-R flash memory device is referred to as the Spansion S29 device. This application note provides the following information about migrating from a Spansion S29 device to a Numonyx M family device: • Critical flash memory device differences between the Numonyx M family device and the Spansion S29 device • Hardware design considerations • Flash software design and software conversion considerations Before you use this document, become familiar with the Numonyx M family and Spansion S29 devices, as described in the datasheets for each device. Note: This application note is based on information available at the time of publication for the Numonyx™ StrataFlash® Cellular Memory M family device and the Spansion S29NS/ WS-R flash memory device. This application note might not reflect changes in specifications to either device. Refer to the appropriate documents from the respective manufacturer for the most current information about each device, before finalizing any design. February 2009 Application Note Order Number: 309204-01 5
  6. 6. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 2.0 Flash Memory Device Comparison This section describes key differences between the Numonyx M family device and the Spansion S29 device. 2.1 Features Table 1 Feature Comparison of Flash Memory Devices below compares the feature sets for the Numonyx M family device and the Spansion S29 device. Table 1: Feature Comparison of Flash Memory Devices Specific Command/ Numonyx M Spansion S29 Mode/Feature Set Feature Family Device Device Boot/Parameter Sectors/ Blocks X Sectors/Blocks Main Sectors/Blocks Control Mode X Programming Mode Object Mode X Word Program Program Buffered Program Block Erase Erase Chip Erase X Suspend Program/Erase Suspend Read While Write Simultaneous Read/Write Read While Erase 8-Word Synchronous Burst 16-Word Continuous Lock Sector/Block Unlock Sector/Block Sector/Block Locking/Unlocking Lock-down Sector/Block X Lock Range Sector/Block X Non-Mux Interface AD-Mux AAD-Mux 56-ball Ballout Package 84-ball Ballout Application Note February 2009 6 Order Number: 309204-01
  7. 7. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 2.2 Performance Specifications Table 2 Performance Comparison of Flash Memory Devices below compares the critical performance specifications of the Numonyx M family device and the Spansion S29 device. Table 2: Performance Comparison of Flash Memory Devices Performance Performance Numonyx M Family Spansion S29 Device Parameter Specification Device 133MHz (non-mux/AD-mux) 104MHz (non-mux/AD- Max CLK Frequency 104MHz (AAD-mux) mux/AAD-mux) Max Synch Latency/ Initial Synch Access 96ns 75ns Time Read Access Times Max Synch Burst Access/CLK to output 5.5ns 7.6ns valid Max Asynch Access Time/Initial Asynch 96ns 80ns Access Time Max OE# Access Time/ 7ns 15ns OE# low to output valid 33mA @ 133MHz Continuous Burst Read 32mA @ 104MHz 30mA @ 108MHz Program/Erase 35mA 20mA Current Consumption (typical values) Standby Mode 20uA 20uA Deep Power Down Mode 2uA N/A Single Word Programming 115us 130us Typical Program and Effective Write Buffer Erase Times 2us 4.8us Programming per Word Sector Erase 900ms (256KB sector size) 600ms (128KB sector size) February 2009 Application Note Order Number: 309204-01 7
  8. 8. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 3.0 Hardware Design Considerations The Numonyx M family and Spansion S29 devices provide low voltage, high performance operation for wireless applications, satisfying the need for increasing data-transfer speeds, reduction in overall system power consumption, and cost. Both flash devices feature multi-partition architecture, hardware read-while-write functionality, and 1.8 V operation. Although both flash devices have similar hardware interfaces, software changes are necessary to accommodate Numonyx M family block sizes, partitioning differences, and programming-region configurations based on data types (e.g., Control Mode, Object Mode). The following sections discuss hardware design considerations when migrating from the Spansion S29 device to the Numonyx M family device. 3.1 AC Read Specifications The critical performance specifications have been identified in the previous section. For other read specifications, please refer to the Numonyx™ StrataFlash® Cellular Memory (Numonyx M family) datasheet (order number 309823) for the latest read timing specifications. 3.2 AC Write Specifications The critical performance specifications have been identified in the previous section. For other write specifications, please refer to the Numonyx™ StrataFlash® Cellular Memory (Numonyx M family) datasheet (order number 309823) for the latest read timing specifications. 3.3 Power and Voltage Regulation The critical performance specifications have been identified in the previous section. For other power and voltage specifications, please refer to the Numonyx™ StrataFlash® Cellular Memory (Numonyx M family) datasheet (order number 309823) for the latest read timing specifications. 3.4 Device Packaging and Ballout The Numonyx M family device is available in 56-ball and 84-ball packages, which are compatible to the Spansion S29 device 56-ball and 84-ball packages. For specific ballout and package information, please contact your Numonyx field representative. Application Note February 2009 8 Order Number: 309204-01
  9. 9. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 4.0 Flash Software Design Considerations The following sections discuss software design considerations when migrating from the Spansion S29 device to the Numonyx M family device. Note: See Section 5.0, “Flash File System Considerations” for information on how these differences may affect your flash file system/manager. 4.1 Memory Partitioning Table 3 Memory Partitioning Comparison of Flash Memory Devices below compares the array architecture of the Numonyx M family device and the Spansion S29 device. Table 3: Memory Partitioning Comparison of Flash Memory Devices Numonyx M Family Spansion S29 Array Attribute Array Density Device Device 128Mb 256Mb Number of Banks/Partitions 8 16 512Mb 1024Mb 128Mb 16Mb 8Mb 256Mb 32Mb 16Mb Bank/Partition Size 512Mb 64Mb 32Mb 1024Mb 128Mb 64Mb 128Mb 8 256Mb 16 Number of Sectors/Blocks per Partition 512Mb 32 1024Mb 64 128Mb 256Mb Sector/Block Size 256KB 128KB 512Mb 1024Mb Numonyx M family flash cells within a block are organized by regions, and segments. A block contains 256 programming regions of 1024 bytes each. Each programming region has 32 segments of 32 bytes. The 32 segments within the programming region are divided into two halves, “A” and “B”. The A half is accessed when address bit A3 = 0, and the B half is accessed when address bit A3 = 1. Note: See Section 5.0, “Flash File System Considerations” for information on how these differences may affect your flash file system/manager. February 2009 Application Note Order Number: 309204-01 9
  10. 10. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 4.2 Programming Operations Unlike the Spansion S29 device, there are some restrictions required for programming of the Numonyx M family device flash array. For example, single word programming can only be used for certain programming modes, such as Control Mode, and buffer programming can only be issued once to a programming region that is configured in Object Mode. Table 4 and Table 5 in Section 4.2.2 show the restrictions for Numonyx M family programming operations. System designers should organize the flash array according to specific requirements of the system with consideration given to two types of information: • Flash File System (FFS) or Headers: refers to smaller, frequently changing code/ data; and • Object: refers to larger, infrequently changing code/data The following sections describe the Numonyx M family device programming region, and programming modes versus programming methods. Note: See Section 5.0, “Flash File System Considerations” for information on how these differences may affect your flash file system/manager. 4.2.1 Programming Regions Unlike the Spansion S29 device, the Numonyx M family device flash cells within a block are organized into regions and segments. A block contains 256 regions of 1024 bytes, and are referred to as programming regions. Each programming region has 32 segments consisting of 32 bytes. The 32 segments within a programming region are further divided into two halves: ‘A’ and ‘B’. The A half has A3 = 0 addresses, and the B half has A3 = 1 addresses. 4.2.2 Programming Mode vs. Programming Method With the exception of the new programming commands used with the Numonyx M family device, programming methods, such as single word programming and buffered programming, are identical for the Spansion S29 and Numonyx M family devices. However, there are some required restrictions for the Numonyx M family device programming modes. The Numonyx M family device features two programming modes: • Control Mode • Object Mode By implementing the appropriate programming mode, system designers can effectively organize how information is stored in the flash memory array. Each programming region can be configured for either of two programming modes: Control Mode or Object Mode. Control and Object programming regions can be intermingled within the same erase block. However, the programming mode for any region within a block can be changed only after erasing the entire block. Table 4 and Table 5 show the restrictions for the Numonyx M family device programming modes. Table 4: Numonyx M Family Program Mode Restriction Program Mode Region Spansion S29 Numonyx M family Control Mode Region NA Multi-write region between erase cycles Object Mode Region NA Single-write region that can be written to only once between erase cycles Application Note February 2009 10 Order Number: 309204-01
  11. 11. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Table 5: Numonyx M Family Programming Command Restrictions Program Command Command Code Numonyx M family Single Word Program 41h Program data in Control Mode Region Only Buffered Program E9h Program data in Control or Object Mode Region Buffered EFP 80h Program data in Control or Object Mode Region 4.2.3 Programming Region State Table Table 6 shows the programming region state and output state transitions based on incoming commands. Only one region/partition can be actively programming at a time. Table 6: Programming Region Next State Table Command Issued Current State of Programming region 41h to B-half 41h to A-half E9h to B-half E9h to A-half (A3 = 1) (A3 = 0) (A3 = 1) (A3 = 0) Program Successful Program Successful Program Successful Erased Region configured to Region configured to Region configured to Control Mode Object Mode Control Mode Program Fail; Illegal Program Fail; Control Mode Command Program Successful Program Successful Object data to Control mode region Object Mode Program Fail; Rewrite to Object mode region 4.3 Device Identification Each flash memory device has a manufacturer ID. To retrieve the manufacturer ID, read address 00h after issuing a Read Device Identifier command on Numonyx flash memory devices, or after an Autoselect command on Spansion flash memory devices. Table 7 Manufacturing ID Codes below shows the manufacturer ID codes for Numonyx and Spansion flash memory devices. Table 7: Manufacturing ID Codes Manufacturer Identifier Numonyx 0089h Spansion 0001h Each flash memory device is uniquely defined using a device ID. Similar to retrieving the manufacturer ID codes, the device ID is also read at address 01h after issuing the Read Device Identifier or the Autoselect command. Table 8 Numonyx M Family Device ID Codes and Table 9 Spansion S29 Device ID Codes list the device ID codes for the Numonyx M family and the Spansion S29 devices. February 2009 Application Note Order Number: 309204-01 11
  12. 12. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Note: Three read cycles (or device ID codes) are required to successfully identify a Spansion S29 flash memory device; the three device ID codes are read at addresses 01h, 0Eh, and 0Fh. Table 8: Numonyx M Family Device ID Codes Device Density Interface Device Identifier Non-Mux 8900h 128 Mbit AD-Mux/AAD-Mux 8903h Non-Mux 8901h 256 Mbit AD-Mux/AAD-Mux 8904h Non-Mux 887Eh 512 Mbit AD-Mux/AAD-Mux 8881h Non-Mux 88B0h 1024 Mbit AD-Mux/AAD-Mux 88B1h Table 9: Spansion S29 Device ID Codes Device Identifier Device Type Device Density Cycle 1 Cycle 2 Cycle 3 128 Mbit 0027h 256 Mbit 0026h S29WS 007Eh 0003h 512 Mbit 0025h 1024 Mbit 0024h 128 Mbit 3A7Eh 3A35h 3A03h 256 Mbit 397Eh 3917h 3903h S29NS 512 Mbit 387Eh 3816h 3803h 1024 Mbit 377Eh 3715h 3703h 4.4 Device Command Codes The command codes between the Numonyx and Spansion flash memory devices also differ. Table 10 Command Set Comparison below lists the command codes for the common flash memory functions on both devices. Application Note February 2009 12 Order Number: 309204-01
  13. 13. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Table 10: Command Set Comparison Bus Cycles Command Device First Second Third Fourth Fifth Sequence Addr Data Addr Data Addr Data Addr Data Addr Data Numonyx XX FF Read Array Spansion RA RD Numonyx XX 90 IA ID Read ID Spansion X55 90 Numonyx WA 41 WA WD Program Spansion N/A Numonyx (3) CBA E9 BA WC-1 WA WD AWB D0 Buffered Program 555 2AA 555 Spansion (4) 25 WC PA PD PA PD 29 AAA 554 AAA Numonyx BA 20 BA D0 Block Erase 555 2AA Spansion 80 30 AAA 554 Numonyx N/A Chip Erase 555 2AA Spansion 80 10 AAA 554 Numonyx BA 60 BA 01 Lock Block 555 2AA Spansion 60 60 SLA 60 AAA 554 Numonyx BA 60 BA D0 Unlock Block 555 2AA Spansion 60 60 SLA 60 AAA 554 Lockdown Numonyx BA 60 BA 2F Block Spansion N/A Erase Numonyx XX B0 Suspend Spansion XXX B0 Program Numonyx XX B0 Suspend Spansion XXX 51 Erase Numonyx XX D0 Resume Spansion 000 30 Program Numonyx XX D0 Resume Spansion 000 50 Notes: 1. All numbers shown are in hexadecimal representation. 2. XX = Any valid address within the flash memory device. IA = Identification code Address offset. ID = Identifier Data. RA = Read Address. RD - Read Data. WA = Word Address. WD = Word Data. February 2009 Application Note Order Number: 309204-01 13
  14. 14. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide WC = Word Count. BA = Block Address. CBA = Colony Base Address. AWB = Address Within Block. 3. After loading the word count into the write buffer, up to 32 words of data can follow. Then the buffer data is followed by the confirm command (D0 at WA). 4. After loading the word count into the write buffer, up to 16 words of data can follow. Then the buffer data is followed by the confirm command (29 at BA). 5. Use the Unlock Bypass command before the Unlock Bypass Program command. 6. Use the Unlock Bypass Reset command to return to read mode when the flash memory device is in Unlock Bypass mode. 4.5 Status Register The Numonyx M family device has a 16-bit register while the Spansion S29 device has an 8-bit register that indicates device and program/erase status. SR7-4 and SR2-0 bits are equivalent for both devices. However, the Numonyx M family device provides additional information in SR3 bit with regards to the program/erase status due to a potential voltage level error. Because the Numonyx M family device has programming regions used with object/ control mode programming that the Spansion S29 device does not have, there are additional SR bits (SR9-8) that provide status information regarding these modes. Table 11 Status Register Bits Comparison below compares the status register bits for both devices. Table 11: Status Register Bits Comparison SR Bit 15-10 9-8 7 6 5 4 3 2 1 0 Sector/ Spansion Device Erase Program Bank/ Erase Program Block S29 N/A N/A Ready Suspend RFU Suspend Partition Status Status Lock SR Status Status Status Status Status Program/ Sector/ Bank/ Numonyx Region Device Erase Program Erase Program Erase Block Partition M Family Reserved Program Ready Suspend Suspend Status Status Voltage Lock Status SR Status Status Status Status Error Status Application Note February 2009 14 Order Number: 309204-01
  15. 15. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 4.6 Configuration Registers The Numonyx M family device has two 16-bit configuration registers while the Spansion S29 device has one 16-bit configuration register. The Numonyx M family device has a Read Configuration Register (RCR) and an Enhanced Configuration Register (ECR). These configuration registers are used to select bus-read modes and to configure synchronous burst read characteristics of the flash device. The Numonyx M family ECR is also used to configure the Deep Power Down (DPD) mode. CR/RCR15-8 and CR/RCR 6-0 bits are equivalent for both devices. However, the Spansion S29 uses CR7 to configure the output drive strength of the device. The Numonyx M family device also has a way to configure output drive strength, but it uses ECR2-0 to do so. Because the Numonyx M family device has a DPD mode that the Spansion S29 device does not have, there are additional ECR bits (ECR15-14) that provide status information regarding this mode. Table 12 Configuration Register Bits Comparison below compares the configuration register bits for both devices. Table 13 Numonyx M Family Enhanced Configuration Register Bits below shows the additional configuration register bits for the Numonyx M family device. Table 12: Configuration Register Bits Comparison SR Bit 15 14-11 10 9 8 7 6-3 2-0 Read Synch/ Spansion Wait RDY/ RDY/ Output Asynch Reserved Burst S29 States/ WAIT Reserved WAIT Drive Read Length CR Latency Polarity Timing Strength Mode Count Read Synch/ Numonyx Wait RDY/ RDY/ Asynch Burst M Family States/ WAIT Reserved WAIT Reserved Reserved Read Length RCR Latency Polarity Timing Mode Count Table 13: Numonyx M Family Enhanced Configuration Register Bits SR Bit 15 14 13-3 2-0 Numonyx M Output Driver Family DPD Mode DPD Polarity Reserved Control ECR February 2009 Application Note Order Number: 309204-01 15
  16. 16. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 5.0 Flash File System Considerations Table 14, “Numonyx M family Flash File System Considerations” provides a list of flash file system/manager concerns when converting to the Numonyx M family device. It is intended as a guide to allow you to examine your particular flash software that you wish to convert to support newer technology parts. It should help you to find operations in your flash software that might need changes. This is NOT a comprehensive list, but is intended to give you a reasonably detailed idea of what to look for in your code. It may also help you find other areas that need to be addressed, but that are not specifically listed here. Table 14: Numonyx M family Flash File System Considerations (Sheet 1 of 2) Flash File Numonyx M family Manager Analysis Consideration Characteristic Bit Twiddling is a flash technique where bits in flash are erased (during the erase block) to 1’s and reprogrammed to 0’s over time via multiple writes. The flash Control Mode vs. characteristic is that only Control Mode regions can bit twiddle. Object mode regions Bit Twiddling Object Mode can only be programmed once (when established in Object Mode) and only all at once. Erasing (the erase block) will put regions back into a state where it can be programmed to either region mode. The low level will need to be modified to recognize and handle Numonyx M family. If New ID, CFI good programming techniques are used, and the flash “low-level” routines are in one Flash Low Level changes, and new or place, this should be reasonably straight forward. If flash commands are scattered changed commands throughout the code, then adding support is more complicated. Best to use CFI where possible. File Header/ File Headers define and control the content of files and or directory entries. They Directory Control Mode typically will need to be in Control Mode if they have data that might be changed. For Handling best efficiency, headers should be grouped within common control mode regions. Block headers control the flash management aspects of a flash erase block. These will Block Headers Control Mode typically have data that needs to be updated or twiddled for pointers and state changes. That means they need to be in control mode. Object Mode is write Cannot change an Object Mode region once it is written. Object mode region must be once, and Object written all at once (e.g. 1KB for Numonyx M family). Other techniques are required to File Edits mode is 1K write at handle updates, insertions, or deletions within a file such that they do not disturb an one time existing region. Cannot just start writing again into an object mode region. To append new data must use another technique such as start allocating a new region beyond the original end File Append Same as File edits of data, or allocate new region, write in existing and new data and invalidate old region Cannot write one or a few bytes at a time or each write will use up a full region for Object Mode is each. Must use another technique to handle the small data, such as buffering, or a Stream data written all at once technique where existing data is moved to a new Object Mode region along with the new data and the old region is invalidated. Partial writes Same as stream data Similar concerns/constraints as “Stream Data” above. PLR state bits will need to be in a control mode region to allow twiddling of the states. If a PLR occurs during the initial write of a region, it is best to invalidate that region. Control Mode and Power Loss New data in the process of being written is lost especially within the specific region Object mode Recovery where the write was occurring at time of power loss. If data was being transferred considerations (like during garbage collection / reclaim), it is likely NOT possible to resume the transfer especially if the write was in progress. Numonyx M family erase block size is larger than previous generations of flash. General Erase Bock Size Example: Spansion S29 is 128KB main blocks and Numonyx M family is 256KB. Other Numonyx flash has 64KB erase blocks Numonyx M family buffer write size is larger. The low-level needs to handle this and General Buffer size other buffer sizes. Application Note February 2009 16 Order Number: 309204-01
  17. 17. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Table 14: Numonyx M family Flash File System Considerations (Sheet 2 of 2) Flash File Numonyx M family Manager Analysis Consideration Characteristic Control mode puts constraints on how much flash is available for use and where the Control Mode data can be accessed. For Numonyx M family, Control Mode means there are 16 bytes General operation of accessible (read/write) data then 16 bytes of FF (cannot write any data there), and so on to the 1KB boundary of the region. Numonyx M family no longer have “parameter blocks” that are available on Spansion Parameter data Parameter Blocks S29 or other “boot block” style parts. As such, routines to access these will need to be changed or removed. Deep Power Down capability of Numonyx M family allows for a much lower power operation. It is not completely a transparent mode and the flash manager may need Power changes to cooperate with power management routines when DPD is use. The issue is DPD Management that all erase/programs canceled if DPD occurs. The file system will either need to treat a DPD event as if power-loss has occurred. There is no resuming anything from a DPD event. Numonyx M family blocking is different from Spansion S29. The main blocks are symmetrically blocked (same size) and are larger. Flash management software needs General Blocking Architecture to adapt to these changes. CFI is a good run-time way to adapt to these sorts of changes from component to component. Garbage Garbage collection is where good data is moved out of an erase block to another area collection Blocking, Regions of flash so invalidated, or replaced, or deleted data in that erase block can be erased. (reclaim) There are changes possible for handling regions and the larger blocks. Initialization of the flash software needs careful attention to be sure not to violate the new Numonyx M family usage model. Simple things like attempting to resume a write Initialization All that was interrupted, or bit twiddling fix-ups within an object mode region are not allowed. 6.0 Design Tools Design tools for the Numonyx M family devices include VHDL and Verilog bus functional models, as well as IBIS files. These tools are available on Numonyx’s website, or they may be obtained by contacting an Numonyx field representative. 7.0 Miscellaneous Enablement Options Note: The information contained in this section are the options currently available during time of publication. Numonyx is constantly working to improve and update enablement options for customers. Please contact your Numonyx field representative for information on the latest options available. 7.1 Numonyx Software • FDI – FDI is a full featured high performance file system provided by Numonyx. FDI has been ported to every major chipset vendor and is suitable for RTOS. • Drivers – Numonyx provides Numonyx M family drivers as reference code for customers to implement Numonyx M family support in their own file system. • Simulator – Numonyx has C-based Numonyx M family simulator that allows a user to simulate a flash device in RAM. February 2009 Application Note Order Number: 309204-01 17
  18. 18. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide 7.1.1 Numonyx™ Flash Data Integrator (Numonyx™ FDI) Numonyx™ Flash Data Integrator (Numonyx™ FDI) is a Numonyx supported code, data, and file manager for use in real-time embedded applications. FDI also includes a high-performance interface for streaming data in voice recording and multimedia applications, as well as packet-size data. The Numonyx FDI Code Manager component allows for direct execution of code, including Java* applets and native CPU software. The Numonyx FDI File Manager component presents a user-friendly POSIX-style interface for software developers, streamlining the development of data-centric applications. Numonyx FDI is founded upon robust power-loss recovery mechanisms, which ensure that data remains uncorrupted even through fluctuations and failure of power to the system. In addition, the Numonyx FDI intelligent wear-leveling techniques increase cycling endurance of flash memory blocks. The Numonyx FDI read-while-write (RWW) capabilities are optimized to allow data writes while simultaneously reading code from the same flash memory component. Numonyx FDI acts as a real-time interrupt handler, enabling software-based RWW. In software-based RWW, Numonyx FDI queues data to be written, while code runs directly out of flash memory; when code is not being read, Numonyx FDI performs flash write operations in the background to transfer queue contents to flash memory. When hardware-based RWW is available, Numonyx FDI takes full advantage of the hardware features to reduce interrupt latency. 7.2 Third Party File Systems • Datalight* – Numonyx M family is enabled in Datalight’s Reliance* flash file system. • Blunk* – Numonyx M family is enabled in Blunk’s TargetFFS*. Note: *Other names and brands may be claimed as the property of others. 7.3 Chipset Vendor Software • Numonyx M family is enabled in Qualcomm’s* EFSII* file system. Numonyx provides a patch for EFSII* to optimize Numonyx M family operations in EFSII*. • FDI has been validated and ported to several different Qualcomm chipsets. Note: *Other names and brands may be claimed as the property of others. 7.4 Linux Support Numonyx M family is enabled in open source Linux kernels and has been validated with the JFFS2 file system. 7.5 Consulting Numonyx has software experts that can assist customers in enabling Numonyx M family in their software. Application Note February 2009 18 Order Number: 309204-01
  19. 19. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Appendix A Additional Information Order/Document Document/Tool Number 304435 Numonyx™ Flash Data Integrator (Numonyx™ FDI) User’s Guide Version 7.7 309823 Numonyx™ StrataFlash ® Cellular Memory (Numonyx M family) Datasheet Note: Contact your local Numonyx or distribution sales office or visit the Numonyx World Wide Web home page at http:// www.Numonyx.com for technical documentation, tools, and additional information. February 2009 Application Note Order Number: 309204-01 19
  20. 20. Spansion S29NS/WS-R to Numonyx™ StrataFlash® Cellular Memory M Family Migration Guide Application Note February 2009 20 Order Number: 309204-01

×