S32DS Power v2.1 - SDK303 - Reload processor expert config fails with error on fatfs_update.chg

[remdzi]

Hello

I am using S32DS Power v2.1 with S32 SDK PA RTM 3.0.3

Everytime I reload the processor expert configuration I get these errors:

• Component is not selected (rtc_api)
• ERROR: Unexpected status of script: Beans\fatfs\Items\fatfs_update.chg, please contact Freescale support.
• No list to choose (RTC alarm list)
• No list to choose (RTC config list)

I always have to manually reselect the RTC API configured within FATFS. But the next time I reload the configuration the RTC API is deselected again and the same errors occur.

Regards,

Rémy

[petervlna]

Hello,

I was talking with our tool expert and he never encountered such issue.

The recommendation here is to uninstall it and do a fresh installation,

Best regards,

Peter

[remdzi]

Hello Peter,

I just tried with a fresh install on a new computer but I get the same error.

What I have done:

On a computer with W10 where S32DS was never installed

1. Install S32DS_Power_Win32_v2.1.exe
2. Install S32DS_PA_2.1_UP14
3. Create a new S32DS application for MPC5748G, only select Z4_0 core and choose to use SDK 3.0.3
4. Add a new fatfs from repository SDK_S32_PA15. PE asks for an OsIf component: Choose New component from  DK_S32_PA15
5. Configure fatfs component to have timestamp using RTC. PE asks for an Rtc component: Choose New component from  DK_S32_PA15
6. Reload configuration
7. Get the errors

Regards

Rémy

[petervlna]

Hello,

Ok, then I expect the issue is in the SDK itself.

I never used it before so I will rise internal ticket for SW team to check it.

Meantime, here are some steps that have helped others, maybe you will find it usefull:

1. Manually reselect RTC API before saving the configuration:

   • After reloading, go to FATFS settings and reselect the RTC API.
   • Save the configuration immediately after making the change.

2. Force dependency resolution:

   • Open the .mex file in a text editor and verify that the RTC component is listed and properly linked to FATFS.
   • Look for entries like:
     <Component name="rtc_api" selected="true"/>
     and ensure FATFS references it.

3. Clean and regenerate the Processor Expert configuration:

   • Delete the Generated_Code and Project_Settings folders.
   • Reopen the project and regenerate the configuration.

4. Update or patch the SDK:

   • Check if there's a newer patch or hotfix for S32 SDK PA RTM 3.0.3.
   • Sometimes NXP releases silent patches that fix Processor Expert script issues.

Best regards,
Peter

[remdzi]

Hello Peter,

I have checked with a text editor the *.pe file (*.mex doesn't exists).

Here is the extract of the fatfs config that select osif and rtc components:

<ItemState>

<ItemSymbol>LinkItem</ItemSymbol>

<ListItemCount>1</ListItemCount>

</ItemState>

<ItemState>

<ItemSymbol>LinkGrp</ItemSymbol>

<ReadOnly>false</ReadOnly>

<UserReadOnly>false</UserReadOnly>

<Expanded>true</Expanded>

</ItemState>

<ItemState>

<ItemSymbol>Link0</ItemSymbol>

<ReadOnly>false</ReadOnly>

<UserReadOnly>false</UserReadOnly>

<Value>osif1</Value>

</ItemState>

<ItemState>

<ItemSymbol>LinkRTC</ItemSymbol>

<ReadOnly>false</ReadOnly>

<UserReadOnly>false</UserReadOnly>

<Value>rtcTimer1</Value>

</ItemState>

I have tried to manually patch the file with:

<ListItemCount>1</ListItemCount> --> <ListItemCount>2</ListItemCount>

or

<ItemSymbol>LinkRTC</ItemSymbol> --> <ItemSymbol>Link1</ItemSymbol>

but it changes nothing after reloading the configuration the rtc_api is always deselected.

Even more stange: if I change

<Value>osif1</Value> --> <Value>foo</Value>

after reloading the configuration osif1 is still selected...

Please keep me informed of the ticket you have open and the answer of your software team.

Regard

Rémy

[petervlna]

Hello,

I will post here as soon as I will get feedback from SW team.

Best regards,

Peter

[petervlna]

Hello,

did you try to reinstall the whole S32DS?

It is some system fault bound to while Eclipse.

best regards,

Peter

[remdzi]

Hello Peter,

Yes: As written in my previous messages I did a full reinstallation but got the same error.

Here we have 3 computers with the same error.

Rémy

[jiri_kral]

Hi Rémy, 

assuming that you also tried create new workspace. In some cases, the workspace metadata may be corrupted. 

Can you please share log file from your current workspace? The log file is located in .metadate directory inside the workspace. 

[remdzi]

Hi Jiri,

I have tried with a new workspace but I get the same result

Please find attached the log

[petervlna]

Hello,

I have spoken with S32DS team. They will test this version and reply here.

Best regards,

Peter