Nested macro opening within "[!ERROR]

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Nested macro opening within "[!ERROR]

Jump to solution
2,093 Views
JwDouble
Contributor II

ENV:EB tresos 28.1

MCAL:MPC574XP_MCAL_4.0_RTM_HF1_2.0.2

MCU:MPC5744P

After the MCU module is configured, there is no problem in compiling. After the GPT module is added and configured, There came the "Parsing file "C:\EB\tresos\plugins\MPC574XP_MCAL4_0_RTM_HF1_2_0_2\eclipse\plugins\Gpt_TS_T2D30M20I2R0/generate_PB/src/Gpt_PBcfg.c (signed)", line "80"
[C:\EB\tresos\plugins\MPC574XP_MCAL4_0_RTM_HF1_2_0_2\eclipse\plugins\Gpt_TS_T2D30M20I2R0/generate_PB/Gpt_VersionCheck_Src_PB.m (signed):54]: Nested macro opening within
"[!ERROR]
"AUTOSAR release revision version number of the Basic Software Module Description ..."
"

In this case, the message [!ERROR] does not close the loop correctly. Therefore, I modify the corresponding file as prompted, resulting in a signature problem. In summary, what I want to solve is the problem that [!ERROR] does not close the loop, and it is not necessary to modify the signature problem

JwDouble_0-1743559644099.png

 

0 Kudos
Reply
1 Solution
2,046 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello,

I have did the tests and also created a new project from scratch and I can confirm I am seeing the same as you.

I was investigating further, and found out that this is linked to the version of Tresos.

Since I am using the version 28.8 and the plugin was originally released for version 14.

See the release notes.

2.4 Modules Configuration
Modules configurations were developed and tested using the Tresos Configuration Tool
version "EB tresos Studio 14.2.1 b140128-1223"

Colleague of mine who is AUOTSAR expert express that this nested macro error rise up if the plugin is very old and run in the newer versions of Tresos.

Best regards,

Peter

View solution in original post

4 Replies
2,082 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello,

Looks like your signature of GPT is invalid

petervlna_0-1743578517696.png

You cannot change AUTOSAR code without signing it via HW key.

Customers do not have such possibility. return to original GPT plugging with original files.

Could you elaborate the issue closer? I am not sure if I understood it from so little information.

best regards,

Peter

0 Kudos
Reply
2,074 Views
JwDouble
Contributor II

Hello,

I downloaded the MCAL package for the MPC574xP from the following page:

https://www.nxp.com/products/MPC574xP

JwDouble_1-1743642184069.png

I believe this is the official package. I have successfully configured the MCU module; however, when configuring the GPT module, EB reported an error. Based on the error details, I checked the files and confirmed that both
\Gpt_TS_T2D30M20I2R0\generate_PBGpt_VersionCheck_Src_PB.m and \Gpt_TS_T2D30M20I2R0\generate_PC\Gpt_VersionCheck_Src.m contain the incorrect code [!ERROR]. The correct code should be [!ERROR!].

Below are my project code.

0 Kudos
Reply
2,047 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello,

I have did the tests and also created a new project from scratch and I can confirm I am seeing the same as you.

I was investigating further, and found out that this is linked to the version of Tresos.

Since I am using the version 28.8 and the plugin was originally released for version 14.

See the release notes.

2.4 Modules Configuration
Modules configurations were developed and tested using the Tresos Configuration Tool
version "EB tresos Studio 14.2.1 b140128-1223"

Colleague of mine who is AUOTSAR expert express that this nested macro error rise up if the plugin is very old and run in the newer versions of Tresos.

Best regards,

Peter

2,011 Views
JwDouble
Contributor II

Hello,

I enjoyed the Chinese traditional Qingming Festival and am delighted to have solved this challenging problem after a wonderful holiday. I have successfully configured the GPT module, and I truly appreciate the expertise you and your colleagues provided. Thank you very much.

0 Kudos
Reply