S32K146费用问题 大家好，团队。我目前正在开发一个使用 S32K146 的项目。我在使用 EB tresos 配置 FEE 模块时遇到了一些问题。您能否提供一些答案或建议？ 如图所示， Fee Block Size和F ee Virtual Page Size之间是什么关系？ 当我将费用虚拟页面大小配置为 8 或 32 时，只有当费用块大小小于或等于 32 时，我才能通过 Fee_Read() 函数检索所需的数据。例如，如果我将Fee Block Size设置为 64（大于 32 的值）并将Fee Virtual Page Size设置为 32，则我无法将数据写入 D-flash，因此也无法读取数据。如果我想将费用块大小设置为 200，我该怎么做？ 感谢您的回复。感谢您的帮助。 回复：S32K146费用问题 嗨，Lukas。现在我可以实现 FEE 功能了，因为我可以直接读出来而不需要等待它写完。你的建议很有帮助。谢谢！ 回复：S32K146费用问题 你好，卢卡斯！谢谢你的回复， 我复制了官方例子提供的读写函数到我的项目中使用，如你的截图所示。S32K146中一个扇区的大小为0x1000。我可以这样理解吗：“Fee Block Size”是用户定义的块大小，其最大值应小于0x1000？这是我的函数调用截图：

K144在ESD测试中卡住了 客户工程师在做ESD测试，外部设备卡死，板子上的硬件复位无法正常复位，需要重新上电才能正常工作。输出接口接了TVS管，请问MCU是否做了保护，无法硬件复位？谢谢！

Questions about flash_partitioning_s32k118 demo code In this demo project after the FLASH_DRV_SerFlexRamFunction function call the FLASH_DRV_EraseSector, FLASH_DRV_VerifySection, FLASH_DRV_Program and FLASH_DRV_ProgramCheck functions are called. What is the purpose of those function calls in this demo project? As my understanding a new value written to the  FlexRAM(by calling FLASH_DRV_EEEWrite function) will automatically generate a new record in the FlexNVM. Are those function calls for demostration purpose or necessary to make EEE function work? - Bruce Re: Questions about flash_partitioning_s32k118 demo code Hi@bjs Yes, those functions just for demostration purpose.

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

S32K1 FreeRTOS 10.5.1 version 2.0.0 を探しています。 S32K1 FreeRTOS 10.5.1 バージョン 2.0.0 を探しています どこにありますか? 日時:S32K1 FreeRTOS 10.5.1バージョン2.0.0を探しています。 ありがとうございます。 見つけました。

LIN通信用の内部または外部発振器 S32K144の内部発振器はLIN 2.0通信に十分ですか、それとも信頼性の高い性能を得るためには外部発振器を使用する必要がありますか? Re:LIN通信用の内部または外部発振器 Hi@ブリッジブランチ あなたはこの答えを見ることができます、 https://electronics.stackexchange.com/questions/507001/bit-error-rate-calculation-for-lin-protocol

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

Problems when changing OCRAM size in Property settings? Hi, I'm using MCUXpress IDE with the MIMXRT1010-EVK. I want to increase the size of the OCRAM. The ITCM and DTCM can be somewhat smaller. I did fill in new sizes in the Properties of the project at C/C++ Build -> MCU Settings. But the application crashes or values are not accepted. See the attached picture. The top-left MCU-settings in the picture are the original setting. I decreased the ITCM and DTCM sizes and increase the OCRAM as in the top-right settings in the picture. The compiler/linker seems to accept this but when running the application, it crashes. The function HardFault_Handler(void) is called even before the first breakpoint in main. Note that I decreased the RAM3 base address because it may not overlap RAM4. And increasing the RAM4 base address results in the error that the size is 0! See bottom-left in the picture. the strange thing is that the size of RAM4 originally was also 0! As a test I decreased the ITCM and DTCM sizes without increasing the OCRAM so that no overlap exists. See bottom-right in the picture. This is accepted by the compiler/linker and the code runs. But off course I want to increase the OCRAM size with 0x8000. How to do this??? i.MXRT 101x 回复： Problems when changing OCRAM size in Property settings? PS: Sorry for my oversight, since it has to be an integer power of 2, then 96KB is also not supported, so there is only one option, 128-0-0KB. 回复： Problems when changing OCRAM size in Property settings? Hi, Thanks for your interest in NXP MIMXRT series! NXP provides a detailed AN to guide this operation, please refer to it.  https://www.nxp.com/docs/en/application-note/AN12077.pdf There are a few notes in it, firstly, since the size of the TCM must be an integer power of 2 and the OCRAM must be greater than 64KB. then, if you want to increase the OCRAM, there must be at least one TCM that has a value of 0. Therefore, please choose the configuration that is right for you from the following three options. Also, if there is a TCM that needs to be 0, then it must be noted: If the requested ITCM/DTCM size is 0 Bytes, disable the corresponding TCM in IOMUXC_GPR_GPR16->INIT_xTCM_EN before configuring the size to 0 Bytes in IOMUXC_GPR_GPR14->CM7_CFGxTCMSZ. For a more specific guide, see also this post, which is a good place to start: Reallocating the FlexRAM - NXP Community Best regards, Gavin

I2C In the IMXRT 1170, we attempt to verify using i2c example code for the CM7 polling method by flashing the board directly, for instance, but with specific Cfg SDL, SDA pins on the J26 port. not receiving the clock-out signal. I alter the pins, such as J 10 and J 09, which are cfg in the example i2c code. We are still unable to obtain a clock signal after compilation. Now , I checked with IMXRT 1160, we get Clock Signal SCL from i2c Example code, but not get signal from data SDA Re: I2C Hi @sabesh , Thanks for your interest in NXP MMXRT series! If your question is solved, please tell me to close this case, and Accept as Solution. thanks. Wish you a nice day! BR mayliu Re: I2C Hi @sabesh , Thank you so much for your interest in our products and for using our community. If you use MIMXRT1170-EVKB board, you can use LPI2C1_SCL J26-12 and LPI2C1_SDA J26-10. Please pay attention that  In the hardware circuit, SCL and SDA must be connected to pull-up resistors, Software SCL and SDA need set as open drain mode and Software Input On Enabled . Please refer to the next Fig. In I2C communication, there are one master and multiple slaves. The master I2C device generates the clock signal. So I suggest you import a SDK demo about I2C master, For example "evkbmimxrt1170_lpi2c_edma_b2b_transfer_master_cm7". If you want I2C communication run okay, Please connect a I2C slave board. So I suggest you use two board, one is as I2C master, one is as I2C slave. Wish it helps you. If you still have question about it, please kindly let me know. Best Regards mayliu

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?

i.MX RT1180 是否支持 IEEE802.1QCR？ i.MX RT1180 是否支持 IEEE802.1QCR？ 我在 i.MX RT1180 上没有找到任何用于 TSN 的 802.1QCR。 所以我想再确认一下。 谢谢。

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

GD3162ゲートドライバ こんにちはNXPの、 DESAT_LED(リーディングエッジブランキング時間)とDESATフィルタ時間の違いを明確にしてください。DESA_LEBがVdsがオンになるプログラム可能な時間を指すようにするためですか?

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

GD3162 gate driver SC fault Hi NXP, What could be the reason that INTB is going to 2.5V from 5V in the case of a short circuit fault ? Can there be any causes in SW? Any possibility ? Re: GD3162 gate driver SC fault Hello Could you please let me know the result? Additionally, would you be able to test the INTB connected directly to the microcontroller? Re: GD3162 gate driver SC fault And also, INTB before connecting to micro is externally given a pull-up to 5V through a 10K resistor Re: GD3162 gate driver SC fault Hi, FYI, in our project, all the INTB pins are connected to one pin of the micro so that if any one of the gate drivers (6 gate (RH, YH, BH and RL, YL, BL) for 3 phase motor) encounters a fault, the PWM is cut off for all. In the attached image you can see that ISENSE pin of the R-L gate driver is supposed to detect phase over current cut off through SC fault and ISEN of Y-L gate driver is supposed to detect DC over current cut off through SC fault. In our case whenever ISEN of YL detects DC bus over current cut off, in that case INTB is going to 2.5V and when phase over current cut off occurs, then INTB is further transitioning from 2.5 to 0. I've noted your point to disconnect INTB from micro and check the signal again. Re: GD3162 gate driver SC fault Hello, Is the INTB pin directly connected to the microcontroller? Please note that the INTB pin has an internal passive pull-up to VDD, and INTB reports faults with an active low signal (logic 0 indicates a fault). According to the datasheet, the INTB pin should indeed be connected directly to the microcontroller. Could you confirm whether, when disconnecting the microcontroller from the INTB pin, the voltage remains at 2.5V in the event of a fault?

リンカスクリプトの作成中にエラーが発生しました 親愛なる皆様へ 最近MCUXpresso v11.10.0に更新され、RT1024 EVKにSDK 2.15を使用しているため、FlexRAMを異なるサイズに再設定して外部RAMを削除しようとしましたが、添付の画像のようなエラーが表示されます。私はリンク https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/Reallocating-the-FlexRAM/ta-p/1117649 をたどろうとしています、そしてそれはSDK 2.12とIDE v11.8の以前のバージョンで私のために働いた。何か変更が加えられ、機能しなくなったのですか? 敬具 ピング     Re:リンカスクリプトの作成中にエラーが発生しました こんにちは@ping1 , 更新情報をいただきありがとうございます。 申し訳ございませんが、 NXP の 最新の ポリシー により 、 お客様 に直接 コード を送信する ことはできません 。 NXP AN12077および https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/Reallocating-the-FlexRAM/ta-p/1117649 を参照することをお勧めします。 あなたの最初の質問はリンカスクリプトの作成中のエラーについてだと思います、そして今あなたは正常にコンパイルすることができます、そしてあなたはあなたのプロジェクトの開発を続けたいと思っています、そうですか? プロジェクトが実際に外部SRAMを使用していることを確認し、HW設計に基づいてプロジェクトを開発してください。 Board_ConfigMPU設定に関しては、私はあなたのためにテストを行っただけで、MPUは設定しませんでした。あなたの実際のプロジェクトに基づいてMPUを設定してください、あなたは私があなたに投稿するリンクを参照することができます。 よろしくお願いいたします メイリュウ Re:リンカスクリプトの作成中にエラーが発生しました こんにちは、5月 FlexRAM サイズを再構成するだけでなく、ターゲット ボードに外部 SRAM がないため、外部 SRAM も削除しましたが、問題を引き起こしますか?それは私が~3年前に問題なくやっていたことです。外部RAMが主に使用されていることに気づき、後でそれを下に移動したので、代わりに内部RAMが使用されています。今のところは問題ないようですが、DTCサイズを128Kに再構成しようとはまだしていません。それを行うにはBoard_ConfigMPU()を変更する必要がありますが、あなたもそれをしましたか?あなたが私にあなたの修正したプロジェクトを送ってくれるなら、私は何が間違っていたのかをチェックできるでしょう。 敬具 ピング Re:リンカスクリプトの作成中にエラーが発生しました こんにちは、5月 あなたがしたのと同じようにダウンロードしてインストールしました - 両方のv24.12、それはあなたが言ったようにHello freertosの例で動作しますが、私がlwip_mqtt_freertos例に同じことを行うと、同じエラーが再び現れました。 緊急の助けが必要です pls 敬具 ピング Re:リンカスクリプトの作成中にエラーが発生しました ありがとう、メイ 私はIDEのいくつかのバージョンをインストールしていますが、リンカスクリプトを使用しようとすると、ロード時にどれを使用するかわかりません。 IDEv24 と SDK v24 も試してみます。 ピン Re:リンカスクリプトの作成中にエラーが発生しました 私は最初にそれを行い、v24.xxに問題があると言われたので、v11.10にロールバックしました。ところで、RT1024_connect.scpはどこにありますか? ピング Re:リンカスクリプトの作成中にエラーが発生しました こんにちは、5月 古いバージョンのSDK(2.12)とIDE(11.6)にロールバックしましたreadmeファイルによると、問題は残っています、私は問題に私の知恵を使い果たしています、それはおそらくIDEとSDKの以前のバージョンで私の他のプロジェクトの初期の段階で前に働いた。後で変更したものが何であれ、バグが発生する可能性がありますが、私が変更したことの1つは、現在freeRTOSを使用しようとしていることです。 ところで、IDE v11.10とRT1064用のSDK 2.16を使用すると、動作します。しかし、今のところ、RT1024を使用する必要があります。 敬具 ピング Re:リンカスクリプトの作成中にエラーが発生しました こんにちは、5月 SDKv2.15を使用しようとしていますが、そのためにどのIDEバージョンを使用すればよいですか? 敬具 ピング Re:リンカスクリプトの作成中にエラーが発生しました こんにちは、5月 返信ありがとうございます。 新製品を開発しており、新しいSDKとIDEバージョンを使用したいと考えています。v2.15 SDKをインストールしたばかりですが、最小IDEはv11.8であり、下位互換性があるため、それ以上のものはそれで動作するはずだと思いました。そうなんですか。 敬具 ピング

PCA9515A evaluation environment I can't find the PCA9515A EVK, but is it possible to replace the PCA9515ADP with the PCA9617ADP-ARD (URL below) and evaluate it? If there are any points to note, would you let me know? https://www.nxp.jp/design/design-center/development-boards-and-designs/analog-toolbox/arduino-shields-solutions/pca9617adp-ard-arduino-shield-level-translating-fm-plus-ic-bus-repeater-evaluation-board:PCA9617ADP-ARD Re: PCA9515A evaluation environment Hi Jozef, Thank you very much for your kind reply. My question was solved. Best regards, Bata Re: PCA9515A evaluation environment Dear Kawabata-san, the PCA9617A is more advanced, than the PCA9515, although these two are very similar. But what will work on the PCA9617A, might not work on the PCA9515. Yes, I would recommend you to use the PCA9617ADP-ARD, but then please consider also use the PCA9617A for your application.  With Best Regards, Jozef

where to find S32S info Hello, In the link below https://www.nxp.com/docs/en/white-paper/GREENBOX2WPA4.pdf it shows "S32S" but from the list of "S32 Automotive Platform Processing Products" in below page https://www.nxp.com/products/processors-and-microcontrollers/s32-automotive-platform:S32 I cannot find any link or word about S32S. Do we have a chip named S32S or it is just a collection of S32 family, i.e a plural of S32?? Thanks Re: where to find S32S info Hi, What we are referring to is that links available under nxp.com related to S32S will redirect to S32Z, similar to the one shown below (which was the S32S product page under NXP): https://www.nxp.com/S32S Please, let us know. Re: where to find S32S info Hello, Thanks for the finding. However can you specify which one can redirect to S32Z/E? For example, I cannot see below "S32S" is same as "all S32S links do redirect to the S32Z/E products...." Thanks Re: where to find S32S info Hi, We can confirm that, under the documentation you have provided and manual searching from our side, all S32S links do redirect to the S32Z/E products. Please, let us know. Re: where to find S32S info Can you help confirm "S32S2 microcontrollers are redirected to the S32Z or E family products" So I can further know who I should contact. Re: where to find S32S info Hi, Seems to be that all information regarding S32S2 microcontrollers are redirected to the S32Z/E family products. For more information on regards of the latter, help us contacting your local NXP FAE/DFAE/representative, since at this moment all documentation is under control of distribution. Please, let us know.

NTAG I2C Pass-through with CLRC663 I am trying to test passthrough mode using NTAG-I2C+ dev kit for Arduino (OM23221ARD) to a CLRC663 reader running the SW297859 SDK, but have been unable to get any data written from the CLRC663 to the NTAG's SRAM buffer in passthrough. I've run the NfcrdlibEx9_NTagI2C example in SW297859 and this confirms that pass through is enabled on the NTAG. I've tried updating this block (see attached) to perform an ISO14443 exchange with the NTAG but the SRAM_I2C_READY of the NS_REG never gets set and if I dump the SRAM I don't see anything written. On the CLRC663 side I get a 0x201 error which looks like a timeout on waiting for a response (which makes sense since I don't currently have the NTAG sending anything back until the SRAM_I2C_READY gets set). Attached is the code change that I made. Can someone please point me the correct direction for performing an ISO14443 exchange with the NTAG? Or is it even possible to perform passthrough exchanges with the CLRC663 running SW297859 SDK since it doesn't support P2P? NFC Frontend Solutions Re: NTAG I2C Pass-through with CLRC663 Hi Fabian, Thanks for your help on this. We got bi-directional communication working with the fast-write commands using the CLRC663 and an Arduino connected to the NTAG. Attached are the code snippets that might save someone else some time in the future. Jeremy Re: NTAG I2C Pass-through with CLRC663 Hello sir, I believe this snippet from the Example may be helpful. Even if the implementation isn't for Pass-through. Unfortunately, as I mentioned we don't have an implementation at this moment as an example to share. My apologies for this. If you could please try using the Mful_fastRead() and the sector select. Which in this case would be sector 0. If you are having issues with the implementation please do not hesitate to share it with us to provide further support. Re: NTAG I2C Pass-through with CLRC663 I don't thing there is any issue with my configuration of the NTAG since I can see it working using the NXP Android reference app when I write to the NTAG then read back over I2C. I believe there is something I am missing on the CLRC663 side of things. I have tried phalMful_FastWrite() without success. Could you provide reference code of using phalMful_FastWrite() that I could use as a starting point? Re: NTAG I2C Pass-through with CLRC663 Hello sir, Unfortunately, we don't have the specific implementation using phpalI14443p4_Exchange() since the implementation in the Ex9_NTagI2C example is using the MIFARE Ultralight API for performing T2T interfacing, we recommend please adopt this practice as well. As recommended in the Datasheet, please use the FastRead command. The MfUl does have this function as: phalMful_FastRead() I'm sure you already have checked SW3647 and SW3648. But in SW3647, NTAG_I2C_Explorer_Demo is shown in CopyInterruptToSRAM() how we recommend copying the data into the SRAM for the CLRC663 to be able to read the passed values. In SW3648, there is a file called Ntag_I2C_Demo which shows the implementation for reading into the SRAM. It is required to check if the SRAM is ready before starting to read the actual memory since it could be blocked from the NFC side. I hope this information may be useful sir. Re: NTAG I2C Pass-through with CLRC663 I can get passthrough working using the NXP sample app for Android (not for iOS) so this implies the NC_REG is set correctly on the NTAG side. What I can't get working is the CLRC663 writing to NTAG via passthrough. void enablePassThroughRFToI2C() { // From NFC SDK // NTAG_SetTransferDir(ntagCoreStateHandle.ntagDriverHandle, RF_TO_I2C); { // ntag.writeRegister(Ntag::NC_REG, NTAG_NC_REG_MASK_PTHRU_ON_OFF, 0); ntag.writeRegister(Ntag::NC_REG, NTAG_NC_REG_MASK_TRANSFER_DIR, RF_TO_I2C); ntag.writeRegister(Ntag::NC_REG, NTAG_NC_REG_MASK_PTHRU_ON_OFF, 0x40); } For the CLRC663, as seen in the previous code snippet, I am prepending the APDU with: uint8_t writeSRAMCmd[] = {0xA6, 0xF0, 0xFF}; // Fast write to Start address of the SRAM block ..but this is not working. Could you provide sample code snippet for CLRC663 writing to the NTAG SRAM buffer? Re: NTAG I2C Pass-through with CLRC663 Hello sir, Thank you for sharing this code snippet. In order to implement the RF -> I2C writing, it is required to first serve the correct direction, and the FD pin in NC_REG. Please share this register configuration to double-check if this is correct. Please keep in mind that this configuration has to be done through I2C. The implementation of the start and end addresses looks good. I believe that the issue is with the register configurations, sir. Could you please check NC_REG values while in session? It is recommended to please implement a CRC when writing to the SRAM directly. Re: NTAG I2C Pass-through with CLRC663 I have tried variations of this with no success. For reference on the NTAG is powered from VCC and I can see data get written to SRAM successfully when using the Android NTAG I2C app so I believe my issue is isolated to what I am doing on the CLRC663. I am using the `./SW297859/Examples/NfcrdlibEx9_NTagI2C` example with the only change to the if block that deals with an NTAG in passthrough: /* check for Pass-through mode */ if ((bDataBuffer[0] & PTHRU_ON_OFF)) { LOG_DEBUG("Writing to NTAG"); uint8_t writeSRAMCmd[] = {0xA6, 0xF0, 0xFF}; // Fast right to Start address of the SRAM block uint8_t dataToWrite[] = {0xDE, 0xAD, 0xBE, 0xEF}; // Example data uint8_t sramWrite[sizeof(writeSRAMCmd) + sizeof(dataToWrite)]; memcpy(sramWrite, writeSRAMCmd, sizeof(writeSRAMCmd)); memcpy(sramWrite + sizeof(writeSRAMCmd), dataToWrite, sizeof(dataToWrite)); status = phpalI14443p4_Exchange(pHal, PH_EXCHANGE_DEFAULT, sramWrite, sizeof(sramWrite), NULL, 0); CHECK_STATUS(status); From the log statement I can see that we attempt to write something, but nothing shows up on the NTAG. I have tried manually appending a CRC as well as writing a full 64 bytes, but have been unable to get anything written. Could you give sample code of how I can write anything to the SRAM buffer? Re: NTAG I2C Pass-through with CLRC663 Hello sir, Yes the CLRC663 does support Ntag I2C passthrough. The issue is that the example from the NFC Reader Library is only, reading specific pages of the NTAG I2C. Once the passthrough is enabled in the NTAGI2C, the CLRC663 needs to read directly to sector 0, page address 0xF0. As mentioned in section 11.3.1 the use of Fast Read commands are recommended. Please keep in mind that both interfaces cannot be accessed at the same time and the status registers need to be implemented in your application using NS_REG. Also, keep in mind that in order to access SRAM is required to power on the device via VCC Unfortunately, we don't have a specific implementation for this in the Library examples. If you could please share your application output and/or implementation. We may be able to provide further help. Re: NTAG I2C Pass-through with CLRC663 Yes, I have looked at AN11579 and can get pass through working between the demo phone app and NTAG but not when using the CLRC663 as the Reader. It would be very helpful if you could tell if the CLRC663 is capable of pass through communications with NTAG I2C Plus to begin with? Re: NTAG I2C Pass-through with CLRC663 Hello, my name is Fabian, I've been assigned to support your case. Thank you for your interest in our products I'm not sure if you have already checked AN11579 is explains the respective configurations and some Block communications schemes for data transfer depending on the requirements of your project. At this point, it is difficult to detect what is wrong with your setup. Please help us by trying to follow the mentioned schemes and let us know if you are still having issues.  Please keep in mind that is very important to configure FD_ON and FD_OFF and get it's status while in session to correctly access the IC through the interfaces. Please let me know if this information is helpful.

[iMX8M Nano] Using General Purpose Timer (GPT) to Count the external Signal Pulses Question:  What is the maximum rising time of external GPT_CLOCK signal? The Problem: We are using iMX8 Nano CPU…We want to use GPT TIMER to count the pulse of external signal…we configure UART3_TXD pad (D18) as GPT1_CLK function and connect our external clock to this pin. We can see the GPT Counter count this signal. However, this only works with simulated signal with rising time about 50ns (see the below picture). When we inject the real signal with rising time about 250ns…the GPT does not count. I use devmem2 tool to access the register directly as below: Set Custom Pin (0x30330248) as GPT1_CLOCK: 0x00000003 Set Clk Select (0x303305E8) to select external clock which is GPT1_CLK: 0x00000001 Set counter mode via Control Reg (0x302D0000): 0x000000C3 Read the Counter value via Count (0x302D0024) Compare the two rising edges of the two signal pulses The Green Line is the simulated signal The Mint Blue is the real signal i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Linux Yocto Project Re: [iMX8M Nano] Using General Purpose Timer (GPT) to Count the external Signal Pulses Hello @Coeus412  Please be sure that this condition is achaiving: The GPT counter can be operated using an external clock from outside the device, and this is the input pin used for that purpose. The external clock input (GPT_CLK) is treated as asynchronous to the peripheral clock (ipg_clk). To ensure proper operations of GPT, the external clock input frequency should be less than 1/4 of frequency of the peripheral clock (ipg_clk). Hysteresis characteristics on this pad will be required because this is a clock input. (From reference manual 12.1.2.1 External Clock Input) Best regards, Salas. Re: [iMX8M Nano] Using General Purpose Timer (GPT) to Count the external Signal Pulses I notice when we use the simulated signal generated by another GPIO of IMX8 the GPT Counter can count correctly (even though the rising time 250ns same as real signal) …but it does not count the real signal. I am checking the datasheet and found below block diagram (there is Sync block with ipg_clk). Does it mean the external GPT_CLK signal need to synchronize with ipg_clk?