• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 276 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

SK-TDA4VM: MCU Domain UART Access

SK-TDA4VM: Access to MCU console output

Peter Tucker
Prodigy 50 points

Part Number: SK-TDA4VM

I am using the J721s2 SoC board with the TDA4 common processor board and an attached fusion application board.  I have successfully built the vision apps (with PROFILE=release) using the j721s2 RTOS PSDK, and am able to run the single camera application with an AR0233 sensor.  Linux console output from the A72 cores shows up as expected on the lowest COM port associated with J44, but I am seeing no output on any of the other COM ports that appear when I connect J43 and J44 to my PC via USB ports. 

I am writing a driver for a new sensor, and would like to view the printf statements being generated by the ISS server running on mcu2_0 to assist with debugging my code.  Is there something special I need to do to enable this output?

Thanks.

  • 0
    Prodigy 50 points

    So I think I've resolved the issue with viewing the output of printf statements from the R5F cores.

    The first thing I realized is that printf output from various cores is being output on the same COM port as the Linux console output.  Lines of output that originate from other than the A72 cores running Linux are prefixed with the identity of the core originatine the output (for example [MCU2_0] or [c7x_2]).

    The second thing I discovered is that the imaging subsystem's diagnostic output can be enabled/disabled in the file imaging/sensor_driver/src/iss_sensor_priv.h. The file contains #defines and #ifdef statements that control whether or not diagnostic output is generated by the subsystem, as follows:

    //#define ENABLE_DEBUG_IMAGING

    #ifdef ENABLE_DEBUG_IMAGING
    #define issLogPrintf(f_, ...) appLogPrintf((f_), ##__VA_ARGS__)
    #else
    #define issLogPrintf(f_, ...)
    #endif

    uncommenting the //#define ENABLE_DEBUG_IMAGING line, then rebuilding the imaging and vision applications, will cause the imaging subsytem's printf statements to show up on the LInux console.