Mismatch in Variant Criterion path for MCAL SW32K358_RTD_R21_11_3.0.0_CD04_P02 with Tresos V29

[bG2023]

Hi,

I am trying to generate MCAL on a EB tresos project that I have received. I am using EB Tresos V29 and MCAL SW32K358_RTD_R21_11_3.0.0_CD04_P02 which are the same versions on which the project was developed.

When I tried to generate the MCAL, I am getting the below error for every single parameter present in the project: "The variant attribute of the node refers to selectable criterions, but no selectable is currently active." Please refer to the image attached for more info

My colleague is able to generate it successfully without issues and he is using the exact same project.

I tried creating the expected post build variant criterion's using sidebar but observed the path is being differed from what the project was initially built upon. Can you please help on how to create the criterion path as EB/PostBuildSelectable/PostBuildSelectableCriterion instead of what tresos is allowing EB/PostBuildSelectable/Criterions/PostBuildSelectableCriterion

FYI, My MCAL project has criterion path as EB/PostBuildSelectable/PostBuildSelectableCriterion and that is why it is raising an issue during generation.

Please let me know if you need any more info on the same.

[NamLee · Accepted solution]

Hi,

The problem comes from missing data inside SystemModel2.tdb file during zip and unzip process, so replacing this file by another file in another project will fix the issue.

Thank you,

Nam.

[bG2023]

Hi,

Yes, Looks like it is solving the issue. I compared the generated code and I observed no changes. I think we can close the ticket for now.

If I face this issue again then I will let you know. Thanks for your quick support.

[NamLee]

Hi Bala,

After few investigation, i think the issue comes from the fact that you may have missing files inside TresosProject (due to the zip files lost)

Please help me to check again to make sure these files are existing and have full data inside (not blank):

- SystemModel2.tdb (TresosProject/config)

- EditPostBuildVariantsSelectable.mem (TresosProject/.prefs)

- PostBuildVariantsSelectable.arxml (TresosProject/systemmod)

Please help me to remove EB Tresos Project before any retry.

If you already pass the errors by porting configuration files in to an example, please help me to compare this project with your current one, and coppy the missing files then try again. (that's what i do to find out the causes)

Thank you,

Nam.

[bG2023]

Hi,

I have checked those points and tried to figure out what changed.It would be helpful if we can have a short call to understand better. FYI I am located in the US and in the EST(Eastern Standard Time). Please find my comments below:

• SystemModel2.tdb (TresosProject/config) - not empty in the current project
• EditPostBuildVariantsSelectable.mem (TresosProject/.prefs) - not empty in the current project
  
• PostBuildVariantsSelectable.arxml (TresosProject/systemmod) - I dont have that file present at all in the current project. Even when this file is not present , when imported at my team member PC it is being created automatically and code generation was successful.
  

Coming to the case of importing the xdm files into example project, Once xdm files are copied it automatically it automatically renames the previous file and creates two new files below automatically.

So I copied the above files to my current project and tried refreshing. But PostBuildVariantsSelectable.arxml created from example project use case is being emptied automatically once I copy it to my own project. So I think your suggestion to copy the missing files and then try again is not working as expected.

[NamLee]

Hi Bala,

Please help me to compare "TresosProject" folder between Your current project (have issue) and The imported project (without issue). I'm pretty sure that there're some missing files, due to the PostBuildVariantsSelectable.arxml can't be generated.

I got a same issue of another customer before, and we follow these steps to find out the missing files.

I suggest you try to close EB project then do "make clean generate" command before any test.

Sure, I can have a short call with you through Teams chat, can you leave your contact here? I tried to find your .etas Teams contact but i can't find it.

Thank you,

Nam.

[bG2023]

Hi ,

Thanks for the response. I have tried removing the entire project and importing from newly unzipped project that is working on another colleague setup. Still I face the same issue.

Also, Can you please help me to understand how to "make clean generate" from Tresos GUI?

I see this is a public post, Is it possible to send me your email is so that I can drop an email from my work account?

[NamLee]

Hi Bala,

As i mentioned before, the root cause of this issue is missing files during zip and unzip folder, so please follow this steps:

- Import all .xdm configuration files into an RTD example (as you said, you already passed this step to have a running project without any issue) -> I'll call this project as ProjectA

- Compare TresosProject folder between ProjectA with you unzipped project (which has criterion variants issues -> I'll call this one as ProjectB)

- Try to coppy missing files (if any) from ProjectA to the ProjectB.

- Try to use command line "make clean generate" before opening EB Tresos

About this "make clean generate", it's another way to generate project without EB Tresos. You can follow instructions by reading the readme.txt file inside any RTD example project.

I also send you a personal message for contacting through Private Message, please help me to check your Messages.

Thank you,

Nam.

[bG2023]

Thanks for the info. I have sent an email with my availability.

[NamLee]

Hi Bala,

I can't see your email, seems like the email did not reach me.

I sent an email to your address in NXP community account, hope that can reach you.

Please help me check it again.

Thank you,

Nam.

[bG2023]

 Hi Nam,

Just a gentle reminder to check if you have any updates on my request.  As said the exact project with same version of tools working on my colleague setup without any modifications or importing into the sample project.

The issue here is that the same MCAL project has been delivered to 6 different teams and its difficult to maintain if we dont't what causing the issue here.

Thanks,

Bala.

[bG2023]

Hi,

Thanks for the timely response. Yeah I have tried the option you have suggested and the variant error is not present any more. But I am not sure if I can follow that approach.

Is there a way I can make it work in my current project itself rather than importing my xdm files to an example project? As said earlier, my colleague was able to generate without issues when using the same project. I want to understand whats missing in my setup which is causing this.

[NamLee]

Hi balaGrandhi,

Sorry for this inconvenience.

To workaround this issue, please enter an example in the package (such as Adc > EBT > K358), add all modules that you're using, then replace your xdm files or import epc files into that example, close EB and open it up, then try to build project again.

There's a small personal tip that i suggest you is that you should use makefile and run command "make clean generate" to make sure the project will run with your own configurations (instead of generate-build in EB)

Please let me know if you have further information.

Thank you,

Nam.