This article is originally from Embedded MCU, welcome to follow
The S32K3 series is a functional safety automotive MCU launched by NXP based on the Cortex-M7 core and 40nm process, supporting up to ASIL-D.
When evaluating the resources of the S32K314, it was found that the actual available RAM size is less than the 512KB stated in the specification, only 416KB. So, where did the disappearing 96KB go?
Table 1 shows the resources of the S32K3 series. It can be seen that the RAM size of S32K3X4 is 512KB, including K314/K324/K344.
According to the S32K3 series data sheet “S32K3xx_DS_Rev7”, the RAM size of the S32K314 is 512K (including 96KB TCM), but according to the S32K series reference manual, the RAM size calculated in S32K3xx_memory_map.xlsx is less than 512K, only 416K, as shown below.
The Explanation for the Disappearance:
The S32K314 and S32K324/S32K344 are the same design, with the same DIE. During the production phase, the internal CM7_1 core is placed in a wait mode through sBAF configuration.
After configuration, although the S32K314 physically has two cores (cortex_M7_0 and cortex_F7_1), the user can only use one core (cortex_F7_0); ITCM_0/DTCM_0 is available, while ITCM_1/DTCM_1 is not available.
The S32K314 RAM does not find ITCM_1/DTCM_1. Users of the S32K314 can access the ITCM/DTCM of the CM7_1 core through the Backdoor method.
512K = 32K ITCM0 + 32K ITCM1_Backdoor + 64K DTCM0 + 64K DTCM1_Backdoor + 320K SRAM.
Extend your kind thumb in the lower right corner, give a like👍, give a little encouragement to the author!
Since each article may involve content references, some content sources are unknown. If any infringement is found, please inform us in the background, thank you;