S32KのトピックRe: s32k312 FEE

s32k312 FEE

fengba_360 — Fri, 27 Sep 2024 01:20:15 GMT

Dear NXP engineer, I submitted a question about FEE this Monday, which needs your answer. Due to the urgency of the project, I have to submit it again. Thank you for your reply, and I'm sorry for any inconvenience caused to your work!

I'm encountering an issue with the FEE initialization process on the s32k312. My program seems to be stuck at the Fee_MainFunction(), preventing me from proceeding with further operations. I've attached my project code. Could you kindly review it for me?

Re: s32k312 FEE

lukaszadrapa — Tue, 01 Oct 2024 11:36:54 GMT

I imported your project to S32DS and I can see following error message in the configurator:

***
Issue: The total size of blocks is too big. They do not fit into the cluster group FeeClusterGroup_0. Increase the size of the cluster or reduce the size of blocks.
Level: Error
Type: Tool problem
Tool: Peripherals
Origin: Peripherals
Resource: Sources
Information: The total size of blocks is too big. They do not fit into the cluster group FeeClusterGroup_0. Increase the size of the cluster or reduce the size of blocks.
***

So, you need to reduce FeeBlockSize (I can see in FeeBlockConfiguration_2 that FeeBlockSize is 7168) or you need to increase the size of cluster. The size of cluster can be increased by adding another FeeSubAddressArea.

I believe that it will work as expected if you fix this error as described above.

Re: s32k312 FEE

fengba_360 — Tue, 01 Oct 2024 12:02:59 GMT

Thank you for responding despite your busy schedule. I just tried your suggested solution. Of course, I had doubted whether this issue was the cause before, but after reducing the size of FeeBlockSize as shown in the image, the program still doesn't work as expected. Here is a screenshot of my recent test. Could you please look at it again?

Re: s32k312 FEE

fengba_360 — Tue, 01 Oct 2024 12:13:46 GMT

Of course, I have also tried the block size of 4 bytes as mentioned in the example routine, but it still didn't work. I have carefully compared the example routine with my configuration and can't find any differences. That's why I'm reaching out to you for help. Thank you.

Re: s32k312 FEE

lukaszadrapa — Wed, 02 Oct 2024 12:24:16 GMT

When calling:

MemAcc_Init(NULL_PTR);

...with NULL_PTR, you need to configure:

Not post-build:

As a result, the MemAcc was not initialized and some pointers pointed to invalid locations which caused hard fault reading.

Regards,

Lukas

Re: s32k312 FEE

fengba_360 — Thu, 03 Oct 2024 03:16:52 GMT

@lukaszadrapa

Thank you for your guidance. Now I can use FEE for data storage normally, but I have another question for you. Regarding the issue: "The total size of blocks is too big. They do not fit into the cluster group FeeClusterGroup_0. You need to increase the size of the cluster or reduce the size of the blocks." How should I configure the size of the cluster group? The places where I currently know I can make configurations are shown in the screenshots below. Please help.

Re: s32k312 FEE

lukaszadrapa — Fri, 04 Oct 2024 12:10:22 GMT

I was playing with the configuration but I can see that adding next physical sectors, clusters etc. does not help in this use case. The limitation is obviously given by physical size of sectors which is 8KB on S32K3. It also depends on other FeeBlocks. If you exceed certain threshold, the configurator will show mentioned message. The expectation is that the size of FeeBlocks is significantly smaller than size of physical sector. So, one solution I can see is to split the data to more blocks.

Regards,

Lukas

Re: s32k312 FEE

fengba_360 — Sun, 06 Oct 2024 12:58:33 GMT

I have conducted tests and found that the block size can work normally at 3072 bytes, but it cannot exceed 4000 bytes. However, the physical sector size can accommodate up to 8192 bytes. If you have any new developments, please let me know. Thank you for your answers.