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.

SK-TDA4VM: Unable to output the added printf information

Part Number: SK-TDA4VM

Hi team,

SDK: ti-processor-sdk-rtos-j721e-evm-08_04_00_06

image version: 08.04.00.10

Operations:

cd vision

 make sdk -j8

 cp vx_app_arm_ipc.out  ./rootfs/opt

./vx_app_arm_ipc.out

VX_app_arm_IPC.out compiled with SDK (print information is added in main function), after copying to the board, it will not output the added printf print information. 

Could you help look into this case? Thanks.

Best Regards,

Cherry

  • Hi Team,

    May I know is there any update?

    Regards,

    Annie

  • Hi Cherry and Annie,

    The procedure that was shared by Cherry looks correct. Here is what I did to test:

    1. Flash prebuilt 8.4 EdgeAI SDK for SK-TDA4VM onto SD card
    2. Add a printf statement in the main function. Specifically: https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/0001_2D00_Testing_2D00_printf.patch
    3. Run the following commands to build and copy over file to SD card (note logs are copy pasted from the history command, so 1999~2002 are the commands I ran):

      1999 cd vision_apps/
      2000 make sdk -j8
      2001 cp out/J7/A72/LINUX/release/vx_app_arm_ipc.out /media/a0488417local/rootfs/opt/
      2002 sudo cp out/J7/A72/LINUX/release/vx_app_arm_ipc.out /media/a0488417local/rootfs/opt/
      2003 history
      a0488417local@udb0488417:/media/a0488417local/2TBStorage/2TBStorage/PSDK_RTOS/ti-processor-sdk-rtos-j721e-evm-08_04_00_06/vision_apps$
    4. Running ./vx_app_arm_ipc.out on the EVM gives the following:


      root@tda4vm-sk:/opt# ./vx_app_arm_ipc.out
      Testing printfAPP: Init ... !!!

      ...and the rest of the default printf logs from vx_app_arm_ipc.out

    I am also using 8.4 SDK to build the ipc test. My recommendation is to compare the flow I shared with the flow that was followed on your end. The only places that I can see a possible issue is the file being edited is different, or if the .out file path is different and the correct .out file is not being transferred over to the SD card.

    Regards,

    Takuma

  • Hi Takuma,

    Thank you for the support.

    The steps are as follows:

    • Flash prebuilt 8.4 EdgeAI SDK for SK-TDA4VM onto SD card
    • Add a printf statement in the main function. Specifically: 
      -Run the following commands to build and copy over file to SD card

    1999 cd vision_apps/
    2000 make sdk
    2001 sudo cp out/J7/A72/LINUX/release/vx_app_arm_ipc.out /media/anzhigang/rootfs/opt/
    2002 history

    sk-tda4vm development board operation as follows:

    root@tda4vm-sk:/opt/vision_apps# ./vx_app_arm_ipc.out
    APP: Init ... !!!
    MEM: Init ... !!!
    MEM: Initialized DMA HEAP (fd=4) !!!
    MEM: Init ... Done !!!
    IPC: Init ... !!!
    IPC: Init ... Done !!!
    REMOTE_SERVICE: Init ... !!!
    REMOTE_SERVICE: Init ... Done !!!
    380.945149 s: GTC Frequency = 200 MHz
    APP: Init ... Done !!!
    ...and the rest of the default printf logs from vx_app_arm_ipc.out


    And there are 2 more questions, would you be able to help check this out? 
    1. They added the print in your patch file and can see the output log normally?
    2. log output of the debug version is the same as that of the release version?

    Thanks and regards,

    Cherry

  • Hi Cherry,

    1. They should see the exact same output as I was seeing. If the software is the same and the hardware is also the same, then I do not have a good idea on why there is a difference between our setup.
    2. The debug version should have more print statements, but the printf I added in the patch should work without building for the debug version.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/vx_5F00_app_5F00_arm_5F00_ipc.out - I attached my vx_app_arm_ipc.out, but can you try running this? If you see "Testing printf" at the start of the logs, then there is something that is wrong with how printf is added to the code, or something wrong with the build. If there are no "Testing printf", I would suspect something wrong with the underlying image flashed onto the SD card.

    Regards,

    Takuma

  • Hi Takuma,

    Could you help compile and run printf testing according to the printf testing above? The customer would like to compare the log output at your end if possible.

    Thanks and regards,

    Cherry

  • Hi Cherry,

    I described in my post from July 24th the steps I have ran to compile and run printf test. I have also copied the relevant logs that shows that printf is functioning as expected.

    If the customer is following the steps exactly as described, then there should be no difference between our logs. However, looking through the steps that have been shared with me, it does look like the steps are followed but resulting logs are different.

    Because there are some differences in resulting behavior, I would like to make our setup as similar as possible by sharing my vx_app_arm_ipc.out that I have verified the extra printf is working. Please run the .out file in my previous post, and share logs so that we can narrow down whether the issue is in the underlying EdgeAI SDK image flashed onto the SD card, or an issue with the build environment/procedure.

    Regards,

    Tauma