Solved! Go to Solution.
mig,
The typical uses for Non-Volatile RAM in embedded systems are for Software to use for things such as:
- Storage of software and/or system configuration parameters needed to keep between system reboots, power cycles, etc.
- Use as a file system
- Use as a boot code area to execute initial code from
- Use to store software (somtimes compressed) code and data for download from slower NVRAM to faster RAM on system bootup.
The advantage of NVRAM, Flash, for code storage etc. memories over ROM is that you can do field upgrades, patches, etc. For rugged systems, storing code in Flash is more reliable than using a disk drive.
As far as what kind of RAM (SDRAM, Static, etc.) to use for your system. If cost is not an object and the performance of the software performance of the reference design meets your need, then it is usually the best place to start as you are not paving new ground for hardware design, you know the chip will work in that HW configuration (chips do have bugs also), and you usually make it easier for the software engineers (such as myself) to run as much of the same software as possible on the reference design and the new design such that debugging your system will go a lot more smoothly.
Hope this helps.
- abartky
mig,
The typical uses for Non-Volatile RAM in embedded systems are for Software to use for things such as:
- Storage of software and/or system configuration parameters needed to keep between system reboots, power cycles, etc.
- Use as a file system
- Use as a boot code area to execute initial code from
- Use to store software (somtimes compressed) code and data for download from slower NVRAM to faster RAM on system bootup.
The advantage of NVRAM, Flash, for code storage etc. memories over ROM is that you can do field upgrades, patches, etc. For rugged systems, storing code in Flash is more reliable than using a disk drive.
As far as what kind of RAM (SDRAM, Static, etc.) to use for your system. If cost is not an object and the performance of the software performance of the reference design meets your need, then it is usually the best place to start as you are not paving new ground for hardware design, you know the chip will work in that HW configuration (chips do have bugs also), and you usually make it easier for the software engineers (such as myself) to run as much of the same software as possible on the reference design and the new design such that debugging your system will go a lot more smoothly.
Hope this helps.
- abartky