When I configure the module Resource in EB my iS32K116, when I configure the Port module and generate the code, I will prompt that the relevant .m file cannot be parsed, but when I select the chip in the Resource as any other chip, the parsing of the Port module is successful, how can I solve or troubleshoot this problem?
And I have tried reinstalling the MCAL installation package, as well as using a version of the order, the situation has not changed.
EB Version:28.0.0
MCAL Version:S32K1XX_MCAL4_3_RTM_1_0_4
Solved! Go to Solution.
Hi Rooki_NXP,
Can you share me the link of the MCAL that you entered?
I enter this link on NXP
Thank you,
Nam.
Hi Rooki_NXP,
This issue already found out and report in our internal ticket MCAL-27236.
The root cause comes from the CRYPTOMANIFEST.MF in the Port plugin and it does not have information for "generate_PC/Port_S32K116_Resource.m", S32K142w and S32K144w
Root Cause Details: Missing configuration files in SIGN_FILES (NA for NewFeature)
Proposed Solution: Update missing configuration files in SIGN_FILES
Duplicated resource in generate_PB. Need to remove and replace by:
generate_PC/Port_S32K116_Resource.m
generate_PC/Port_S32K142w_Resource.m
generate_PC/Port_S32K144w_Resource.m
The issue was fixed in MCAL 4.3 RTM 1.0.5, i already tested and it's running well, please help me to use this release.
Thank you,
Nam.
Hi Rooki_NXP,
Please try to search MCAL package in NXP website. You can see the latest release of MCAL 4.3 is version 1.0.5 in Jul 31.
Thank you,
Nam.
It is in this software directory
I couldn't find it at the same address
Hi Rooki_NXP,
Can you share me the link of the MCAL that you entered?
I enter this link on NXP
Thank you,
Nam.
Hi Rooki_NXP,
I just try to reproduce in my side, and the issue comes from the fact that the CRYPTOMANIFEST file (in META-INF folder) doesn't sign derivative K116 PC (PreCompile). So it seems like a bug of signing process of license file with NXP side.
The PB (PostBuild Generate) can be executed, but you have to configure all modules as PB so it's not a clear solution.
One of another solution is signing again in your side, but i'm contacting to verify this solution first, so just inform to you like that.
Please wait me for a bit longer,
Thank you,
Nam.
Hi Rooki_NXP,
Please help me to use the EB Tresos version 24 as mentioned in Release Notes.
Thank you,
Nam.
It's still a bad situation. Do you have any other solutions?
Thank you for your suggestion. I will try this method