Threadx porting guide for LPC546xx controllers through MCUXpresso IDE

[prasannanaik]

Hi,

I am using LPC546xx and MCUXpresso IDE v11.5.

I want to port threadx on this platform.

Is there any guide for this or reference code?

Thanks and best regards,

Prasanna

[PabloAvalos]

Hi @prasannanaik 

Thank you so much again for your patience.

After double-checking with my teammates, our suggestion for a porting guide, you can refer to LPC55s69 SDK 2.11.1. It provides good example for porting to LPC546xx.

Also, you can refer to ThreadX doc :

https://docs.microsoft.com/en-us/azure/rtos/threadx/overview-threadx

Especially for ARM v8 part:

https://docs.microsoft.com/en-us/azure/rtos/threadx/user-guide-armv8m/chapter1

Hope this information might be helpful, please let me know if you have more questions, otherwise, please mark this answer as an accepted solution.

Thank you.
Sincerely,
Pablo Avalos.

[prasannanaik]

Hi @PabloAvalos ,

I have used LPC55s69 SDK as reference but its architecture is different than LPC546.

I have followed the process shared at "https://github.com/azure-rtos/threadx/blob/master/ports/cortex_m4/gnu/readme_threadx.txt"

The first step in the guide is to build the threadx library using the batch file given in example folder: "https://github.com/azure-rtos/threadx/tree/master/ports/cortex_m4/gnu/example_build"

I have used process and commands mentioned in the following link to build:

"https://mcuoneclipse.com/2017/08/03/building-eclipse-and-mcuxpresso-ide-projects-from-the-command-li... 

After building the batch file, I got a library file tx.a of Threadx.

I have renamed this file as threadx_sp.a

On linking this threadx_sp.a library file, I get the following error:

lpcxpresso54608_gpio_led_output2.axf uses VFP register arguments, C:\Users\20071270\Desktop\Threadx RTOS Workspace\LPC546 Workspace\lpcxpresso54608_gpio_led_output2\azure-rtos\binary\threadx\cortex_m4\mcux\libthreadx_sp.a(tx_block_allocate.o) does not

In Threadx forum, they have mentioned to enable VFP in the compiler and assembler to avoid this problem.

How do i enable VFP in the compiler and assembler during command line build?

Thanks and best regards,

Prasanna

[PabloAvalos]

Hi @prasannanaik 

Hope you find well, thank you so much for your reply and your patience.

Regarding your question, I found a thread that might be helpful to solve your issue with the VFP. You should check it: https://community.nxp.com/t5/Kinetis-Design-Studio/Error-VFP-register/m-p/426794

In addition, you can try going directly to MCUXpresso and change some settings on there, like this one:

Or trying to follow the suggestions on this thread from our community, too: https://community.nxp.com/t5/MCUXpresso-IDE/Unable-to-get-printf-to-print-floating-point/m-p/721059

Please let me know if the information was helpful, or if you still need help too. I will stay tuned to your answer.

Thank you so much.
Sincerely,
Pablo Avalos.

[prasannanaik]

Hi @PabloAvalos ,

Thanks for your reply.

I have tried methods shared in both the links but none is useful. 

My problem is that I am trying to build threadx library using command line feature of MCUXpresso.

When I use the built library in my project it results in the VFP register error as mentioned earlier.

As per threadx forum, there should be some way of enabling floating point access during compilation through command line.

I couldn't find the commands in the user manual.

Can you please go through the communication from threadx team below to understand the problem clearly:

https://github.com/azure-rtos/threadx/issues/184

Thanks and best regards,

Prasanna

[prasannanaik]

Hi Pablo,

Is there any update on the query?

Thanks,

Prasanna

[PabloAvalos]

 Hi @prasannanaik 

Please accept my apologies for the delay, we are overloaded on the requests these days. I really appreciate your patience.

Regarding your question, we are still checking the information that you are requesting. Please let me know if you have any other questions. I will answer you as soon as possible with the proper information.

Thank you so much again.
Best Regards.
Pablo Avalos.