Shulou(Shulou.com)06/01 Report--

This article will explain in detail how FRAM is used as a single-chip solution for code memory applications. The content of the article is of high quality, so the editor will share it for you as a reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Applications using memory technology are usually divided into executable code and data tasks. Executable code requires the use of non-volatile memory and the ability to retain the code in memory under all conditions. Data tasks require fast, simple and unlimited read / write access to memory. The memory that performs data tasks is volatile or non-volatile, depending on the application. Usually, the memory of executable code uses ROM-based technology, while the memory of data tasks uses RAM-based technology. As a non-volatile RAM product in Cypress, FRAM provides unique advantages-it can combine executable code and data in a single memory. This article introduces the memory requirements of code storage.

Memory requirements for code storage

◆ non-volatile

Corresponding capacity of ◆

◆ read access time

◆ 's ability to prevent accidental writes

Field programmability of ◆ in a part or piece of code

The ability to perform read access while programming with ◆

The basic requirement of code storage is that it should be a non-volatile memory and be able to maintain its state under all conditions. The code memory is read-only and the contents stored in the memory are not updated during operation. The memory space required to keep the code is set by the application. Usually 20% of the additional memory space, 30% of it, is available for future system modifications. The code execution time is determined by the read access time of the memory; the shorter the access time, the less impact on the controller overhead.

The code memory is read-only. Any unexpected write operation should be prevented because it can cause application failure. However, in several cases, the code memory will be overwritten. It is one case to periodically update the design to add new features or correct hardware errors. On-site reprogramming code memory capability is a major advantage and function. In general, reprogramming affects only a part or piece of code, not the entire code. During reprogramming, the write access time is a factor in determining the time required to reprogram the device.

The code memory contains code that implements the erase / programming function, which is responsible for achieving pre-planned field programmability. During field programming, ensure that read / write access can be performed on bytes of memory or some parts of registers at the same time to avoid unnecessary hassle caused by copying erasure / programming code to other memory (RAM) and executing code from these storage spaces.

Nand Flash is a common solution for code memory, but in some applications (its code size is small and applications require symmetrical read / write access times (operations such as data logging, energy collection, or long-life batteries, etc.), FRAM should be chosen.

About how FRAM as a single-chip solution for code memory applications is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.