• State Resolved
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 59 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

TDA4AL-Q1: How to debug vision_app applications by CCS

TDA4VH-Q1: Debugging Vision_Apps usnig CCS Tool for R5F as TIOVX host

Chandan Modi
Prodigy 10 points

Part Number: TDA4VH-Q1

Hi TI Team,

Following the "Application note for OpenVx Host on R5F (MCU2_0) " we have made the necessary changes and are able to run the Vision Apps without A72, usnig SBL/OSPI mode in RTOS only.

RTOS SDK: 10.1

Board: J784S4 based Custom Board

However I would like to know if it is possible to Debug the App using CCS in No Boot Mode?

It's mentioned that .out runs only on A72:

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1338838/tda4al-q1-how-to-debug-vision_app-applications-by-ccs

Thank you in advance.

Best Regards,

Chandan Modi

 

  • +1
    TI__Mastermind 22280 points

    Hi Chandan,

    Chandan Modi said:
    However I would like to know if it is possible to Debug the App using CCS in No Boot Mode?

    I don't think so, because tiovx firmwares require other cores to be loaded.

    Chandan Modi said:
    It's mentioned that .out runs only on A72:

    Yes, if a72 is the host then .out runs only on a72 but if you managed to run r5f as host and remove a72 then you don't have to consider the .out file

    You can use ccs to debug in sbl boot mode itself, 

    Add while(gLoop) in the mcu2_0 firmware and load the core, one the cores are up connect to ccs and load the symbols in ccs then unblock the core by setting gLoop value. Make gLoop as volatile and global variable. Once it is unblocked then you can debug step by step.

    Regards,
    Gokul

  • 0 in reply to Gokul S
    Prodigy 10 points

    Hi Gokul,
    Thank you! I am able to debug using the suggested method.

    However as understood, in case of SW change, this workflow still requires rebuilding, switching the board to UART boot mode, flashing, then switching back to OSPI boot mode before running and attaching the debugger.

    Additionally, this means I need to be physically present at the board to change the boot mode switches every time I make a software change and want to debug.

    So to sum up, in the typical No‑Boot mode workflow, where the program can be loaded directly without changing boot switches, is currently not possible with Vision_Apps?

    Thanks once again.

    Best Regards,
    Chandan Modi

  • 0 in reply to Chandan Modi
    TI__Mastermind 22280 points

    Hi Chandan,

    Chandan Modi said:

    However as understood, in case of SW change, this workflow still requires rebuilding, switching the board to UART boot mode, flashing, then switching back to OSPI boot mode before running and attaching the debugger.

    I would suggest using a different boot flow which is convenient for debugging instead of ospi, once program is finalized then flash the ospi.

    Chandan Modi said:

    So to sum up, in the typical No‑Boot mode workflow, where the program can be loaded directly without changing boot switches, is currently not possible with Vision_Apps?

    You could give a try by loading all the core's firmware which is running tiovx one by one and then resume all. Default vision_apps firmwares require all the cores to be loaded and running. 

    Regards,
    Gokul