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.

TDA4VH-Q1: UART example not starting

Part Number: TDA4VH-Q1

Hello all,

BOARD: J784S4XEVM Evaluation board | TI.com

I have compiled using "

ti-processor-sdk-rtos-j784s4-evm-09_00_00_02.tar.gz  — 1432019 K

"

the demo app Uart_TestApp_Freertos for mcu2_0, and placed in the sd card location as seen bellow:

On a separate thread: TDA4VH-Q1: signing rtos binaries for HS devices - Processors forum - Processors - TI E2E support forums

I found out which binary to place in the lib location.

Now, the problem is, I have both usbs connected to the pc, and done as this described:

Jacinto Processors TDA4AP/TDA4VP/TDA4AH/TDA4VH EVM Users Guide (ti.com)

now, how can I get the mcu2_0 to talk with me?

Is MCU2_0 connected to any uart?

  • Hi,

    By default all the main domain cores uses the same UART. If you are running Linux along with any application on mcu2_0, you can modify the your mcu2_0 application to send logs on a different UART and make sure that UART is not used by Linux.

    Regards,
    Parth

  • I hoped it would do it automatically, all I had to do is change the cores in the build....or?

    I have Uart_TestApp_freertos compiled for MCU2_0, does it still use the same UART as the LInux cores? the reason I ask is because documentation is limited on this matter and faulty a bit too. Where must I change to have it output data on the next UART ( i have the linux com port on com4, so how to make it write to com5?)

    Br, Mircea

  • please, show me where to edit the Uart_TestApp_freertos to have it spit data on any of the ones bellow: 

  • Hi Mircea,

    For Uart_TestApp_freertos, you should be able to change the UART port by changing the UART_INSTANCE in UART_baord.h at <PDK>/packages/ti/drv/uart/test/src

    Regards,
    Parth

  • I have no idea what to make of this:

    The BOARD uarts that I have are the following:


    /* UART LLD instance number for primary UART port */
    #define BOARD_UART_INSTANCE (8U)
    /* UART LLD instance number for MAIN UART1 port */
    #define BOARD_UART1_INSTANCE (1U)
    /* UART LLD instance number for MAIN UART2 port */
    #define BOARD_UART2_INSTANCE (2U)
    /* UART LLD instance number for MAIN UART3 port */
    #define BOARD_UART3_INSTANCE (3U)
    /* UART LLD instance number for MAIN UART4 port */
    #define BOARD_UART4_INSTANCE (4U)
    /* UART LLD instance number for MAIN UART5 port */
    #define BOARD_UART5_INSTANCE (5U)
    /* MCU UART LLD instance number */
    #define BOARD_MCU_UART_INSTANCE (0U)
    /* WKUP UART LLD instance number */
    #define BOARD_WKUP_UART_INSTANCE (0U)

    Ok, everything nice and good, in the document: Jacinto Processors TDA4AP/TDA4VP/TDA4AH/TDA4VH EVM Users Guide (ti.com)

    We can see that the MCU_UART, the one I am connected to, i think ( for me it is COM4), this is where I see the data from the LINUX and have my shell. as you can see, they are not the same numbers. my RTOS is using BOARD_UART_INSTANCE, which is 8, and MCU_UART is 0, so I should have the data from my MCU UART on another com port, right?

    And how do I map these numbers? 

    "UART5 COM 2", which core has UART5?, I can trial-and-error check in my PC, connecting Putty to each new COM that I see, but how to make sure it is actualy connected to the correct core?

  • Hi,

    Please refer to the UART chapter in TRM.

    There is 1 UART instance available in MCU Domain, 1 in Wkup Domain and 10 in Main Domain.
    EVM only exposes 6 of these instances, as you can see in the image that you shared from the user guide.

    Now ideally, you can use any of these 6 instances for printing logs for EVM, but for simplicity all MCU domain (MCU1_0) logs are routed to MCU_UART0, that is the first COM Port which enumerates after connecting to J48.

    All the main domain logs are routed to UART 8 by default. Now, you can modify your UART test app to use UART 5, 2 or 3 for logging so it does not conflict with Linux logs. You can do this by changing the instance UART_board.h as explained in the previous post.

    Regards,
    Parth