Remaking post as I have a better understanding of what the issue appears to be?
When I run the program, it appears to initialize the first MemAcc successfully, but the 2nd and 3rd is completely blank data and never initializes even once the first area is complete. In the example after the first is finished with 96 of 96 then the 2nd one fills in its values. The first never changes off JOB_STATE_STOP and AreaIndex 1 never moves off of JOB_STATE_STARTING.
I have each memsector batch configured identically and assigned to their own Memaccaddress configurations that are also identical.
A comparison with FEE_Example_S32K344 where once Length remain reaches 0, the area index 0 memacc data is removed and AreaIndex 1's information is used and it goes from JOB_STATE_STARTING to JOB_STATE_PROCESSING
What might be causing this error of not completeing the job on the first Memory area?
Also it initializes just fine with NULL_PTR for some reason? Which I find very confusing in both this and the example but I suppose I will not question it as I cannot find the config pointer for FEE_Init.
Hi @pb632146,
I haven't tested the project, but I noticed that you initialize MemAcc_Init() with a NULL_PTR.
Regards,
Daniel