Using printf on kinetis on a custom hardware (no development board) with MQZLite

[kaustubhkagalka]

Hi,

I a working on a project where we are using "mkl26z256vlh4" processor. I am trying to get some debug data through a UART on a PC. I am following this guide Tutorial: Printf() with (and without) Processor Expert | MCU on Eclipse .

This worked when I was using the same hardware without MQXLite RTOS. But when I use it with MQXLIte I get some build errors,shown in the attachments.

Is there any way I can still use ConsoleIO component to get the debug data through UART?

[Kan_Li]

Hi Kaustubh Kagalkar,

I have a FRDM-KL26z on hand, and will try to test the console feature with MQXlite, any progress will keep you posted. Thanks for your patience!

Have a great day,
Kan

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

[kaustubhkagalka]

Thanks Kan.

[Kan_Li]

Hi Kaustubh Kagalkar,

I found there is already a MQX Lite demo based on FRDM-KL25Z , which uses ConsoleIO component to get the debug data through UART, so I think you may use that demo as a starting point. The project can be found in the fold of "C:\Freescale\CW MCU v10.6\MCU\CodeWarrior_Examples\Processor_Expert\MQXLite\Kinetis\FRDM_KL25Z\LED_KL25Z" Please kindly refer to the following for more details.

Hope that helps,

Have a great day,
Kan

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

[kaustubhkagalka]

Hi Ken ,

Thanks for your answer , will check out this solution. Talking to my colleague who started this project, he thinks he selected "No I/O" instead of "UART" while creating this project.taht could be the issue.

Kaustubh