TJA1153 PINOUT & Datasheet Hi, For a product development, we are planning to use S32K MCU along with Secure CAN chip TJA1153. Could you provide technical datasheet as I could not find in online. I need to know the PINOUT, voltage levels, operating modes and other features. Thanks Karthik Raja Re: TJA1153 PINOUT & Datasheet Hi Thanks for that information. When I checked Evaluation boards BOM, S32K3X4EVB is using TJA1443ATK but in the interface list & in the block diagram it is shown as TJA1153.  Are both same or why it is still given like this. Kindly clarify which CAN transceiver is used in S32K3X4EVB board. Re: TJA1153 PINOUT & Datasheet Hi Karthik, The TJA1153A datasheet as well as other useful documentation are classified as Secure Files requiring an NDA. If your company has not signed the NDA with NXP yet, you can request it from: https://www.nxp.com/support/support:SUPPORTHOME If there is a valid NDA in place, you can download the datasheet from: https://www.nxp.com/products/interfaces/can-transceivers/secure-can-transceivers/secure-hs-can-transceiver-with-sleep-mode:TJA1153 Please make sure you are signed in to nxp.com. If you do not see the datasheet, please click on "Request additional access" or edit your secure access rights by going to My NXP > Profile. For more information about secure access rights, please refer to this website: https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS The TJA1153A is a standalone HS-CAN transceiver with Sleep mode offering these security features: In case there are no security violations detected, the TJA1153A behaves like a standard HS-CAN transceiver such as the TJA1443ATK. BR, Tomas Re: TJA1153 PINOUT & Datasheet Hi, And also when I checked S32K3X4EVB interfaces it is given as TJA1153 is used but when I checked BOM I found TJA1443ATK chip is used. But I see TJA1443 chip is not secure CAN.  Can you clarify this, or secure CAN is something to do with algorithms? Re: TJA1153 PINOUT & Datasheet Hi When I checked Evaluation boards BOM, S32K312EVB is using TJA1043TKY part and S32K3X4EVB is using TJA1443ATK but in the interface list it is shown as TJA1153 is used in S32K3X4EVB. Can you please clarify this.

RT 1176 FlexSPI RW frequency DQS hi, we have a question regarding the flash NOR RW freq . we currenty working on a custom board using the RT1176 , we are implementig a  flashloader a bootsel and a bootloader as we want to boot from  IS25LP128 SERIAL FLASH MEMORY WITH 133MHZ MULTI I/O SPI & QUAD I/O  so the boot flow is perfect when running on 60Mhz serialClkFreq , but we need to raise that to 133Mhz  after Refernce manual lookup , we found that we need a to mux a FLEXSPI DQS pin and change the sampling to  readSampleClksrc= kFlexSPIReadSampleClk_LoopbackFromDqsPad . but when looking for pin mux options we found 3 choices basicaly AD_17 ,  SD_B2_05 and EMC_B2_18  we tried three of them and none worked (no boot)  is there anything else we're missing !  thank you  Yosri  #i.MX-RT1176   Re: RT 1176 FlexSPI RW frequency DQS Hi @yosri_c According to the rt1170 RM, it can be used as FLEXSPI1_A_DQS pin. But for Boot, it can not be used as DQS pin. Hope this will help you. BR Hang Re: RT 1176 FlexSPI RW frequency DQS hi , i read the section and that's why i asked , the GPIO_EMC_B2_18 pin was used in a previous RM as FlexSPI_DQS_A pin , and then i read about it in another thread that it will be depracated ! my question was , does  this pin support the DQS function  or not anymore  ( RT1176 - flexSPI DQS connection for max R/W speed - NXP Community ) Thank you  Re: RT 1176 FlexSPI RW frequency DQS Hi @yosri_c  Not all FlexSPI Pinmux combinations can be used to connect to serial NOR Flash for boot. About boot pin, please refer to the system boot chapter in the RM manual. Hope this will help you. BR Hang Re: RT 1176 FlexSPI RW frequency DQS hi @Harry_Zhang , okay thank you for the reply , we're just  conserned and want to know the use of the PIN GPIO_EMC_B2_18 is it deprecated and doesn't support DQS functionality anymore ?  because we still have it in the refernce manual as a DQS pin . Thank you so much indeed for clarifying this  Re: RT 1176 FlexSPI RW frequency DQS Hi @yosri_c  Are you using the Primary Pin Group or the Secondary Pin Group？ According the i.MX RT1170  Reference Manual. For the secondary pin group, the Maximum Flash frequency supported on this port is 100MHz. . And have you chosen this frequency? Hope this will help you. BR Hang Re: RT 1176 FlexSPI RW frequency DQS hi,  thank you for the answer . as i mentionned we already changed the sampling config to kFLEXSPI_ReadSampleClkExternalInputFromDqsPad. we changed the  .serialClkFreq = kFlexSpiSerialClk_133MHz  we muxed the pin  IOMUXC_SetPinMux(          IOMUXC_GPIO_AD_17_FLEXSPI1_A_DQS,   // GPIO_EMC_B2_18 is configured as FLEXSPI1_A_DQS        1U);                                    //  Software Input On Field: Force input path of pad GPIO_EMC_B2_18      IOMUXC_SetPinConfig(        IOMUXC_GPIO_AD_17_FLEXSPI1_A_DQS,  //  GPIO_EMC_B2_18 PAD functional properties :        0x07U);                                but still we couldn't boot  Re: RT 1176 FlexSPI RW frequency DQS Hi @yosri_c  When the transmission rate is relatively high, in order to transmit data more accurately, DQS is provided by flash. So you can try to config config.rxSampleClock = kFLEXSPI_ReadSampleClkExternalInputFromDqsPad. And config the pin mux that you mentioned. Hope this will help you. BR Hang

[S32Z] VKMS for HSE-H/M firmware Hi NXP Team! I noticed that S32K has support for VKMS (vehicle key management system). See this post and the application note "an744410 - K3_SecurityWorkshop_VKMS__29Mar2022.pdf (1.0).pdf". Is VKMS (core) also available for the HSE-H/M firmware used for S32Z? Best regards, Philipp Sommer Re: [S32Z] VKMS for HSE-H/M firmware Hi, We understand that all S32Z/E related information is under control of distribution, for which we can recommend contacting your local NXP FAE/DFAE/representative. We do apologize for the inconvenience. Please, let us know. Re: [S32Z] VKMS for HSE-H/M firmware I think we can move this to S32Z2 - NXP Community

How to use PFE function of S32G-VNP-RDB3 (s32g399a) based on RTOS? We are developing S32G-VNP-RDB3 (s32g399a) based on RTOS. I know we need to use PFE to use more than one Ethernet port, but PFE requires a separate driver to be applied, and I don't know how to do that. To rephrase my question, it is as follows. 1. How to use PFE function in S32G-VNP-RDB3(s32g399a)? 2. is there any demo file for PFE's PTP and TIME Aware Shaper features? If anyone knows how to use it, please help me.... Please help... Re: How to use PFE function of S32G-VNP-RDB3 (s32g399a) based on RTOS? Hi ! Thank you very much for your response. about Q1 When I got the tresos from that page (link: S32G3 Safe and Secure Vehicle Network Processor | NXP Semiconductors), I could not get any confirmation regarding the license. Instead, I downloaded version 29 from the place where you can download different versions, checked the activation code, activated it, and am using it. About Q2 and Q3 I'm having trouble using and developing it due to the lack of documentation. I will try to check the related release notes. Thank you for your help. For additional questions, I will create a new session to ask. Re: How to use PFE function of S32G-VNP-RDB3 (s32g399a) based on RTOS? Hi, Below will be some comments on regards of your questions: Q1. Is it mandatory to use Tresos to use PFE FW? [DA]: We understand that the PFE MCAL driver is only to be used with EB Tresos. As for the license error, did you activate EB Tresos itself? Q2. Do you know any documentation explaining how to use PFE FW in S32 Design Studio? [DA]: At this moment, there is no up-to-date documentation for PFE MCAL under S32DS. We do apologize. Q3. Is PFE FW used in conjunction with PFE MCAL Driver? [DA]: We understand that there is indeed a requirement for PFE MCAL with PFE FW, since it details under the respective release notes that uses both RTD package and PFE FW. Please, let us know. Re: How to use PFE function of S32G-VNP-RDB3 (s32g399a) based on RTOS? I am very grateful for your response. I went to the site you told me about and downloaded the Dirver and Firmware for PFE, and I had additional questions in the process. Q1. Is it mandatory to use Tresos to use PFE FW?   Q1.1. I installed the PFE FW plugin from Tresos, but when I open it in Tresos, I get a license error like in the attached picture. Q2. Do you know any documentation explaining how to use PFE FW in S32 Design Studio? Q3. Is PFE FW used in conjunction with PFE MCAL Driver? Re: How to use PFE function of S32G-VNP-RDB3 (s32g399a) based on RTOS? Hi, On regards of PFE usage under the M7 core (which we assume is the one being used with RTOS), there is a PFE Driver for M7 MCAL, which should be available under the Automotive Software Package Manager inside the S32G3 product page (link: S32G3 Safe and Secure Vehicle Network Processor | NXP Semiconductors). The specific version needs to be paired with an specific version of RTD, which should be also available under the Automotive Software Package Manager. As for the specifics of being implemented with RTOS, we understand that the available examples do not use RTOS. As for the specific features, we understand that they are not implemented under the available examples. We do apologize. Please, let us know.

16位总线和IVT数据的并行NOR-Flash 你好。 在 i.MX7D 参考手册第 1241 页上，IVT 头格式图表明要设置的值为 0xD1-0x0020-0x40 到 .word0xD1002040，但在20132年“i.MX6 IVT结构”中Anson Huang回答说应该是.word0x402000D1。 我认为手册上说的是 0x400 = 0xD100 0x402 = 0x2040 但这是错误的吗？ 谢谢！ 回复：16位总线和IVT数据的并行NOR闪存 谢谢 Harvey021。 那么安森用小端方式解释了吗？ 我很困惑，因为参考手册说它是大端的。

S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi, I am trying to build the PFE-DRV_S32G_M7_MCAL_1.4.0 MasterProject_RDB3. I followed the instructions described in the document S32G PFE Master Demo Building V2 by John Li. I successfully created the MasterProject_RDB3 project in EB Tresos and copied all the generated files to the 'PFE-DRV_S32G_M7_MCAL_1.4.0/example_application' folder. However, I encountered an issue where the Mcl_Types.h file is reported as missing. Could you help identify what I might be missing or misconfigured? For reference, I am using: Design Studio 3.5 RTD 4.4 4.0.2 EB Tresos 27.1.0 PFE-DRV_S32G_M7_MCAL_1.4.0 $ make CC src/CDD_Mcl_Cfg.c In file included from src/CDD_Mcl_Cfg.c:39: include/CDD_Mcl_Cfg.h:41:10: fatal error: Mcl_Types.h: No such file or directory 41 | #include "Mcl_Types.h" | ^~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:690: output_RDB3/CDD_Mcl_Cfg.o] Error 1 Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD! I'm glad to know that you were able to solve your problem! Thanks for selecting my reply as a solution. Best regards, Alejandro Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e and @GuilhermeS32G, Thank you both! After recreating the EB project and ensuring the "Copy projects into workspace" option was not selected, I was able to successfully build the entire PFE 1.4.0 and generate the ELF file. I truly appreciate your patience and your help in resolving this issue. Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Thanks again @GuilhermeS32G! @XD, as mentioned in a previous comment, avoid using the Copy project into workspace option when importing the project into Tresos, this will cause missing files problems: You should access the original folder in which the project was decompressed with cygwin and then follow the build steps, for me it is C:\NXP\PFE-DRV_S32G_M7_MCAL_1.4.0\example_application, also please use the original make file, as mentioned by Guilherme, you only need to modify the project_parameters.mk file. It is also worth mentioning that after I changed my RTD version to the correct one, I did not need to manually import the project into tresos, I just specified the workspace path in the project_parameters and the build scripts took care of everything. As previously mentioned I ran the following commands: make clean ; make generate ; make build Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD , From your generate output I see that your files are being generated at C:\EB\tresos\workspace\generate_RDB3\  when they actually should be generated at /cygdrive/c/Users/XD/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0_test/example_application/generate_RDB3 This is the reason why the header file is not being found. Did you modify the content of the Makefile? If so, please rollback to the original version. There is no need to manually include any header file. All of the changes are made in the project_parameters.mk file. Besides, when running make build, there are some files that should be compile before Eth_43_PFE.c: CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/autolibc.c CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/blalloc.c CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/elf.c CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c ... Try to delete the output_RDB3 folder before running make build or run make clean. Best regards, Guilherme Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , Thank you for looking into this issue. Actually, I am using D2306 now. I re-copied everything and attached the output from the make generate command. There was an error indicating that the folder already exists, followed by some warnings. After generating, I encountered a missing file error when running make build. AzureAD+XD@SF-XD /cygdrive/c/Users/XD/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0_test/example_application $ make generate cp eth_pfe_configs/00_pfe_fci_l2br_test/MasterProject_RDB3/Eth_1.xdm MasterProject_RDB3/config C:/EB/tresos/bin/tresos_cmd.bat -data C:/EB/tresos/workspace importProject C:/Users/XD/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0_test/example_application/MasterProject_RDB3 2>&1 EB tresos Studio 27.1.0 b200625-0900 Copyright 2003-2020 Elektrobit Automotive GmbH Current workspace: C:\EB\tresos\workspace Importing project C:\Users\XD\Downloads\PFE-DRV_S32G_M7_MCAL_1.4.0_test\example_application\MasterProject_RDB3 ERROR 24-12-03,16:48:54 (11102) A project with name "MasterProject_RDB3" already exists in workspace Errors "1" Warnings "0" make: [Makefile:726: generate] Error 1 (ignored) C:/EB/tresos/bin/tresos_cmd.bat -data C:/EB/tresos/workspace autoconfigure MasterProject_RDB3 GenerateAllVariants 2>&1 EB tresos Studio 27.1.0 b200625-0900 Copyright 2003-2020 Elektrobit Automotive GmbH Current workspace: C:\EB\tresos\workspace INFO 24-12-03,16:49:00 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:00 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:00 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:00 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:00 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USOs_TS_T40D11M40I2R" instead of "EB_TS_MOD_USOs_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USOs_TS_T40D11M40I2R" instead of "EB_TS_MOD_USOs_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USOs_TS_T40D11M40I2R" instead of "EB_TS_MOD_USOs_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USSerdes_TS_T40D11M4" instead of "EB_TS_MOD_USSerdes_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USSerdes_TS_T40D11M4" instead of "EB_TS_MOD_USSerdes_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USSerdes_TS_T40D11M4" instead of "EB_TS_MOD_USSerdes_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:02 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USBaseNXP_TS_T40D11M" instead of "EB_TS_MOD_USBaseNXP_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USBaseNXP_TS_T40D11M" instead of "EB_TS_MOD_USBaseNXP_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USBaseNXP_TS_T40D11M" instead of "EB_TS_MOD_USBaseNXP_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:03 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:05 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:05 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:05 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:05 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. BUILD SUCCESSFUL INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:06 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. BUILD SUCCESSFUL WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1105Q/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110b/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110a/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Eth_1/ELEMENTS/Eth/EthConfigSet/EthCtrlConfig/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigEgressLastSchedulerRef" with value "ASPath:/Eth_1/Eth/EthConfigSet/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigScheduler_0" does not refer to nodes. INFO 24-12-03,16:49:00 (13030) Code generation (mode: "generate") Running generator "Mcu_TS_T40D11M40I2R0" in mode "generate" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:00 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Mcu.epc INFO 24-12-03,16:49:00 (13030) Code generation (mode: "generate") Running generator "Mcu_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:00 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Power_Ip_PBcfg.c" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Clock_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Mcu_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Mcu_Ipw_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Clock_Ip_PBcfg.h" INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Mcu_PBcfg.h" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ram_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ram_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Clock_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Clock_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ram_Ip_PBcfg.h" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Ram_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Mcu_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Power_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Mcu_PBcfg.c" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Power_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Clock_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Power_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Ram_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Power_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Platform_TS_T40D11M40I2R0" in mode "generate" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Platform.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Platform_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\IntCtrl_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\IntCtrl_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\System_Ip_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\System_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Platform_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Platform_Ipw_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Platform_Ipw_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Platform_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Platform_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\IntCtrl_Ip_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Resource_TS_T40D11M40I2R0" in mode "generate" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Resource.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Resource_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Os_TS_T40D11M40I2R0" in mode "generate" for module "Os_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Os.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Os_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Os_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Os_cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Dem_TS_T40D11M40I2R0" in mode "generate" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Dem.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Dem_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dem_IntErrId.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Mcl_TS_T40D11M40I2R0" in mode "generate" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Mcl.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Mcl_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Dma_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\CDD_Mcl_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Cache_Ip_Cfg_DeviceRegisters.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Dma_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Mcl_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\CDD_Mcl_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Mcl_Ip_Cfg_DeviceRegisters.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\CDD_Mcl_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg_Devices.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg_DeviceRegistersV3.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\CDD_Mcl_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Cache_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\CDD_Mcl_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Serdes_TS_T40D11M40I2R0" in mode "generate" for module "Serdes_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Serdes.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Serdes_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Serdes_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Serdes_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ipw_PBCfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ip_PBCfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Serdes_Ip_PBCfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Serdes_Ipw_PBCfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ip_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "EcuC_TS_T40D11M40I2R0" in mode "generate" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\EcuC.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "EcuC_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Gpt_TS_T40D11M40I2R0" in mode "generate" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Gpt.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Gpt_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Gpt_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Gpt_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Rtc_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Stm_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Gpt_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Stm_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Stm_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Rtc_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Gpt_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Gpt_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Pit_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Rtc_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Ftm_Gpt_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Stm_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Gpt_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Gpt_Ipw_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Gpt_Ipw_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Gpt_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Pit_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Pit_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Rtc_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Pit_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Spi_TS_T40D11M40I2R0" in mode "generate" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Spi.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Spi_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_PBcfg.h" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ip_PBcfg.h" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Spi_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ipw_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ipw_PBcfg.h" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Lpspi_Ip_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Lpspi_Ip_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Spi_Ipw_PBcfg.c" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Spi_Ip_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Lpspi_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "SafetyBase_TS_T40D11M20I2R0" in mode "generate" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\SafetyBase.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "SafetyBase_TS_T40D11M20I2R0_GeneratorId" in mode "generate" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\SafetyBase_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Eth_43_PFE_TS_T40D11M14I0R0" in mode "generate" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Eth.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Eth_43_PFE_TS_T40D11M14I0R0_GeneratorId" in mode "generate" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Eth_43_PFE_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\pfe_cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Eth_43_PFE_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Eth_43_PFE_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Eth_43_PFE_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "BaseNXP_TS_T40D11M40I2R0" in mode "generate" for module "BaseNXP_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\BaseNXP.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "BaseNXP_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "BaseNXP_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\modules.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Soc_Ips.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\OsIf_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\OsIf_ArchCfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\OsIf_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\PlatformTypes.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Port_TS_T40D11M40I2R0" in mode "generate" for module "Port_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Port.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Port_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Port_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Siul2_Port_Ip_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Port_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Port_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Siul2_Port_Ip_PBcfg.c" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Siul2_Port_Ip_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Siul2_Port_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:04 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Port_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:05 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Port_PBcfg.c" INFO 24-12-03,16:49:05 (13030) Code generation (mode: "generate") Running generator "Mcu_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:05 (13030) Code generation (mode: "generate") Running generator "Platform_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:05 (13030) Code generation (mode: "generate") Running generator "Resource_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Dem_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Mcl_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "EcuC_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Gpt_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Spi_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "SafetyBase_TS_T40D11M20I2R0_UniqueNGGeneratorId" in mode "generate" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Eth_43_PFE_TS_T40D11M14I0R0_UniqueNGGeneratorId" in mode "generate" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Port_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Port_TS_T40D11M40I2R0" WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1105Q/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110b/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110a/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:00 (1069) Code generation (mode: "generate") The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Eth_1/ELEMENTS/Eth/EthConfigSet/EthCtrlConfig/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigEgressLastSchedulerRef" with value "ASPath:/Eth_1/Eth/EthConfigSet/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigScheduler_0" does not refer to nodes. INFO 24-12-03,16:49:00 (13030) Code generation (mode: "generate") Running generator "Mcu_TS_T40D11M40I2R0" in mode "generate" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:00 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Mcu.epc INFO 24-12-03,16:49:00 (13030) Code generation (mode: "generate") Running generator "Mcu_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:00 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Power_Ip_PBcfg.c" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Clock_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Mcu_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Mcu_Ipw_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Clock_Ip_PBcfg.h" INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Mcu_PBcfg.h" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ram_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ram_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Clock_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Clock_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ram_Ip_PBcfg.h" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Ram_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Mcu_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Power_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:01 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Mcu_PBcfg.c" INFO 24-12-03,16:49:01 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Power_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Clock_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Power_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Ram_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Power_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Platform_TS_T40D11M40I2R0" in mode "generate" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Platform.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Platform_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\IntCtrl_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\IntCtrl_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\System_Ip_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\System_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Platform_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Platform_Ipw_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Platform_Ipw_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Platform_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Platform_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\IntCtrl_Ip_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Resource_TS_T40D11M40I2R0" in mode "generate" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Resource.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Resource_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Os_TS_T40D11M40I2R0" in mode "generate" for module "Os_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Os.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Os_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Os_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Os_cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Dem_TS_T40D11M40I2R0" in mode "generate" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Dem.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Dem_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dem_IntErrId.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Mcl_TS_T40D11M40I2R0" in mode "generate" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Mcl.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Mcl_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Dma_Ip_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\CDD_Mcl_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Cache_Ip_Cfg_DeviceRegisters.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Dma_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Mcl_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\CDD_Mcl_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Mcl_Ip_Cfg_DeviceRegisters.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\CDD_Mcl_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg_Devices.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_Cfg_DeviceRegistersV3.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\CDD_Mcl_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Cache_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\CDD_Mcl_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Dma_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Serdes_TS_T40D11M40I2R0" in mode "generate" for module "Serdes_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Serdes.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Serdes_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Serdes_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Serdes_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ipw_PBCfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ip_PBCfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Serdes_Ip_PBCfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Serdes_Ipw_PBCfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Serdes_Ip_CfgDefines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "EcuC_TS_T40D11M40I2R0" in mode "generate" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\EcuC.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "EcuC_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Gpt_TS_T40D11M40I2R0" in mode "generate" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Gpt.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Gpt_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Gpt_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Gpt_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Rtc_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Stm_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Gpt_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Stm_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Stm_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Rtc_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Gpt_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Gpt_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Pit_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Rtc_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Ftm_Gpt_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Stm_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Ftm_Gpt_Ip_Cfg_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Gpt_Ipw_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Gpt_Ipw_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Gpt_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Pit_Ip_PBcfg.c" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Pit_Ip_PBcfg.h" INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Rtc_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Pit_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Spi_TS_T40D11M40I2R0" in mode "generate" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Spi.epc INFO 24-12-03,16:49:02 (13030) Code generation (mode: "generate") Running generator "Spi_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:02 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_PBcfg.h" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ip_PBcfg.h" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Spi_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ipw_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ipw_PBcfg.h" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Lpspi_Ip_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Lpspi_Ip_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Spi_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Spi_Ipw_PBcfg.c" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Spi_Ip_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Lpspi_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "SafetyBase_TS_T40D11M20I2R0" in mode "generate" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\SafetyBase.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "SafetyBase_TS_T40D11M20I2R0_GeneratorId" in mode "generate" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\SafetyBase_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Eth_43_PFE_TS_T40D11M14I0R0" in mode "generate" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Eth.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Eth_43_PFE_TS_T40D11M14I0R0_GeneratorId" in mode "generate" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Eth_43_PFE_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\pfe_cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Eth_43_PFE_PBcfg.c" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Eth_43_PFE_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Eth_43_PFE_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "BaseNXP_TS_T40D11M40I2R0" in mode "generate" for module "BaseNXP_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\BaseNXP.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "BaseNXP_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "BaseNXP_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\modules.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Soc_Ips.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\OsIf_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\OsIf_ArchCfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\OsIf_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\PlatformTypes.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Port_TS_T40D11M40I2R0" in mode "generate" for module "Port_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (20053) Code generation (mode: "generate") Generating file C:\EB\tresos\workspace\generate_RDB3\output\Port.epc INFO 24-12-03,16:49:03 (13030) Code generation (mode: "generate") Running generator "Port_TS_T40D11M40I2R0_GeneratorId" in mode "generate" for module "Port_TS_T40D11M40I2R0" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Siul2_Port_Ip_Defines.h" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Port_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Port_Cfg.c" (leaving file unchanged) INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Siul2_Port_Ip_PBcfg.c" INFO 24-12-03,16:49:03 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Siul2_Port_Ip_PBcfg.h" INFO 24-12-03,16:49:03 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Siul2_Port_Ip_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:04 (13016) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\include\Port_Cfg.h" (leaving file unchanged) INFO 24-12-03,16:49:05 (13014) Code generation (mode: "generate") Generated "C:\EB\tresos\workspace\generate_RDB3\src\Port_PBcfg.c" INFO 24-12-03,16:49:05 (13030) Code generation (mode: "generate") Running generator "Mcu_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:05 (13030) Code generation (mode: "generate") Running generator "Platform_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:05 (13030) Code generation (mode: "generate") Running generator "Resource_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Dem_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Mcl_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "EcuC_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Gpt_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Spi_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "SafetyBase_TS_T40D11M20I2R0_UniqueNGGeneratorId" in mode "generate" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Eth_43_PFE_TS_T40D11M14I0R0_UniqueNGGeneratorId" in mode "generate" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:06 (13030) Code generation (mode: "generate") Running generator "Port_TS_T40D11M40I2R0_UniqueNGGeneratorId" in mode "generate" for module "Port_TS_T40D11M40I2R0" Unattended wizard "Execute multiple tasks(GenerateAllVariants)(GenerateAllVariants)" exited with warnings. Errors "0" Warnings "8" C:/EB/tresos/bin/tresos_cmd.bat -data C:/EB/tresos/workspace make generate_swcd MasterProject_RDB3 2>&1 EB tresos Studio 27.1.0 b200625-0900 Copyright 2003-2020 Elektrobit Automotive GmbH Current workspace: C:\EB\tresos\workspace Generating project MasterProject_RDB3 in mode generate_swcd INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USOs_TS_T40D11M40I2R" instead of "EB_TS_MOD_USOs_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USOs_TS_T40D11M40I2R" instead of "EB_TS_MOD_USOs_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USBaseNXP_TS_T40D11M" instead of "EB_TS_MOD_USBaseNXP_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USBaseNXP_TS_T40D11M" instead of "EB_TS_MOD_USBaseNXP_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USSerdes_TS_T40D11M4" instead of "EB_TS_MOD_USSerdes_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USSerdes_TS_T40D11M4" instead of "EB_TS_MOD_USSerdes_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:13 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:14 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. WARNING 24-12-03,16:49:12 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110a/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:12 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1105Q/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:12 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110b/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:12 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Eth_1/ELEMENTS/Eth/EthConfigSet/EthCtrlConfig/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigEgressLastSchedulerRef" with value "ASPath:/Eth_1/Eth/EthConfigSet/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigScheduler_0" does not refer to nodes. INFO 24-12-03,16:49:13 (13030) Running generator "Mcu_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Mcu_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:13 (13030) Running generator "Resource_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13030) Running generator "SafetyBase_TS_T40D11M20I2R0_GeneratorId" in mode "generate_swcd" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:13 (13030) Running generator "Os_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Os_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13030) Running generator "BaseNXP_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "BaseNXP_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\BaseNXP_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:13 (13030) Running generator "Dem_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13030) Running generator "Serdes_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Serdes_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Serdes_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:13 (13030) Running generator "EcuC_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13030) Running generator "Gpt_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:13 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Gpt_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:14 (13030) Running generator "Spi_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:14 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Spi_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:14 (13030) Running generator "Eth_43_PFE_TS_T40D11M14I0R0_GeneratorId" in mode "generate_swcd" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:14 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Eth_43_PFE_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:14 (13030) Running generator "Platform_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:14 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Platform_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:14 (13030) Running generator "Mcl_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:14 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Mcl_Bswmd.arxml" (leaving file unchanged) INFO 24-12-03,16:49:14 (13030) Running generator "Port_TS_T40D11M40I2R0_GeneratorId" in mode "generate_swcd" for module "Port_TS_T40D11M40I2R0" INFO 24-12-03,16:49:14 (13016) Generated "C:\EB\tresos\workspace\generate_RDB3\swcd\Port_Bswmd.arxml" (leaving file unchanged) Errors "0" Warnings "4" C:/EB/tresos/bin/tresos_cmd.bat -data C:/EB/tresos/workspace make verify_swcd MasterProject_RDB3 2>&1 EB tresos Studio 27.1.0 b200625-0900 Copyright 2003-2020 Elektrobit Automotive GmbH Current workspace: C:\EB\tresos\workspace Generating project MasterProject_RDB3 in mode verify_swcd INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USMcu_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcu_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USResource_TS_T40D11" instead of "EB_TS_MOD_USResource_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USSafetyBase_TS_T40D" instead of "EB_TS_MOD_USSafetyBase_TS_T40D11M20I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USOs_TS_T40D11M40I2R" instead of "EB_TS_MOD_USOs_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USOs_TS_T40D11M40I2R" instead of "EB_TS_MOD_USOs_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USBaseNXP_TS_T40D11M" instead of "EB_TS_MOD_USBaseNXP_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USBaseNXP_TS_T40D11M" instead of "EB_TS_MOD_USBaseNXP_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USMcl_TS_T40D11M40I2" instead of "EB_TS_MOD_USMcl_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USSerdes_TS_T40D11M4" instead of "EB_TS_MOD_USSerdes_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USSerdes_TS_T40D11M4" instead of "EB_TS_MOD_USSerdes_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USEcuC_TS_T40D11M40I" instead of "EB_TS_MOD_USEcuC_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USSpi_TS_T40D11M40I2" instead of "EB_TS_MOD_USSpi_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USGpt_TS_T40D11M40I2" instead of "EB_TS_MOD_USGpt_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USEth_43_PFE_TS_T40D" instead of "EB_TS_MOD_USEth_43_PFE_TS_T40D11M14I0R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USPlatform_TS_T40D11" instead of "EB_TS_MOD_USPlatform_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USDem_TS_T40D11M40I2" instead of "EB_TS_MOD_USDem_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. INFO 24-12-03,16:49:20 (12145) Using a shortened feature name ("EB_TS_MOD_USPort_TS_T40D11M40I" instead of "EB_TS_MOD_USPort_TS_T40D11M40I2R0") for license check. WARNING 24-12-03,16:49:19 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1105Q/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:19 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110a/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:19 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiChannel/SpiChannel_SJA1110b/SpiChannelEcucPartitionRef" with value "" does not refer to nodes. WARNING 24-12-03,16:49:19 (1069) The node "/AUTOSAR/TOP-LEVEL-PACKAGES/Eth_1/ELEMENTS/Eth/EthConfigSet/EthCtrlConfig/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigEgressLastSchedulerRef" with value "ASPath:/Eth_1/Eth/EthConfigSet/EthCtrlConfig_2/EthCtrlConfigEgress/EthCtrlConfigScheduler_0" does not refer to nodes. INFO 24-12-03,16:49:20 (13030) Running generator "Mcu_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Mcu_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Resource_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Resource_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "SafetyBase_TS_T40D11M20I2R0_GeneratorId" in mode "verify_swcd" for module "SafetyBase_TS_T40D11M20I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Os_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Os_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "BaseNXP_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "BaseNXP_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Mcl_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Mcl_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Serdes_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Serdes_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "EcuC_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "EcuC_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Spi_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Spi_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Gpt_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Gpt_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Eth_43_PFE_TS_T40D11M14I0R0_GeneratorId" in mode "verify_swcd" for module "Eth_43_PFE_TS_T40D11M14I0R0" INFO 24-12-03,16:49:20 (13030) Running generator "Platform_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Platform_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Dem_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Dem_TS_T40D11M40I2R0" INFO 24-12-03,16:49:20 (13030) Running generator "Port_TS_T40D11M40I2R0_GeneratorId" in mode "verify_swcd" for module "Port_TS_T40D11M40I2R0" Errors "0" Warnings "4" AzureAD+XD@SF-XD /cygdrive/c/Users/XD/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0_test/example_application $ AzureAD+XD@SF-XD /cygdrive/c/Users/XD/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0_test/example_application $ make build CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c:54:10: fatal error: pfe_cfg.h: No such file or directory 54 | #include "pfe_cfg.h" | ^~~~~~~~~~~ compilation terminated. make: *** [Makefile:690: output_RDB3/Eth_43_PFE.o] Error 1 AzureAD+XD@SF-XD /cygdrive/c/Users/XD/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0_test/example_application $  Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello again @XD, After a closer look to the Release notes present on the PFE-DRV_S32G_M7_MCAL_1.4.0 directory, I notice that the RTD version I was using is incorrect. Although the Release notes indicate version 4.0.2, it needs to be an specific version: In FlexNet this translates to version S32 Real-Time Drivers Version 4.0.2, without any patch or hotfix. You can download the SW32G_RTD_4.4_4.0.2_D2306.exe extract the files in any convenient folder (avoid using the default C:/NXP/ to avoid multiple RTDs in S32DS) once extracted you can copy the files into the  C:/EB/tresos/plugins/ directory (first remove all the old drivers, they have the suffix ...TS_T40D11M40I2R0). now you should be able to run: make clean ; make generate ; make build without any problems.  Please let me know if this solved your problem. Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed hello @XD, can you share the output of the command "make generate"? To check if there are generation errors. As I mentioned, the files inside generate/ directories are not exactly header files , they are use to generate the header files with the same name, therefore you cannot include them in your makefile. Thanks Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , This issue occurred during the build process(make build). The pfe_cfg.h file is part of the MCAL 1.4.0 ZIP package and is located in the PFE-DRV_S32G_M7_MCAL_1.4.0\eclipse\plugins\Eth_43_PFE_TS_T40D11M14I0R0\generate\include folder. I’ve attached a screenshot and the folder structure of the ZIP file's plugins directory, which includes the generate and generate_swcd folders. The source file Eth_43_PFE.c references this header file on line 54, and it appears to be the only pfe_cfg.h file available. I modified the Makefile to include the path to the generate/include folder, but unfortunately, this file doesn’t seem to behave as a typical header file. I'm uncertain whether the Eth_43_PFE.c in your source code is expecting this same header file. This is missing head file $ make build mkdir -p output_RDB3 CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c:54:10: fatal error: pfe_cfg.h: No such file or directory 54 | #include "pfe_cfg.h" | ^~~~~~~~~~~ compilation terminated. make: *** [Makefile:691: output_RDB3/Eth_43_PFE.o] Error 1 this is after adding that header file $ make CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c In file included from C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c:54: C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/generate/include/pfe_cfg.h:25:1: error: expected identifier or '(' before '[' token 25 | [!NOCODE!][!// | ^ In file included from C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c:54: C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/generate/include/pfe_cfg.h:58: error: "PFE_CFG_SLAVE_HIF_MASTER_UP_TMOUT" redefined [-Werror] 58 | #define PFE_CFG_SLAVE_HIF_MASTER_UP_TMOUT ((uint32)0U) | C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/generate/include/pfe_cfg.h:56: note: this is the location of the previous definition 56 | #define PFE_CFG_SLAVE_HIF_MASTER_UP_TMOUT ((uint32)([!"num:i(EthGeneral/EthVendorSpecific/EthSlaveHifMasterUpTimeout)"!]U)) | C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/generate/include/pfe_cfg.h:63: error: "PFE_CFG_SLAVE_READ_EMAC_STAT_CNT_DIRECT" redefined [-Werror] 63 | #define PFE_CFG_SLAVE_READ_EMAC_STAT_CNT_DIRECT FALSE | C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/generate/include/pfe_cfg.h:61: note: this is the location of the previous definition 61 | #define PFE_CFG_SLAVE_READ_EMAC_STAT_CNT_DIRECT TRUE | C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/generate/include/pfe_cfg.h:82: error: "PFE_CFG_HIF_IRQ_ENABLED" redefined [-Werror] 82 | #define PFE_CFG_HIF_IRQ_ENABLED FALSE  Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD,  Does this problem occur when executing make generate or make build? if they occur when executing make build, the problem could be that there is a generation problem, files under .../generate/ directories are not exactly header files, as you can see in the pfe_cfg.h, they have a specific syntaxis . Those files are used to generate a proper header file, therefore if there is a problem when executing make generate you won't be able to execute make build correctly.  if the problem is present when using make generate, please share the output of the terminal so I can review the errors. Best regards Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , Thank you for your suggestions. Unfortunately, upgrading to RTD 5.0.0 is not an option for me, as it would prevent others from importing my project unless everyone upgrades to the same version. I have reviewed the missing file, and the header content appears to be abnormal. Below is a snippet of the pfe_cfg.h file located at: C:\NXP\SW32G_RTD_4.4_4.0.2\eclipse\plugins\Eth_43_PFE_TS_T40D11M14I0R0\generate\include. This file is required by: C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c. It seems that this file cannot be compiled as-is. Could you please check on your end if you are experiencing the same issue? A similar problem occurs with the header files in: C:\EB\tresos\plugins\BaseNXP_TS_T40D11M40I2R0\generate_PC\include\PlatformTypes.h. I’m unsure whether something in my file system has been corrupted. Your assistance in verifying this would be greatly appreciated. [!NOCODE!][!// [!INCLUDE "Eth_43_PFE_GetPfeParameters.m"!][!// Macros for hif interrupt [!ENDNOCODE!][!// /** * @file pfe_cfg.h * @brief PFE driver configuration file * @details This file needs to be included in all PFE sources before any other. * PFE include. It contains macros specifying: target hardware, target OS, * enabled features, and highlevel driver configuration. */ #ifndef PFE_CFG_H #define PFE_CFG_H /*================================================================================================== * FILE VERSION CHECK ==================================================================================================*/ #ifdef PFE_SRC_VERSION_CHECK #if (PFE_SRC_VERSION_CHECK != 43140440) #error "This header file was included from incompatible source file (different SW version)" #endif #else #define PFE_SRC_VERSION_CHECK 43140440 #endif #define PFE_CFG_TARGET_OS_AUTOSAR #define PFE_CFG_TARGET_ARCH_armv7le /* PFE_CFG_PFE_MASTER || PFE_CFG_PFE_SLAVE */ [!IF "EthGeneral/EthVendorSpecific/EthPfeMultiInstance = 'true' and EthGeneral/EthVendorSpecific/EthPfeSlaveMode = 'true'"!][!// #define PFE_CFG_PFE_SLAVE [!IF "node:exists(EthGeneral/EthVendorSpecific/EthSlaveHifMasterUpTimeout)"!][!// #define PFE_CFG_SLAVE_HIF_MASTER_UP_TMOUT ((uint32)([!"num:i(EthGeneral/EthVendorSpecific/EthSlaveHifMasterUpTimeout)"!]U)) [!ELSE!][!// #define PFE_CFG_SLAVE_HIF_MASTER_UP_TMOUT ((uint32)0U)  Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Thanks for helping again @GuilhermeS32G! about your description @XD, are you copying the files into workspace when importing the project? if so, please avoid doing it, as mentioned by @GuilhermeS32G, you should enter the folder of your project in the terminal and then generate and build in the same folder. It is not necessary to point to the S32DS plugins, I generally copy them to the tresos folder (as mentioned before) and it has the same effect, the important part is to correctly point them in the project_parameters.mk. Do any of the paths used in your project, either in the tresos installation or the project location, have spaces in the name? if so, please change the project location to one without spaces, this has caused me several problems in the past. Another suggestion I can give you is to use the latest version of the PFE MCAL driver and example, which is 1.5.0, this will require to use RTD 5.0.0, this version should cause less problems when generating and compiling. If you decide to follow this step, please consider that having more than one RTD version in S32DS is extremely problematic. You can install a new instance of S32DS in another folder, for example C:/NXP_2/, to avoid modifying your  current installation.  Let me know if the information I shared proved useful. Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @GuilhermeS32G , Thank you for your help again. I followed your instructions and modified the project_parameter.mk file to point PLUGINS_DIR to my RDT plugins. However, I encountered some issues again. The first issue was a missing 'EthIf_Cbk.h' file. I printed the $(INCLUDE_DIRS) from the Makefile and noticed that the EthIf_TS_T40D11M40I2R0 folder was not included. To resolve this, I manually added it to the include paths, which fixed the 'EthIf_Cbk.h' missing issue. INCLUDE_DIRS += $(PFE_INCLUDE_DIRS) \ $(GDIR)/include \ $(PLUGINS_DIR)/Mcl_$(AR_MCAL_PKG_NAME)/include \ $(PLUGINS_DIR)/EthTrcv_$(AR_MCAL_PKG_NAME)/include \ $(PLUGINS_DIR)/EthIf_$(AR_MCAL_PKG_NAME)/include \ $(PLUGINS_DIR)/BaseNXP_$(AR_MCAL_PKG_NAME)/header \ However, I then encountered another missing file: 'Tm.h'. This time, I couldn’t find the file anywhere—not in the RDT folder nor in the DS32 folder. Based on the source code, it appears to be related to AUTOSAR. I’m unsure if I am missing any additional packages that need to be pre-installed. CC C:/NXP/SW32G_RTD_4.4_4.0.2/eclipse/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/oal_time_autosar.c C:/NXP/SW32G_RTD_4.4_4.0.2/eclipse/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/oal_time_autosar.c:44:10: fatal error: Tm.h: No such file or directory 44 | #include "Tm.h" /* AUTOSAR Time Service */ | ^~~~~~ compilation terminated. make: *** [Makefile:692: output_RDB3/oal_time_autosar.o] Error 1 Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD , Try following these steps: After installing the EB Tresos Studio, download and install the RTD Drivers from AUTOSAR in the default installation folder (C:/NXP/SW32G_RTD_4.4_4.0.2_HF03). When prompted to provide the path to the EB Tresos, input the directory where EB Tresos have been installed. Check that in your EB Tresos installation path there is the file links/SW32G_RTD_4.4_4.0.2_HF03.link with content path=C:/NXP/SW32G_RTD_4.4_4.0.2_HF03​ Download the S32G PFE MCAL Driver compatible to your RTD drivers (in your case RTD 4.0.2 is compatible with PFE MCAL version 1.4.0) From the downloaded the .zip file, extract the folder eclipse/plugins/Eth_43_PFE_TS_T40D11M14I0R0 inside C:\NXP\SW32G_RTD_4.4_4.0.2_HF03\eclipse\plugins Also extract the example_application folder to a location that you find convenient. Import the example application into EB Tresos Studio and generate the project as described by @alejandro_e . Modify the project_parameters.mk file to reflect your current paths. For example: #The path to the compiler instalation dir GHS_DIR ?= c:/ghs/comp_202014 GCC_DIR ?= C:/NXP/S32DS.3.5/S32DS/build_tools/gcc_v9.2/gcc-9.2-arm32-eabi DIAB_DIR ?= c:/WindRiver/compilers/diab-7.0.3.0 #The path to the Tresos plugins directory TRESOS_DIR ?= C:/EB/tresos PLUGINS_DIR ?= C:/NXP/SW32G_RTD_4.4_4.0.2_HF03/eclipse/plugins TRESOS_WORKSPACE_DIR ?= $(TRESOS_DIR)/workspace FW_DIR ?= pfe_firmware LWIP_DIR ?= ../lwip Save the file with the modifications. Make sure you have the Make tool for Windows available from your CMD. Open a new command window and move inside the example_application folder. Run make HW=RDB3 and wait for the build. In my case, I had some issues with the Linker. Errors such as this one appeared: c:/nxp/s32ds.3.5/s32ds/build_tools/gcc_v9.2/gcc-9.2-arm32-eabi/bin/../lib/gcc/arm-none-eabi/9.2.0/../../../../arm-none-eabi/bin/real-ld.exe: output_RDB3/startup_cm7.o: in function `_core_loop': (.core_loop+0x0): multiple definition of `_core_loop'; output_RDB3/startup_cm7.o:(.core_loop+0x0): first defined here If it happens from your side, delete the contents of the files C:/NXP/SW32G_RTD_4.4_4.0.2_HF03/eclipse/plugins/Platform_TS_T40D11M40I2R0/startup/src/m7/gcc/startup_cm7.s and C:/NXP/SW32G_RTD_4.4_4.0.2_HF03/eclipse/plugins/Platform_TS_T40D11M40I2R0/startup/src/m7/gcc/Vector_Table.s Then run the build the command again. If everything goes well, the ELF file shall be generated inside the output_RDB3 folder. Best regards, Guilherme Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , Apologies for the delayed response; it was due to the holiday break. I had previously imported the project, but I decided to re-import it. After importing the project again, I encountered some errors during the "Verify Project" step, as shown in the attached screenshot. The errors primarily indicate missing parameters for the buildfile and failed generator runs for some modules. However, I double-checked and confirmed that the required modules are present in the EB plugins folder. These errors don't seem to affect the code generation process since I can generate the project without any issues. I then copied the generated files (including the include, output, and src folders) to the pfe_example_application folder. I also updated the project_parameters.mk file as you suggested, setting the path: FW_DIR ?= C:/Users/XD/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0/example_application/pfe_firmware. However, I still encountered a missing file error during compilation: $ make mkdir -p output_RDB3 CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c:54:10: fatal error: pfe_cfg.h: No such file or directory 54 | #include "pfe_cfg.h" | ^~~~~~~~~~~ compilation terminated. make: *** [Makefile:690: output_RDB3/Eth_43_PFE.o] Error 1 The missing file, pfe_cfg.h, is located at: C:\EB\tresos\plugins\Eth_43_PFE_TS_T40D11M14I0R0\generate\include. It seems to be an auto-generated header file, but the compiler is not including this path. Could you advise on how to resolve this issue? Thank you for your assistance. XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Have you imported the project into Tresos Studio before compiling in the terminal? Please import it as follows: File -> import Select "Browse..." Select the MasterProject_RDB3 Click finish (avoid selecting the "Copy projects into workspace" option): Now right click in the "someId" title, and select "Load Configuration": Now verify your project, after it finishes you should see no errors: Now generate the project: Now you can run make build in the project directory. Also please define the FW_DIR variable in the project_parameters.mk which should look something like the following: FW_DIR ?= C:/NXP/PFE-FW_S32G_1.7.0 Please let me know the result after using this method. Also, if you encounter problems of missing files, check if they were correctly copied into the tresos/plugins directory by running the command we have being using. Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , Thank you for looking into this issue. I wasn’t aware that all plugins from RTD needed to be copied to EB, as I didn’t see that step mentioned in the instructions. However, I have now completed that step and noticed some differences, but I am still encountering a missing file issue. This time, the compiler is reporting that "EthIf_Cbk.h" is missing. I’ve verified that this file exists in C:\NXP\SW32G_RTD_4.4_4.0.2\eclipse\plugins\EthIf_TS_T40D11M40I2R0, and I have already copied all plugins from RTD to EB. Did you encounter the same issue? Or any others changes I need to make in Makefile or project_parameters.mk to include the missing header file? $ make mkdir -p output_RDB3 CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE.c CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_43_PFE_Irq.c CC C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_PFE_LLD.c C:/EB/tresos/plugins/Eth_43_PFE_TS_T40D11M14I0R0/src/Eth_PFE_LLD.c:67:10: fatal error: EthIf_Cbk.h: No such file or directory 67 | #include "EthIf_Cbk.h" /* EthIf callbacks to be called from Eth driver */ | ^~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:690: output_RDB3/Eth_PFE_LLD.o] Error 1 Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD, Have you copied all RTD plugins from S32DS installation path to the Tresos installation path? Now that I checked again the paths in which you have the problematic. Using my paths as an example, this would mean: all files from: C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32XX_4_0_0\RTD Copied into: C:\EB\tresos\plugins Please not that depending on the module you may also need to copy the files from directories like: C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32XX_4_0_0\LLCE C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32XX_4_0_0\SEC_CRYPTO Let me know the result of the test. Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD, Sorry for de delay, I am also having trouble building the  application. I will reach out to the internal team an come with an update. I appreciate your patience. Best regards, Alejandro Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , Sure, the file is attached. The .mk file type is not supported, I change it to a txt file. Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD, Thanks for the information, can you share your project_paramters.mk file? Thanks  Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , Thank you for your response, no, I cannot find that file in the PFE project AzureAD@SF-X /cygdrive/c/Users/XiaodongHu/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0/example_application $ find . -name Mcl_Types.h AzureAD@SF-X /cygdrive/c/Users/XiaodongHu/Downloads/PFE-DRV_S32G_M7_MCAL_1.4.0/example_application Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD, Thanks for the information. Can you confirm that the file is present in your project folder? you can use the same method I mentioned before.  Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hi @alejandro_e , Thank you for your quick response and support; I really appreciate it. I can confirm that the Mcl_Types.h header file is present in both C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32XX_4_0_0\RTD\Mcl_TS_T40D11M40I2R0\include and C:\NXP\SW32G_RTD_4.4_4.0.2\eclipse\plugins\Mcl_TS_T40D11M40I2R0\include. However, according to the instructions and the README file, the build process requires running the make command in the 'PFE-DRV_S32G_M7_MCAL_1.4.0\example_application' directory using Cygwin. I am unsure how to include this header file in the build process. I suspect I may have missed something in the Makefile or project_parameters.mk files. Could you please advise? Thanks, XD Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Hello @XD it is good to support you again, My first recommendation is to check if the file is present in the respective installation folder, for example, in my computer it is in C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32XX_4_0_0\RTD\Mcl_TS_T40D11M40I2R0\include, if you are not sure of your installation path you can run this PowerShell command  in the C:\NXP\ directory and it will find the file path if exist, for example: PS C:\NXP> gci -r -fi Mcl_Types.h Directory: C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32XX_4_0_0\RTD\Mcl_TS_T40D11M40I2R0\include Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 11/10/2024 03:43 p. m. 14462 Mcl_Types.h If you are able to find the file please check that you have added the corresponding module in the peripherals view: After adding it you should update the code. If you cannot find the file with the PowerShell command mentioned please re install your RTDs and search for the file again. If nothing of the above solved the problem please send me a screenshot like the following, showing your include paths: Let me know if this information was useful. Re: S32G3 built PFE-DRV_S32G_M7_MCAL_1.4.0 example failed Add a screenshot of the make output after running make clean to avoid any confusion. PFE-DRV_S32G_M7_MCAL_1.4.0/example_application $ make mkdir -p output_RDB3 CC src/CDD_Mcl_Cfg.c In file included from src/CDD_Mcl_Cfg.c:39: include/CDD_Mcl_Cfg.h:41:10: fatal error: Mcl_Types.h: No such file or directory 41 | #include "Mcl_Types.h" | ^~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:690: output_RDB3/CDD_Mcl_Cfg.o] Error 1

S32K314のCPU周波数を下げる方法は? 親愛 なる 私たちのプロジェクトでは、S32K314のCPU動作周波数を元の160MHzから100MHzに変更する必要があります。この変更はどこで行うことができますか?さらに、CPU 周波数を下げるとどのような影響がありますか? ありがとうございます！

How to lower the CPU frequency of the S32K314? Dear Sir, We have a requirement in our project to change the CPU operating frequency of the S32K314 from the original 160MHz to 100MHz. Where can we make this change? Additionally, what are the impacts of reducing the CPU frequency? Thanks! Re: How to lower the CPU frequency of the S32K314? You can use multiple clock configuration in the S32DS. It is needed to keep clocking options as defined in device's RM Table 145. System clocking configurations

S32K3 prints system information via UART port Excuse me: S32K312 prints system information through the UART port. Is there a demo routine for using the Printf() function to print information?

S32K344 S32DS Opening the DMA module causes static variables not to be initialized Hi all!          In the S32DS development environment, the addition of the DMA RTD module caused the static variable to be incorrectly initialized and the value to be 0. The chip is not operating properly, and it is in HardFault_Handler.        Details are as follows: After DMA is configured, the content in the screenshot section of the added configuration file may cause this situation. It causes the static variable to have an initial state of 0 instead of an initial value, as follows:（Observe the variable before it is run and just entered debugging state） How to set up to avoid this situation?  Thanks very much！ Best Regards tian Re: S32K344 S32DS Opening the DMA module causes static variables not to be initialized Hi VaneB!      Many thanks for your replying.The problem has been solved。The ld file is not modified when SPD is transplanted，A conflict occurs after the DMA module is added。     Is there any reference document for SPD transplantation or related materials? The modification of ld file was ignored due to insufficient materials. Best Regards tian Re: S32K344 S32DS Opening the DMA module causes static variables not to be initialized Hi @_tian_10  Please test if you have the same behavior with any example that uses DMA. Also, there is the possibility that a wrong memory allocation is causing abnormal code execution, so please verify the linker file.  Re: S32K344 S32DS Opening the DMA module causes static variables not to be initialized Hi VaneB!  Thank you for your attention！   Today I did some careful debugging again and found some problems with the data and bss initializer functions.（init_data_bss）as follow： The function here is to load the initialization data in ROM into RAM, but at this time the ROM address content actually points to the RAM space, and the contents of the RAM address space are all 0. I don't know why this is the case, in the correct project the ROM address points to the ROM space, like the following: Look forward to your reply! Best Regards tian Re: S32K344 S32DS Opening the DMA module causes static variables not to be initialized Hi @_tian_10  Please provide more details about the situation. Also, if possible provide the steps to reproduce the issue.  B.R. VaneB

Configure MR-T1ETH8 with the SJA1110 ECT GUI Hi! Is it possible to build a firmware for the MR-T1ETH8 so that it could be configured from the SJA1110 ECT GUI? Best regards Daniel Re: Configure MR-T1ETH8 with the SJA1110 ECT GUI Ok, I'll contact our sales representative. Thanks for the help! Best regards Daniel Re: Configure MR-T1ETH8 with the SJA1110 ECT GUI Hello @Daniel_W , yes, that should be possible - MR-T1ETH8 has flash and 10-pin debug connector. ECT server needs to be added to your SJA1110's firmware. Since ECT is quite new tool, I would recommend contacting your assigned sales representative or field application engineer. Best regards, Pavel

Understanding the Reference Manual pinout/How to i2c Hello, I am trying to make a simple board with just the S32K341EHT0MPAST on it and some pins to access some analog and digital i/o and the i2c. However looking at the reference manual and it seems like every GPIO pin is extremely multifunctional? I'm a bit overwhelmed and I don't understand how you would set each pin to a specific function. There are so many "ALTx" columns. I see on the attached excel file for the s32k3 series that pin 41 and 42 are LPI2C1_SCL and LPI2C1_SDA respectively, and that there is another set of LPI2C0 pins. Do I understand correctly that I should be fine to use pin 41 and 42 as SDA and SCL and that the I2C0 is another "set" of i2c pins I could access? For simple digital and analog i/o I'm also a little lost, I see ADC_Sx as "standard input" pins available, but for digital would those be FXIO_Dx pins? Re: Understanding the Reference Manual pinout/How to i2c Hi @pb632146 Yes, you can look at each I2C[X] as a different instance for the communication module to use. There are some pins routed to these functions as alt mux that can be changed depending on what modules you may need. Inside the S32K3xx's datasheet you can find how many communication, analog and human-machine interfaces there are supported for the family. For example, you can find the figure map where each module is listed for the specific MCU derivative: For analog, there are up to three Analog Comparators (CMP) and up to three 12-bit Analog-to-Digital Converters (with up to 24 channel analog inputs). For digital, you can use GPIOs. The FlexIO module is a flexible input and output to emulate communication protocols, you can use this presentation as reference: Introduction to FlexIO. Best regards, Julián

code warrior floating license 注册license时提供的ip 有限制么，局域网ip可以么 Re: Code Warrior Floating License Is there any restriction on the IP provided when registering the license? Can the LAN IP be used? Thank you so much!! Re: Code Warrior Floating License Is there any restriction on the IP provided when registering the license? Can the LAN IP be used? Did any error messages pop up during the compilation process? If no error messages appear, there should be no problem. But if errors still appear, you'd better confirm with Jorge again, license-related issues, he is an expert and can give you more professional advice. Re: Code Warrior Floating License Is there any restriction on the IP provided when registering the license? Can the LAN IP be used? Thank you very much for your reply. I can now compile the code and build the target normally. Is there any hidden danger of compilation or license compliance in the compiled files? Re: code warrior floating license 注册license时提供的ip 有限制么，局域网ip可以么 Hi Jimmy Xu, 很抱歉你的问题还没有被解决。License支持哪一个版本，standard 还是 professional， 这取决于你购买时的选择。 Professional的功能是最全的，Standard功能会少一些。 老实说，CodeWarrior license 不是我的专业领域。我看到你还有一个private ticket， 已经有license team的support在跟进了。 希望 license team 的同事能够顺利解决你的问题，如有任何新的情况，请及时告知我们。 BRs， Celeste Re: Code Warrior Floating License Is there any restriction on the IP provided when registering the license? Can the LAN IP be used? Without starting the server, lincese shows two lines of error (network problem, I can't post the picture), combined with the previous results: the lower line is activated. Does the license only support the standard edition MCU 10.5 version, but not the professional edition MCU 10.5? Re: code warrior floating license 注册license时提供的ip 有限制么，局域网ip可以么 Hello JimmyXu, 我找到了下面的链接：Floating License -Environment Variables. - NXP Community 里面提到环境变量的设置，我不确定它是否与你遇到的问题有关，你可以试一下。 除此之外，你还可以尝试一下移除license，然后重新导入并重启codeWarrior，看看是否有效果。 BRs, Celeste Re: code warrior floating license 注册license时提供的ip 有限制么，局域网ip可以么 使用code warrior floating license，在官网生成license.dat后，在服务器上运行lmtools，服务正常启动。 client 使用和server相同的license.dat ，启动code warrior后报错 如何解决？ Re: code warrior floating license 注册license时提供的ip 有限制么，局域网ip可以么 Hello Jimmy, 我认为局域网是可以的，你可以尝试下。 BRs, Celeste Re: Code Warrior Floating License Is there any restriction on the IP provided when registering the license? Can the LAN IP be used? Pop-up window when opening code warrior Re: Code Warrior Floating License Is there any restriction on the IP provided when registering the license? Can the LAN IP be used? This is the picture

The image generated by the provisioning tool does not match, I did not see "FCFB ########################################################################################################## 生成构建脚本： build_image_lnx.sh 生成构建脚本： build_image_win.bat 生成构建脚本： build_image_mac.sh 正在执行脚本C:\Users\Administrator\secure_provisioning00\build_image_win.bat ###脚本： 构建镜像: C:\Users\Administrator\secure_provisioning00\build_image_win.bat Build HAB image nxpimage hab export -c "C:\Users\Administrator\secure_provisioning00\bd_files\imx_application_gen_win.bd"  -o "D:\RT1052_Example Code\Example\1.led_test\hello_world_boot.bin"  "C:\Users\Administrator\secure_provisioning00\source_images\hello_world.srec" Success. (HAB container: D:\RT1052_Example Code\Example\1.led_test\hello_world_boot.bin created.) nxpimage succeeded ### Build flashloader as unsigned bootable image ### nxpimage hab export -c "C:\Users\Administrator\secure_provisioning00\bd_files\unsigned_MIMXRT1050_flashloader_win.bd"  -o "C:\Users\Administrator\secure_provisioning00\bootable_images\unsigned_MIMXRT1050_flashloader.bin"  "C:\nxp\MCUX_Provi_v10\bin\_internal\data\targets\MIMXRT1050\flashloader.srec" Success. (HAB container: C:\Users\Administrator\secure_provisioning00\bootable_images\unsigned_MIMXRT1050_flashloader.bin created.) nxpimage succeeded ###脚本“构建镜像”的结果： 成功（返回代码= [0]成功） 操作的状态： 成功: 构建镜像 Re: The image generated by the provisioning tool does not match, I did not see "FCFB Indeed, this issue has been resolved. thank you. Re: The image generated by the provisioning tool does not match, I did not see "FCFB Hi, in your screenshot I can see the file name has "SDRAM" in it, but also in the screenshot the DCD is not configured, it might be the root cause why the application does not run. Regards, Libor Re: The image generated by the provisioning tool does not match, I did not see "FCFB Hi, may be the training video can help you. There should be all steps captured: Secure Boot on the i.MX RT10xx Crossover MCUs | NXP Semiconductors If you cannot find any information in the user guide, please let us know what information is missing. It is not possible to provide help without information: - what you want to do - what the problem is. Re: The image generated by the provisioning tool does not match, I did not see "FCFB Can't I run the LED program even after writing it in PROVISION TOOL? The image construction is incorrect. I can run it using KEIL's original image. Is it not possible to follow the official manual step by step? The documentation for this tool is not detailed enough. I can't use it. Re: The image generated by the provisioning tool does not match, I did not see "FCFB Hi, MCUXpresso Secure Provisioning tool does not generate the image with FCB, the FCB is written to flash as extra step. The FCB can be specified either as simplified or full configuration. Kindly review generated write script for details.

Minimum input voltage for edge capture Hi, In a KV4X, for a digital input, input voltage high is 0.7 x Vdd and input voltage low is 0.35 x Vdd. Which are the minimum and maximum values for edge capture? I have a sinusoidal signal of 200 mV peak in an input pin and I see that it is enough to detect falling/rising edges. Thanks in advance Re: Minimum input voltage for edge capture I have found why edges were being detected with such a low signal. Re: Minimum input voltage for edge capture Hi @zorrotz, Please maintain the edges of the captured signal between 0.7 x Vdd and 0.35 x Vdd in order to ensure a proper edge detection of the signal. Re: Minimum input voltage for edge capture I have forgotten to say that Vdd = 3.3 V

Find the Demo project of Pflash Hello, I want to use S32K311 to develop Bootloader, which involves PFlash erasing, writing, and bank switching. With the S32DS configuration tool, do you have related Demo projects? Can you share them with me？Thanks. Re: Find the Demo project of Pflash hello @CcW18, There are C40_IP and FLS MCAL RTD examples in S32DS IDE. Unfortunately, there are no examples specifically for S32K311. But still, you can refer to the examples and configure the drivers in your project accordingly. Regards, Daniel

How to build S32K3xx AutoSAR example project? Hello, I am trying to build an example project from SW32K3_S32M27x_RTD_4.4_4.0.0_P20_D2403. From its readme.txt, the build method to run "make build" from the command line. But there is video a few years ago which shows the way to use S32DS IDE to build AutoSAR example project for MPC574x MCU. https://www.nxp.com/video/introduction-to-nxp-autosar-mcal-software:AUTOSAR-OnDemand-Training-Video Is the way to use S32DS available for S32K3XX MCU? Thanks! Crane Re: How to build S32K3xx AutoSAR example project? I  downloaded the RTD and I didn't know how to find RTD head files. Now I solve the problem. Thank you Re: How to build S32K3xx AutoSAR example project? I am not sure if you have downloaded any RTD files before. For example, if you click the blue "S32K3 Standard Software Package" in the section 2.3 at this link https://www.nxp.com/document/guide/getting-started-with-the-s32k3x4evb-t172-evaluation-board-for-automotive-general-purpose:GS-S32K3X4EVB-T172?section=get-software, it will guide you to a page where you can find links to different versions of "Real Time Driver". This is for the MCU I have used before. There should be the similar page for the MCU you are using that you can find. Then you can look for the version of RTD that fit for your project on those pages. If you are asking for the specific version of RTD I used before, I don't remember any more. Hope it helps! Crane Re: How to build S32K3xx AutoSAR example project? Hello cranes, How to get RTD files， in my project I don't have the files so that I can't complie my project. Re: How to build S32K3xx AutoSAR example project? Hi, The issues is addressed and the project is built successfully by using command line. Thanks! Crane Re: How to build S32K3xx AutoSAR example project? Hello, It is from an example project. An example project, including EB config, from NXP's RTD, not a project I created myself.  Do you know who might know this? Or should I raise another question about this? Thanks! Crane Re: How to build S32K3xx AutoSAR example project? Hello, I do not have knowledge on your EB config, nor generated code. The package is defined in Resource plugin. Best regards, Peter Re: How to build S32K3xx AutoSAR example project? Hello, I found that the MCU model "S32K344" is not defined. This causes some symbols are not recognized. But this is supposed to be defined in the code generated from EB Tresos, right? I couldn't find why it is not defined in the S32K344 example project. Thanks! Crane Re: How to build S32K3xx AutoSAR example project? Hello, I personally always used GHS for code generated from EB Tresos. I will test it following days with S32DS and let you know if there are any special constraints. Best regards, Peter Re: How to build S32K3xx AutoSAR example project? Hello, Yes, that's correct. But if we look at the errors occur from the beginning as first a few in the below screenshot, which come from the files generated by EB Tresos and RTD, they are not relevant to this file. And actually adding check_example.h indeed doesn't remove any of these errors. Attached is the new build log file. At the end of the log file, there is "error: 'VV_RESULT_ADDRESS' undeclared". This macro 'VV_RESULT_ADDRESS' is in the Makefile in the example project folder. Do we need to add this file to the project generated in S32DS? If so, where to add? I already tried and it didn't work to add it in the project root folder as in the example project. Obviously it doesn't work to just copy the folders of include and src from the example project to the newly generated project in S32DS. There are many things missing, not just check_example.h. So, what is the correct way to build an example AutoSAR project from S32K3xx RTD? Just feel so weird that there is example projects in RTD but there are no guidelines about how to build the example project. What is missing here? Thanks! Crane  Re: How to build S32K3xx AutoSAR example project? Hello, I still see the same issue. You do not have all header files in the project: Best regards, Peter Re: How to build S32K3xx AutoSAR example project? Hello, Yes, it removed the previous errors, but still miss things as in the attached log. This project file structure is as below now: The RTD folder is copied from the non-AutoSAR example project for the same module. It seems that there possibly should be something else inside for AutoSAR project.  Thanks! Crane Re: How to build S32K3xx AutoSAR example project? Hello, As in any other compiler, you simply add paths for your header locations in include options: Best regards, Peter Re: How to build S32K3xx AutoSAR example project? Hello, Yes, I see that. But the issue is, I searched through the folder of the example project and files generated by EB Tresos, there are no such files. They are the files from RTD. Obviously, the example project needs the header files from RTD. Here is the file structure of an empty project created in S32DS. No RTD there, which is understandable. It can be built and run.  Here is the file structure of the example project with the files generated by EB Tresos. (include and src under generate are generated from EB Tresos.) There are no Mcl_Types.h and other header files that are needed. Then my question is, how to include RTD in the project so that the missing header files can be found by the compiler? Thanks! Crane Re: How to build S32K3xx AutoSAR example project? Hello, Your log says you are missing header files. Do you have those header file in your project? Best regards, Peter Re: How to build S32K3xx AutoSAR example project? Hello, I tried the way you mentioned. I create an empty project in S32DS, then move the folder of include and src in the example project to the empty project. It doesn't work and I got the build log as attached. Do you know who might know how to import the example project from the RTD for S32K3xx? What I am trying is an example project from the MCU's RTD package. There should be a guideline about how to build and test the example project. There is readme.txt in the example project folder, but unfortunately, it doesn't work to follow what's in it as described in my previous post. Thanks! Crane Re: How to build S32K3xx AutoSAR example project? Hello, My question is, is there a way to use S32DS to import an example project for S32K3xx MCU and build it? It doesn't work using the same way shown in the video as the example projects have a different project structure. I do not know if there is automatic import script in S32DS for tresos generated files. But you can always do it by hand. Simply create black project in S32DS and move the C and H files to the project. This way you should be able to compile project. In the past when there was no S32DS I was doing it this way with Windriver or GHS compilers. Best regards, Peter Re: How to build S32K3xx AutoSAR example project? Hello Peter, After 30 minutes of the video, it shows how to import an example project for MPC574x and build the project under S32DS.  My question is, is there a way to use S32DS to import an example project for S32K3xx MCU and build it? It doesn't work using the same way shown in the video as the example projects have a different project structure. In the readme.txt in the example project folder (C:\NXP\SW32K3_RTD_R21-11_3.0.0_P07\eclipse\plugins\Pwm_TS_T40D34M30I0R0\examples\EBT\S32K3XX\Pwm_example_S32K344, the file is attached), it shows how to build the project in Windows command prompt. (I tried but I couldn't make it work as it seems something is still missing). How can I import and build this project under S32DS as what's done in the video for MPC574 project? Thanks! Crane Re: How to build S32K3xx AutoSAR example project? Hello, I am bit confused here. The video shows EB Tresos configuration tool and how to generate project files. Those are later put into S32DS and compiled there.This is a common use case. Is the way to use S32DS available for S32K3XX MCU? I apologize, but I do not understand this question. Could you please specify it closer? Best regards, Peter

イーサネットスイッチSJA1105 SPIがデータを取得できません SJA 1105 SPIを使用してチップIDを取得すると、SDOのデータはSDIとまったく同じですが、その現象の原因は何ですか?

Is RTD 3.0.0 compatible DMA for FlexCAN I have configured and ran a example code for receiving CAN data through DMA it does not generating any receiving complete interrupt.  Re: Is RTD 3.0.0 compatible DMA for FlexCAN Hi, yes, can be aplicable. BR, Petr Re: Is RTD 3.0.0 compatible DMA for FlexCAN MPC57xx: Configuring and Using the eDMA Controller Is this application notes totally applicable for S32K322 also? Re: Is RTD 3.0.0 compatible DMA for FlexCAN Hi @PetrS  what is the difference b/w these both functions FlexCAN_Ip_RxFifo(INST_FLEXCAN_0,&recvBuff2); FlexCAN_Ip_Receive(INST_FLEXCAN_0, RX_MB_IDX, &rxData, false); and when I was reading the k3 reference manual it was not that much clear to me, Can you provide any simple document for understand the CAN DMA , message buffer usage, CAN ID filtering, CAN Interrupts, etc. Re: Is RTD 3.0.0 compatible DMA for FlexCAN Hi @PetrS  what is the difference b/w these both functions FlexCAN_Ip_RxFifo(INST_FLEXCAN_0,&recvBuff2); FlexCAN_Ip_Receive(INST_FLEXCAN_0, RX_MB_IDX, &rxData, false); Re: Is RTD 3.0.0 compatible DMA for FlexCAN Hi, yes it is. If you have some issue please share your simplified project, or refer to posted demos, e.g.  https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K312-CAN-Transmit-amp-Receive-Using-MB-amp-FIFO-DMA/ta-p/1789196 BR, Petr

S32K312 IIC DMA slave mode maximum receiving length can only be 8 bytes Hi all  I am using the DMA function of the IIC slave, but the maximum length that IIC can receive at once is only 8 bytes. Data exceeding 8 bytes cannot be retrieved from the buffer. I have uploaded the project, can you help me identify the problem. Thanks Re: S32K312 IIC DMA slave mode maximum receiving length can only be 8 bytes Thank you for your help. Although there is a problem with this routine, it can be used to compare the errors in my current project. I have identified the cause Re: S32K312 IIC DMA slave mode maximum receiving length can only be 8 bytes Hi @Reyna_pan45  I have observed that the project is based on the application provided in Example S32K312 I2C Transmit & Receive Using DMA DS3.5 RTD300. Just to confirm, if no modifications are made to the project, presents the same behavior? Re: S32K312 IIC DMA slave mode maximum receiving length can only be 8 bytes As you said ：The number of bytes that can be transmitted per transfer is not restricted. The received data length I set is 18 bytes ，Why can't I receive data exceeding 8 bytes？ Re: S32K312 IIC DMA slave mode maximum receiving length can only be 8 bytes Hi @Reyna_pan45  The I2C bus specification defines that each byte transmitted on the SDA line must be 8 bits long. The number of bytes that can be transmitted per transfer is not restricted. While the hardware itself does not impose a limit on the read transfer size, it requires the software to queue multiple read commands for larger transfers. Currently, the driver can receive between 1 and 256 bytes of data, and it can also be configured to discard received data instead of storing it in the receive FIFO. BR, VaneB