DebugP_log() and UART

Eli Mordel

Expert 1345 points

Other Parts Discussed in Thread: SYSCONFIG

Hi,

I'm using the mcu_plus_sdk_243x with am243x-EVM

I found out how to use UART_putchar() for printouts.

Does the DebugP_log() eventually uses UART to print out ?

I've followed the code but could not find the exact place when it puts chars in UART.

In which file and function does the DebugP_log() uses the UART ?

Thanks,

Eli

over 1 year ago

0 QJ Wang over 1 year ago

TI__Guru**** 197036 points

Hi Eli,

I will forward your question to our expert.

0 Eli Mordel over 1 year ago in reply to QJ Wang

Expert 1345 points

Thanks!

0 QJ Wang over 1 year ago in reply to Eli Mordel

TI__Guru**** 197036 points

Hi Eli,

The DebugP_log has three options: UART0, CCS console, or memory log.

Please refer to the description on TIREX page:

For AM243x:

https://dev.ti.com/tirex/explore/node?node=A__AD2nw6Uu4txAz2eqZdShBg__com.ti.MCU_PLUS_SDK_AM243X__AROnekL__LATEST

For AM263x:

https://dev.ti.com/tirex/explore/node?node=A__AD2nw6Uu4txAz2eqZdShBg__com.ti.MCU_PLUS_SDK_AM263X__aBmeCqF__LATEST

0 Eli Mordel over 1 year ago in reply to QJ Wang

Expert 1345 points

Hi,

Yes it's a very useful information .

I'm trying to follow the code and understand how the DebugP_log() function works with the UART.

I did single step dive into each function it invokes and finally got into out(..) function which I cannot understand.

I see it works but I would like to understand the moment it calls the Uart_putchar() or any other UART function.

Is this code found in *.c file or maybe *.lib somewhere in the SDK ?

Thanks,

Eli

0 QJ Wang over 1 year ago in reply to Eli Mordel

TI__Guru**** 197036 points

Eli Mordel said:
Is this code found in *.c file or maybe *.lib somewhere in the SDK ?

It is in *.c files of SDK.

0 Eli Mordel over 1 year ago in reply to QJ Wang

Expert 1345 points

Hi,

I'm glad - It's much easier to use c files instead of libraries.

Can you please tell me in which c file in the SDK the DebugP_log() uses the UART ?

Thanks,

Eli

0 QJ Wang over 1 year ago in reply to Eli Mordel

TI__Guru**** 197036 points

Hi Eli,

1. DebugP_log() --> _DebugP_logZone()

2. _DebugP_logZone() calls (void) vprintf_(format, va); --------- DebugP_nortos.c

3. vprintf_() calls _vsnprintf(_out_char..) in ../kernel/nortos/dpl/common/printf.c

4. _out_char(..) calls putchar_(character); -- printf.c

5. putchar_(character); calls putchar(character); -- ti_dpl_config.c

0 Eli Mordel over 1 year ago in reply to QJ Wang

Expert 1345 points

Hi,

I see the putchar() in the ti_dpl_config.c but when I follow step by step with the debugger - eventually it calls the sdtdio putc which doesn't call the UART

Further down in ti_dpl_config.c ther's a DebugP_uartLogWriterPutChar(character); which actually invokes the UART

How can I get rid of the putchar(character); - the ti_dpl_config.c is an "Auto generated file"

Thanks,

Eli

0 QJ Wang over 1 year ago in reply to Eli Mordel

TI__Guru**** 197036 points

HI Eli,

putchar(character) in putchar_() is to display the text in CCS console.

You can disable the CCS Log from the sysconfig:

0 Eli Mordel over 1 year ago in reply to QJ Wang

Expert 1345 points

Thanks !

Code Composer Studio™︎

Code Composer Studio forum

DebugP_log() and UART