sample_embedding_folder2/0676905.txt

Ticket Name: RTOS/TDA2: NDK 2_24_02_31 debug print

Query Text:
Part Number: TDA2 Tool/software: TI-RTOS Hello everyone! I am trying to do some modifications within the TCP source files. I am using VISION_SDK_02_12_01_00 for Windows. In order to do some debugging, I have used "DbgPrintf" and "printf" functions. However, when one of these functions gets invoked, I cannot see an appropriate output on the serial port. At first, I have used a MicroSD card to load the AppImage and I could not see any output of these functions. After that, I have loaded the AppImage using JTAG connection and CCS and I have not noticed the output neither on the UART console nor on the CCS console. Is there any solution to debug the NDK code using debug prints that would be visible on the UART console, or as the second solution, to be visible on the CCS console? I would like that solution not to imply using any application beyond the VSDK, i.e. I would just like to run the AppImage and to get the desired print outputs. Thanks in advance, Marko

Responses:
Hello Marko, The NDK debug prints (using printf and dbgprintf) are not routed to serial port and are only console prints. These will only come on CCS console. We don't support serial prints in NDK as it is independent package. There are 2 options 1. After loading appimage and before running use-case, connect CCS and load symbols. After this you should get prints on console. 2. If you are sure that your debug code won't run before initialization of VSDK, you can directly Vps_printf function of VSDK (define prototype locally & declare it as extern).

Thanks, Prasad. Linking the Vps_printf function with NDK resolved my issue.