SPRADK4 October   2024 AM263P2-Q1 , AM263P4 , AM263P4-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2OptiFlash Technology
  6. 3OptiFlash Hardware Accelerators
    1. 3.1 RL2_OF Accelerators
      1. 3.1.1 RL2-Flash Cache
      2. 3.1.2 FLC - Fast Local Copy (Image Download Acceleration)
      3. 3.1.3 Region-Based Address Translation (RAT)
    2. 3.2 FSS Accelerators
      1. 3.2.1 On-the-fly-Safety Engine
      2. 3.2.2 On-the-fly-Security Engine
      3. 3.2.3 FOTA HW Engine
  7. 4OptiFlash SW Tooling
    1. 4.1 Smart Placement
    2. 4.2 Smart Layout
    3. 4.3 Optishare
    4. 4.4 Dynamic Overlay
  8. 5Benchmarks and Performance Data
  9. 6Usecases for OptiFlash Accelerators
  10. 7Getting Started With OptiFlash
  11. 8Conclusion

Introduction

Current indicators suggest that traditional MCUs with embedded flash on the same die, as shown in Figure 1-1, will not scale beyond a 22 nm technology node due to high-voltage circuits required for programming and erasing flash. Flash-based processes are also costly due to large number of masks required to integrate embedded flash on MCU/SOC die using deep sub-micron digital CMOS technology. Thus, these MCUs will only work for older process nodes (such as 28nm, 40nm, 65nm…).

There are also alternate new NVM technologies coming up such as MRAM, RRAM, and so forth, but even these are not yet ready for high-reliability applications such as automotive.


 Traditional MCU

Figure 1-1 Traditional MCU

High-performance MCUs, as shown in High Performance MCU, use an external Flash Memory part and typically download the entire image to SRAM during boot time. These MCUs, depending on their processing and power needs based on application they are addressing, work across process nodes (for example, down to newer process nodes such as 3/5nm or custom nodes like 45nm), where flash technology is not available. Also, having a separate flash part is cheaper due to the flash only process node. Most common disadvantage of these MCUs is the cost due to large SRAM size (>= Application SW Image Size) and large boot/startup time.


 High Performance MCU

Figure 1-2 High Performance MCU