• State TI Thinks Resolved
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 79 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

Original question:

TDA4VM: Debugging TDA4VH R5 cores

TDA4VH-Q1: Unable to do step through debugging for MCU domain R5 core

Deepankar maithani
Prodigy 196 points
Part Number: TDA4VH-Q1

Tool/software:

I followed the instructions provided in  the  documentation  Setting up CCS  But when i launch the launch script i get following error.

I also donot have the   ti-fs-firmware-j784s4-gp.bin  binary in the  folder. How can i get this binary.  Can anyone please help fix itl

  • 0
    Prodigy 196 points

    I managed to  enter the debugging session . But loading binary fails  when i try to load to MCU1_0 in the main domain.

  • 0 in reply to Deepankar maithani
    TI__Expert 6140 points

    Hi,

    Are you trying to debug a Vision Apps example? 

    Debugging Vision Apps examples in CCS is very difficult and not recommended as it requires specific techniques to load firmware onto cores and then begin debugging an individual core. It is much more difficult in Vision Apps as the binaries span across multiple cores instead of a single core.
    Thanks,

    Neehar

  • 0 in reply to Neehar Sawant
    Prodigy 196 points

    The loading of firmware is not working even for the other binaries which are not related to vision apps.  I am doing following steps:

    1. I am building the binary using the following command

    pdk_j784s4_09_02_00_30/packages/ti/build$ make -s ipc_qnx_echo_test_freertos BOARD=j784s4_evm PROFILE=debug

    2. Then i run my  ccxl launch file by right clicking on it in the Target configuration tab as shown below

    3. It takes me in the debugging view. Below is the state of my cores in debugging window

    4. Then i go to the scripting console and run the launch.js file. I get following logs

    5. Then i connect to Main_cortex_R5_0_0 core as shown below. The core goes in suspended state.

    6. Afterwards i try to  load firmware the firmware ipc_qnx_echo_test_freertos_mcu2_0_debug.xer5f in the MAIN_Cortex_R5_0_0.

    7. I get following error message

    What could be the issue.

  • 0 in reply to Deepankar maithani
    TI__Expert 6140 points

    Hi,

    Can you test if you are able to load an example without HLOS running? For example, Sciserver or GPIO blink example.
    Thanks,

    Neehar

  • 0 in reply to Neehar Sawant
    Prodigy 196 points

    I am not running any HLOS. I have removed the uboot from the OSPI partition and hence there is no HLOS boot.  My understanding is that in such a situation the Board will go in no boot mode. One more question. Does the MCU cores used DDR  during code execution or do they use the internal SRAM. After running the launch.js i see that DDR is being configured. I was wondering is it required for the microcontroller code to run ?

  • 0 in reply to Neehar Sawant
    Prodigy 196 points

    Can you point me to the documentation for building these examples?

  • 0 in reply to Deepankar maithani
    Prodigy 196 points

    I built the another binary using  make -s GPIO_LedBLink_TestApp_freertos  PROFILE=DEBUG BOARD=j784s4_evm.  and tried to flash it to MCU1_0 and build one with CORE=mcu2_0 for MCU1_0 in the main domain. BUt i always get the same error as in step 7 above. I also erased the uboot from OSPI so that the board is in noboot mode. Here is how my Main domain UART output looks like

  • 0 in reply to Deepankar maithani
    TI__Expert 6140 points

    Hi,

    Have you set the switches on your board to be in No boot mode?

    SW11[1-8] = 1000 1000
SW7[1-8]  = 0111 0000


    Thanks,

    Neehar