LPC MicrocontrollersのトピックFreeRTOS build failure in Release configuration (MCUXpresso IDE v24.9.25)

FreeRTOS build failure in Release configuration (MCUXpresso IDE v24.9.25)

sushmasan — Thu, 05 Dec 2024 14:50:34 GMT

Hello Team,

Can someone please help me what might cause FREERTOS component to fail only in release configuration?

Regards,
San

Re: FreeRTOS build failure in Release configuration (MCUXpresso IDE v24.9.25)

EdwinHz — Fri, 06 Dec 2024 21:57:51 GMT

What component are you seeing fail? How is it failing (i.e. hardfault, halting, etc.)? Does it only happen with release build or also with debug build? What MCU, SDK and IDE versions are you using?

BR,
Edwin.

Re: FreeRTOS build failure in Release configuration (MCUXpresso IDE v24.9.25)

sushmasan — Tue, 10 Dec 2024 18:26:35 GMT

Hi @EdwinHz ,

The error is with this component,

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.

Surprisingly I am not seeing the issue now.

These are the steps followed,

- Created a new workspace folder(C:/Test/ws) and while launching the MCU Xpresso IDE provided this as a workspace path

- Copied the Free RTOS code to Test folder

- While trying to build using Debug/Release configuration, Debug is PASS, Release is FAIL.

Now I made few changes,

- Created a new workspace folder(C:/Test/new_ws) and while launching the MCU Xpresso IDE provided this as a workspace path

- Copied the Free RTOS code to new_ws folder

- While trying to build using Debug/Release configuration, now both are PASS.

I am wondering if there is an issue with path or something, then in the first scenario both debug and release has to fail. But only Release configuration build has failed.

Any idea?

Regards,
San

Re: FreeRTOS build failure in Release configuration (MCUXpresso IDE v24.9.25)

EdwinHz — Wed, 11 Dec 2024 17:28:33 GMT

Hi @sushmasan,

It was probably a porting issue that caused the '../freertos/freertos-kernel/portable/GCC/ARM_CM33_NTZ/non_secure/portasm.c' to not be copied correctly into the first workspace. Then with the second one, it was likely copied correctly, which is why it worked on a second try.

BR,
Edwin.