Hi, NXP expert, I have an issue with the S32K312 feed initialization time and would like to consult about it. The details are as follows:
I configured two fee storage clustergroups, one primary and one standby. The standby is a backup of the primary. A total of 19 blocks were configured, and the blocks are stored in both the primary and standby. The software version is Mcal RTD4.0.0 HF02, and Burst mode is enabled.
Chenxu1_0-1785460201957.png
Test method:
Upon power-up, the initialization time is printed (after calling Mem_43_INFLS_Initt(), MemAcc_Initt(), and Fee_Init(), wait for the Fee_GetStatus() interface to return MEMIF_IDLE), and all blocks are written with data once.
The test results are as follows:
Number of power-ups | Initialization time (ms) | illustrate |
1 | 8 | |
2 | 15 | |
3 | twenty three | |
4 | 40 | |
5 | 48 | |
6 | 57 | |
7 | 65 | |
8 | 74 | |
9 | 82 | |
10 | 90 | |
11 | 99 | |
12 | 107 | |
13 | 115 | |
14 | 124 | |
15 | 133 | |
16 | 141 | |
17 | 149 | |
18 | 158 | |
19 | 166 | |
20 | 175 | |
twenty one | 183 | |
twenty two | 192 | |
twenty three | 200 | |
twenty four | 209 | |
25 | 217 | |
26 | 226 | |
27 | 234 | |
28 | 8 | Cluster paging |
Based on the above tests, we found that the time for each increment changes very quickly. Therefore, we would like to inquire whether there is a formula for calculating the initial time and whether it can be optimized.
Hi @Chenxu1
There is no formula provided by the FEE driver documentation to calculate the initialization time. The initialization time depends on the actual state of the FEE storage, such as the amount of stored data, number of records, and whether any cluster recovery or swap is required. The main configuration parameter that can improve initialization performance is FeeDataBufferSize, as a larger buffer allows more data to be processed per Fls_MainFunction cycle. See please Fee user manual for details. For a realistic estimate, the initialization time should be measured on the target configuration after prolonged FEE usage and multiple write cycles.
Regards,
Lukas
Yes, this has been discussed here several times. For example:
https://community.nxp.com/t5/S32K/S32K312-FEE-FLS-INIT-time/m-p/2024041
Regards,
Lukas
Hi,
Currently, writing 16 bytes causes the next initialization to take 2ms longer. At this point, there's no page switching involved—just reinitializing and reading 16 bytes again, which adds 2ms. Is this normal?