• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 516 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.

TDA4VH-Q1: Unable to Debug using XDS110

Gowtham R
Intellectual 300 points
Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Tool/software:

Hi TI team,

Thanks for looking into this

Trouble Halting Target CPU:
(Error -1325 - (0:0:0))
Device failed to enter debug/halt mode (cannot determine cause). Choose 'Force Debug' to force the CPU into a state that allows debug of the CPU.  Note that this is a debug tool and you will not be able to reliably restart code execution after invoking this feature.  A Power-On Reset of the device will be required to resume system operation.
(Emulation package 9.12.0.00150)

When I try to load my firmware C71X_0 its throwing this error.

I am trying to load the firmware from CCS(12.4)

SDK 9.2

Let me know how to solve this error , I want to setup a env to debug the error

For initial setup I followed https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j784s4.html

after that when i try to load my firmware I am getting this error, what are the possible reasons for this

We are blocked , any resolution can help us.

  • 0
    TI__Mastermind 21520 points

    Hi,

    Is this a custom application? Is the application you are running on C71X_0 baremetal or FreeRTOS? If it is FreeRTOS, you will need to start the MCU1_0 core to ensure sciserver is running.  

    Can you confirm you are booting the board in No Boot mode and running the launch.js script? 

    Thanks,

    Neehar

  • 0 in reply to Neehar Sawant
    Intellectual 300 points

    Hi,

    Thanks for the response ,

    Yes its a custom application , 

    C71x is running on FREERTOS

    Can you confirm you are booting the board in No Boot mode and running the launch.js script? 

    yes, changed the SW11 and SW7 settings to NO boot mode and did this,

    One thing is if i try to load a pre-built firmware from SDK-RTOS like pdk udma_xxx_.xe71 and vision_apps out for C71 I am able to go ti debug mode, where as when I load my own firmware, I am not able to make C71x go into debug mode.

  • 0 in reply to Gowtham R
    Intellectual 300 points

    C71X_0: Trouble Reading Memory Block at 0xa663c680 on Page 0 of Length 0xc0: (Error -1044 - (0:128:0)) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.12.0.00150) C71X_0: Trouble Halting Target CPU: (Error -1325 - (0:0:0)) Device failed to enter debug/halt mode (cannot determine cause). Choose 'Force Debug' to force the CPU into a state that allows debug of the CPU. Note that this is a debug tool and you will not be able to reliably restart code execution after invoking this feature. A Power-On Reset of the device will be required to resume system operation. (Emulation package 9.12.0.00150) MCU_Cortex_R5_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.12.0.00150) C71X_0: Error C71X_0: Error: (Error -1353 - (0:0:0)) Register or Memory request has timed out for an unknown reason. Restart the application. If error persists, please report the error. (Emulation package 9.12.0.00150) C71X_0: Error: (Error -1170 - (0:0:0)) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.12.0.00150) C71X_0: Unable to determine target status after 20 attempts C71X_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging M

    The error I am facing. it throws a pop up saying to do Force Debug, if I continue with that option this happens

  • 0 in reply to Gowtham R
    TI__Mastermind 21520 points

    Hi,

    Neehar Sawant said:
    If it is FreeRTOS, you will need to start the MCU1_0 core to ensure sciserver is running.  

    Were you able to test this? Simply click on the MCU1_0 core and press the resume button.

    To confirm, you only see this issue with your custom board? 

    Do you see the issue when loading your application or when running? Does your program reach main?

    Thanks,

    Neehar

  • 0 in reply to Neehar Sawant
    Intellectual 300 points

    To confirm, you only see this issue with your custom board? 

    I don't use the custom board, its TDA4VH, yes the custom firmware application throws this error

    Were you able to test this? Simply click on the MCU1_0 core and press the resume button.

    When to do this after i load my firmware or before that?

    Do you see the issue when loading your application or when running? Does your program reach main?

    No its not reaching the main program

  • 0 in reply to Gowtham R
    TI__Mastermind 21520 points

    Hi,

    Gowtham R said:

    To confirm, you only see this issue with your custom board? 

    Sorry this was a typo, I meant with your custom application.

    Gowtham R said:

    When to do this after i load my firmware or before that?

    You can test starting MCU1_0 core before you start the C71X core. Either after loading your application or after should not make a difference. Let me know your results.

    If you are not reaching the main program there will be an issue with the boot up code. You can disable main as the entry point to step through and debug the startup code for C7x.

    Thanks,

    Neehar

  • 0 in reply to Neehar Sawant
    Intellectual 300 points

    If you are not reaching the main program there will be an issue with the boot up code. You can disable main as the entry point to step through and debug the startup code for C7x.

    How to change the entry point, and is there i way to set the files path ?

  • 0 in reply to Gowtham R
    TI__Mastermind 21520 points

    Hi,
    I will follow up with more information tomorrow. 
    Thanks,

    Neehar

  • 0 in reply to Neehar Sawant
    Intellectual 300 points

    Thanks will be helpful for us

  • 0 in reply to Gowtham R
    Intellectual 300 points

    Hi, any update in this? and can we use the Latest CCS version for SDK 9.02 ? (CCS 20).

    I am having CCS 12.4 for now

  • 0 in reply to Gowtham R
    TI__Mastermind 21520 points

    Hi,

    Gowtham R said:
    How to change the entry point, and is there i way to set the files path ?

    Right click on the target configuration you are using and click 'Properties'. On the tab on the left, select 'Auto Run and Launch Options'. And under 'Auto Run Options', you can remove 'main' from the 'Run to symbol' option under 'Auto Run Options'. Select 'Apply and Close' and let me know if this works for you.

    Gowtham R said:

    nd can we use the Latest CCS version for SDK 9.02 ? (CCS 20).

    I am having CCS 12.4 for now

    You are using the correct version of CCS for SDK 9.2. We do not support CCS 20 for SDK 9.2 and the SDK has been validated and tested on CCS 12.4 as seen on the setup page.

    Thanks,

    Neehar

  • 0 in reply to Neehar Sawant
    TI__Mastermind 21520 points

    Hi Gowtham,

    Following up, is this issue still open?

    Thanks,

    Neehar