• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 319 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.

Original question:

CCS/TMS320F28377S: Error -1135 @ 0x0 when debugging F28377S

TMS320F28377S: F280025C_UNIVERSAL MOTOR CONTROL PROJECT FOR BLDC USING DRV8323 debug not happened

Bhuvaneshwaran M
Prodigy 190 points

Part Number: TMS320F28377S

Dear team

we are working LAUNCHXL -280025C for universal motor control project with 80 pin package , with drv8343 bldc motor pump verified motor running successfully 

 now to migrate same mcu f280025 with 48 pin package , when trying to debug we observed below points

1.when connect 80 pin with EVM 3.3v with usb can flash program and debug also 

 METHOD OF CONNECTION  PIN PACKANG MCU WHEN JTAG 3.3 v input (WITHOUT 12V POWER SUPPLY) FLASHED PROGRAM COMMENTS  WHEN JTAG 3.3 v input (WITH 12V POWER SUPPLY) FLASHED PROGRAM COMMENTS 
(LUANCH XL F280025C) EVM with drv8343 EVM F280025 - 80 PIN TCK=3.3V (YES)DUBUG HAPPENED  TCK=3.3V DUBUG HAPPENED 
TMS=0V TMS=0V
OUR TARGET BOARD(F280025 ) WITH XDS110 PROGRAMMER (LUANCH XL F280025C) F280025 - 48PIN TCK=3.3V DUBUG HAPPENED  TCK=0V DEBUGG NOT HAPPENED (mcu got reset )
TMS=0V TMS=3.3

  • 0
    TI__Guru 55700 points

    What is the error message reported in CCS?

  • 0 in reply to Manoj Santha Mohan
    Prodigy 190 points

    We are working f280025c -48 pin on ECU  we are reused universal motor control project which is having 80 pin code (changed 48 pin configuration), and verified EVM board also working fine which is corresponding 48 pin ,

    Now trying to flash the program our target ECU (Electric coolant pump) observed below pints

    1. when we connect programmer and without 12 v power supply  we can successfully flash the program to ECU , also debug happening not get any error

    But during the time switched on 12 supply MCU got reset , its showing below error

    C28xx_CPU1: JTAG Communication Error: (Error -1135 @ 0xAD1C) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.7.0.00213)

    C28xx_CPU1: 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

    1. when we connect 12v and trying to flash program to ECU immediately got below issue, please let me know your feedback on this . we need to disscsss on this  

    C28xx_CPU1: GEL Output:
    Memory Map Initialization Complete
    C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Start ...
    C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
    C28xx_CPU1: JTAG Communication Error: (Error -1135 @ 0x82F1E) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.7.0.00213)
    C28xx_CPU1: 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 

  • 0 in reply to Bhuvaneshwaran M
    TI__Guru 55700 points

    C28x the debug probe reported an error

    This error is commonly associated with C28x devices and is usually associated with a range of hardware or firmware problems that prevent the JTAG debugger to connect to the core.

        C28xx: Error connecting to the target:
    (Error -1135 @ 0x0)
    The debug probe reported an error.
    Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

    The e2e forum threads below cover some possible root causes for this issue:

    This error can also manifest when caused by the problems reported in the Invalid data read back section above