Building a MQX Standard project with PE and KSDK

[bhh]

I am trying to build a project for the TWR-K60 board using KDS 2.0, KSDK 1.1 with a MQX Standard RTOS.

This is the flow I am following...

1. Create new KDS project.

2. Choose the board.

3. Select Kinetis SDK, enable Processor Expert and choose Standalone mode.

4. Change OSA component from bare metal to MQX KSDK (this chooses MQX Lite by default)

5. Fix the clocks for the processor (delete default clock configs 2-4 since they can't support the desired UART rates)

6. Change the settings for the DebugCs1 fsl_debug_console to use UART5 at 115,200 (this is the OSJTAG debug output)

7. Config other peripherals and pins.

8. Generate the PE code.

9. Build the project.

This all works fine.

However, if I try to change the RTOS to MQX Standard from Lite, a couple things occur.

First, I have to delete the DebugCs1 console.  MQX Standard doesn't seem to be able to share the UART with the other drivers.

I have tried to set the MQX Standard debug to UART5 and DebugCs1 to a different UART, but I still get the error.

I also have to add at least one MQX task before generating the PE code.

I can generate the PE code, but building the project results in about 40 errors.  It seems like the code is trying to assert portions of the DebugCs1 UART without it being there.

Has anyone else run into this?  Any workarounds?

Thanks.

[Jorge_Gonzalez]

Hi again Brian:

I think I found the issue.

Seems that the new project wizard is failing to add paths to gcc libraries when creating a K60 project with PEx + MQX + KSDK.

To solve this select your project and go to Project -> Properties -> C/C++ Build -> Settings -> Cross ARM C++ Linker -> Miscellaneous and in "Other" objects add the next library files:

"${eclipse_home}/../toolchain/lib/gcc/arm-none-eabi/4.8.0/libgcc.a"

"${eclipse_home}/../toolchain/arm-none-eabi/lib/libc.a"

"${eclipse_home}/../toolchain/arm-none-eabi/lib/libsupc++.a"

"${eclipse_home}/../toolchain/arm-none-eabi/lib/libm.a"

Refer to the picture below:

Then do a "clean" and rebuild the project. The errors should be gone.

Regards!,
Jorge Gonzalez

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[bhh]

That did the trick.  Thanks!

[Jorge_Gonzalez]

Hello Brian Hight:

I have reproduced the same problem as yours. I need to investigate this with the software team. Please let me reply as soon as I get some feedback or resolution.

Regards!

Jorge Gonzalez