• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 348 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.

TDA4AL-Q1: [IFV700]: How to enable trace logs from pdk source files

Dinesh Badkas
Intellectual 545 points
Part Number: TDA4AL-Q1

Hello Team,

we are looking for to enable the trace logs from source files from pdk folder for debug purpose. (GT_0trace, etc..)

e.g. ti-processor-sdk-rtos-j721s2-evm-09_00_00_02/pdk_j721s2_09_00_00_45/packages/ti/drv/dss/src/*.c

Sample source:

We built files using script: sdk_builder/make_sdk.sh

Later updated *.out files on the EVM at path: /lib/firmware/vision_apps_evm

reboot EVM.

unfortunately we are not able to see expected logs on board console.

Request your suggestions to resolve this problem please.

  • 0
    TI__Guru* 84926 points

    Hi,

    These are error logs which would be printed from MCU2_0.

    Could you please confirm if you are looking for the error logs by triggering this error or you have used some dummy logs using the same API?

    Please run ./vision_apps_init.sh script before running the application to get the remote core logs.

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Intellectual 545 points

    Hello Nikhil,

    During run time we are getting 'Request submit failed' error, while making viss as input.

    Looks like driver is returning with -2 (invalid argument) error code. Hence we wanted to check which argument.

    Agreed those prints are from mcu2.0.

    we would need both - error logs also and temporary dummy logs also for debug purpose.

    Yes, every time we are executing init script. But no prints seen on board console.

    My basic doubt is which uart port needs to be connected for mcu2.0 console? 

    Presently I am just checking on following uart (J44), where we get linux boot logs and console: 

  • 0 in reply to Dinesh Badkas
    Intellectual 545 points

    Looks like macro - FVID2_CFG_TRACE_ENABLE needs to be enabled used in following header: trace.h

    #if part looks to be disabled:

    But macro looks be defined as follows:

    request your guidance please, to resolve our confusion.

    Also one strange thing I observed is, if I intentionally introduce any compilation error in any of the source in /drv folder, ./make_sdk.sh shows the compilation error but it still proceeds for to link its lib/.out but does not break the build.

  • 0 in reply to Dinesh Badkas
    Intellectual 545 points

    After compilation. we are replacing following bins:

    Kindly correct us, if we are wrong:

  • 0 in reply to Dinesh Badkas
    TI__Guru* 84926 points

    Hi,

    Are you also trying print using  GT0_trace() with DssTrace as mask and GT_ERR as class type in the file dssm2mApi.c file as shared in the screenshot?

    FVID2_CFG_TRACE_ENABLE is enabled by default. Additionally, (for eg. in DSS), DssTrace mask also enables on GT_ERR class of logs.

    This could be seen in dss_cfg.h

    To build this dss library, you could have to go to pdk repo (${PDK_PATH}/packages/ti/build) and do

    make pdk_libs CORE=mcu2_0 BOARD=j721s2_evm

    with this, please confirm if the DSS driver files got built successfully.

    After this, you could build ./make_sdk.sh, and check if the logs are printing.

    Dinesh Badkas said:
    Presently I am just checking on following uart (J44), where we get linux boot logs and console: 

    This is correct. You will get the logs along with A72 itself from MCU2_0 

    Regards,

    Nikhil