compile error when build bootloader, following AN13750

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

compile error when build bootloader, following AN13750

Jump to solution
1,310 Views
superyyf
Contributor II

Dear NXP,

I want to run the inter-core communication demo on the S32G_RDB3 development board, based on the AN13750 tutorial.
When I compile the bootloader I report the following error, I basically follow the same configuration steps as in the documentation, except for the part about modifying the bootloader source code.

In file included from C:/EB/tresos/workspace/Bootloader_S32G3XX_ASR_4.4_M7/output/include/CDD_Rm
_Cfg.h:46,
from C:/EB/tresos/workspace/Bootloader_S32G3XX_ASR_4.4_M7/output/src/CDD_Rm_Cfg
.c:43:
C:/EB/tresos/workspace/Bootloader_S32G3XX_ASR_4.4_M7/output/include/CDD_Rm_Ipw_Cfg.h:48:10: fata
l error: Xrdc_Ip_Types.h: No such file or directory
48 | #include "Xrdc_Ip_Types.h"
| ^~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:81: CDD_Rm_Cfg.o] Error 1

Some Version Information:

Integration_Reference_Examples_S32G3_2023_02

EB tresos 27.1

Please tell me how to clear these error message and continue building.

Thank you.

0 Kudos
Reply
1 Solution
1,284 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

The XRDC file been referenced under your error is related to the RM module, did you remove any reference to this module?

If so, did you delete the output folder prior to generating the project? This can also be a problem, where the output folder maintains non-updated files with old configurations.

Please, let us know.

View solution in original post

0 Kudos
Reply
4 Replies
1,285 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

The XRDC file been referenced under your error is related to the RM module, did you remove any reference to this module?

If so, did you delete the output folder prior to generating the project? This can also be a problem, where the output folder maintains non-updated files with old configurations.

Please, let us know.

0 Kudos
Reply
1,277 Views
superyyf
Contributor II

Thanks for the solution, it did work, the previous error disappeared after I deleted the output folder and then recompiled.
But when I unchecked two options as follows, I got the compilation error again.

superyyf_0-1698812978991.png

 

c:/NXP/Integration_Reference_Examples_S32G3_2023_02/code/framework/realtime/swc/bootloader/platforms/S32G3XX/src/Bootloader_Specific.c: In function 'Platform_ElevatedExecHandler':
c:/NXP/Integration_Reference_Examples_S32G3_2023_02/code/framework/realtime/swc/bootloader/platforms/S32G3XX/src/Bootloader_Specific.c:160:5: error: implicit declaration of function 'ASM_KEYWORD' [-Werror=implicit-function-declaration]
160 | ASM_KEYWORD("ldr r0, =currentCoreBootImageAddress");
| ^~~~~~~~~~~
c:/NXP/Integration_Reference_Examples_S32G3_2023_02/code/framework/realtime/swc/bootloader/platforms/S32G3XX/src/Bootloader_Specific.c: In function 'Bl_PreSetup':
c:/NXP/Integration_Reference_Examples_S32G3_2023_02/code/framework/realtime/swc/bootloader/platforms/S32G3XX/src/Bootloader_Specific.c:383:47: warning: unused parameter 'applicationConfig' [-Wunused-parameter]
383 | StatusType Bl_PreSetup(Bl_ApplicationDetails *applicationConfig)
| ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~
c:/NXP/Integration_Reference_Examples_S32G3_2023_02/code/framework/realtime/swc/bootloader/platforms/S32G3XX/src/Bootloader_Specific.c: In function 'Bl_EnablePartitionPeripheral':
c:/NXP/Integration_Reference_Examples_S32G3_2023_02/code/framework/realtime/swc/bootloader/platforms/S32G3XX/src/Bootloader_Specific.c:496:32: warning: comparison of integer expressions of different signedness: 'int' and 'long unsigned int' [-Wsign-compare]
496 | while ((1 << peripheralId) !=
| ^~
cc1.exe: some warnings being treated as errors
make: *** [Makefile:81: Bootloader_Specific.o] Error 1
0 Kudos
Reply
1,254 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

For the ASM_KEYWORD, this is related to disabling the Secure boot option:

"This is due to the header file  'Mcu.h' is missing when BL_CRYPTO_USED==OFF. After this is fixed, the bootloader can be compiled successfully."

We added the header directly into the Bootloader.c file and can proceed on this regard.

DanielAguirre_0-1698853986346.png

Please, let us know.

0 Kudos
Reply
1,239 Views
superyyf
Contributor II

Thanks Daniel-Aguirre, it works.

After i directly add Mcu.h to Bootloader_Specific.c (not Bootloader.c), the error disappear.

0 Kudos
Reply