Failed to build FreeRTOS using the new IDE MCUXpresso IDE v24.9.25 in Release configuration

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

Failed to build FreeRTOS using the new IDE MCUXpresso IDE v24.9.25 in Release configuration

1,259 Views
sushmasan
Contributor II

Hello Team,

I am wondering why FreeRTOS build is failing only in Release configuration, where as the build is successful with Debug configuration.

The same code worked fine in both Debug and release configuration with "MCUXpresso IDE v11.10.0_3148"

Any idea, what is different in the new IDE release compared to the last release?

Please find the FreeRTOS directory structure,

sushmasan_0-1732210315751.png       

  sushmasan_1-1732210364260.png      

sushmasan_2-1732210419141.png

Here is the error,

make -r -j16 all 
make[1]: *** No rule to make target '../freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/portasm.c', needed by 'freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/portasm.o'.  Stop.
Building file: ../freertos/freertos-kernel/portable/MemMang/heap_4.c
make[1]: *** Waiting for unfinished jobs....
Building file: ../freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/port.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -DCPU_LPC55S69JBD100 -DCPU_LPC55S69JBD100_cm33 -DCPU_LPC55S69JBD100_cm33_core0 -DSDK_OS_BAREMETAL -DSDK_DEBUGCONSOLE=1 -DCR_INTEGER_PRINTF -DPRINTF_FLOAT_ENABLE=0 -DSERIAL_PORT_TYPE_UART=1 -DSDK_OS_FREE_RTOS -D__MCUXPRESSO -D__USE_CMSIS -DNDEBUG -D__REDLIB__ -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\FreeRTOS_Lib\source" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\LPC55S69_Core\CMSIS" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\LPC55S69_Core\device" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\FreeRTOS_Lib\freertos\freertos-kernel\include" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\FreeRTOS_Lib\freertos\freertos-kernel\portable\GCC\ARM_CM33_NTZ\non_secure" -Os -fno-common -g -gdwarf-4 -Wall -c -ffunction-sections -fdata-sections -fno-builtin -fmacro-prefix-map="../freertos/freertos-kernel/portable/MemMang/"= -mcpu=cortex-m33 -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mthumb -D__REDLIB__ -fstack-usage -specs=redlib.specs -MMD -MP -MF"freertos/freertos-kernel/portable/MemMang/heap_4.d" -MT"freertos/freertos-kernel/portable/MemMang/heap_4.o" -MT"freertos/freertos-kernel/portable/MemMang/heap_4.d" -o "freertos/freertos-kernel/portable/MemMang/heap_4.o" "../freertos/freertos-kernel/portable/MemMang/heap_4.c"
Invoking: MCU C Compiler
arm-none-eabi-gcc -DCPU_LPC55S69JBD100 -DCPU_LPC55S69JBD100_cm33 -DCPU_LPC55S69JBD100_cm33_core0 -DSDK_OS_BAREMETAL -DSDK_DEBUGCONSOLE=1 -DCR_INTEGER_PRINTF -DPRINTF_FLOAT_ENABLE=0 -DSERIAL_PORT_TYPE_UART=1 -DSDK_OS_FREE_RTOS -D__MCUXPRESSO -D__USE_CMSIS -DNDEBUG -D__REDLIB__ -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\FreeRTOS_Lib\source" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\LPC55S69_Core\CMSIS" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\LPC55S69_Core\device" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\FreeRTOS_Lib\freertos\freertos-kernel\include" -I"C:\Test\CODE_WORKSPACE\21Nov2024_With_New_IDE\FreeRTOS_Lib\freertos\freertos-kernel\portable\GCC\ARM_CM33_NTZ\non_secure" -Os -fno-common -g -gdwarf-4 -Wall -c -ffunction-sections -fdata-sections -fno-builtin -fmacro-prefix-map="../freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/"= -mcpu=cortex-m33 -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mthumb -D__REDLIB__ -fstack-usage -specs=redlib.specs -MMD -MP -MF"freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/port.d" -MT"freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/port.o" -MT"freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/port.d" -o "freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/port.o" "../freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/port.c"
Finished building: ../freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/port.c
Finished building: ../freertos/freertos-kernel/portable/MemMang/heap_4.c

make: *** [makefile:37: all] Error 2
"make -r -j16 all" terminated with exit code 2. Build might be incomplete.

Regards,
San

0 Kudos
Reply
6 Replies

1,237 Views
Harry_Zhang
NXP Employee
NXP Employee

HI @sushmasan 

Base on the error, No rule to make target '../freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/portasm.c', needed by 'freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/portasm.o'.

The file may be missing or the path is incorrectly specified in the build configuration for the Release build.

BR

Harry

0 Kudos
Reply

1,230 Views
sushmasan
Contributor II

Hi @Harry_Zhang ,

I think you might have seen my comment, debug configuration build is working only release configuration build is failing.

If the file is not present, then build has to fail with debug configuration build also.

Please find the FreeRTOS and LPC55S69 core for your reference.

I just created a workspace with new IDE version and exported the Free RTOS and LPC55S69 core and build it. Only Free RTOS is failed to build that too on Release build configuration only.

Regards,
San

0 Kudos
Reply

1,202 Views
Harry_Zhang
NXP Employee
NXP Employee

Hi @sushmasan 

Harry_Zhang_0-1732615323940.png

I tested your project.

Debug and Release are no issue.

BR

Harry

0 Kudos
Reply

1,193 Views
sushmasan
Contributor II

Hi @Harry_Zhang ,

Were you able to build FreeRTOS in Release configuration using IDE version v24.9.25?

Because in your snapshot I saw LPC55s69_Core component build details.
The issue I am seeing is only with FreeRTOS component, that too in Release configuration.

Regards,

San

0 Kudos
Reply

1,154 Views
Harry_Zhang
NXP Employee
NXP Employee

Hi @sushmasan 

I just build your attached using IDE version v24.9.25.

"Were you able to build FreeRTOS in Release configuration using IDE version v24.9.25?"

Should i  create a new FreeRTOS project using IDE version v24.9.25 and build it?

BR

Harry

0 Kudos
Reply

1,075 Views
sushmasan
Contributor II

Hi @Harry_Zhang ,

You don't need to create a new FreeRTOS project.

But I am wondering why in my workspace only the Release configuration is failing.

I even tried creating a new workspace, but still the same issue is seen.

Regards,
San

0 Kudos
Reply