This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F28P659DK-Q1: CPU2 debug prints

Part Number: TMS320F28P659DK-Q1
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hi

To get the debugs prints from CPU2 to PC, i have configured UART. The configurations are same in MCU side and PC side... But uart not working. If there is anythig i need to do in CPU2 side to get the debug prints?

  • Part Number: TMS320F28P659DK-Q1

    Tool/software:

    Hi,

    I am working on configuring UART to send debug prints from CPU2 to a PC on an F28P65x LaunchPad.
    The UART configurations on both the MCU side and the PC side are aligned, and I can successfully receive UARTA(42,43 pins) data when configured on CPU1.

    However, after disabling UARTA(42,43 pins) on CPU1 and setting it up on CPU2, I am unable to get debug prints via UART. Is there anything specific I need to configure or modify on CPU2 to make UART work?

    please reply asap..

  • Hello,

    If UART communication is working on CPU1, then there should be no issue with your hardware setup. You will need to hand over permissions of the peripheral to CPU2 in order to read/write the UART registers. We have some C2000ware examples showing how to hand over ownership of different peripherals to CPU2 in the path: [C2000ware install]/driverlib/f28p65x/examples/c28x_dual/ you can take a look at. 

    Best Regards,

    Delaney

  • Hi

    Thank you.. Its working

    In CPU1 printf(); will work just like in a c program.. But in CPU1 not...
    If i add any library/configurations in CCS IDE will i get CPU2 prints in CCS IDE itself?

  • Hello,

    printf() uses the JTAG connection to the device rather than the UART connection. To clarify, you got printf to work on CPU1 but not on CPU2 is that correct? According to this thread, printf should be possible on both cores. 

    Did you make sure to change the CCS context to CPU2 (by clicking on that core in the debug window)?

    Best Regards,

    Delaney