• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 84 subscribers
  • Views 263 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.

TMS320F28379D: Unable to set GPIO115 high in custom carrier card

Gautham Angadi
Prodigy 140 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: DRV8305

Tool/software:

Hi,

We have TMS320F28379D, through which we are trying to drive DRV8305, we are using CCS 12.5. We have tested our open loop code in Launchpad with Boost XL and it is working. On Launchpad, GPIO124 is connected to EN_GATE, however, in our board GPIO115 is connected to EN_GATE. On changing GPIO pin from 124 to 115 on our program, building it and debugging it, we get the following error:

"
C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201) C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0x8750) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201) C28xx_CPU1: Unable to determine target status after 20 attempts 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 C28xx_CPU2: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201) C28xx_CPU2: Error: (Error -1135 @ 0x8750) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201) C28xx_CPU2: Unable to determine target status after 20 attempts C28xx_CPU2: 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
"
 We have tried using a simple toggle program to test if we can toggle GPIO115, we used the blinky example which is available. We were successfully able to toggle the pin.
What can we do to debug this further?
Note:
Although GPIO115 is not available on Launchpad, we still tried to use our original program with GPIO115 pin as output and we did not get the above error.
  • 0
    TI__Mastermind 27720 points

    Hi Gautham,

    It seems GPIO115 is also used for JTAG (EM2RAS). Reassigning this thread to a JTAG expert.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 140 points

    Okay, thank you.

  • 0 in reply to Gautham Angadi
    TI__Mastermind 36526 points

    Guatham,

    Actually I do not think that GPIO115 is a JTAG signal. Are you able to share the schematic for your JTAG signals on you board(TCK,TMS,TDI.TDO,TRST)?

    Thanks,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 140 points

    Hi ,

    JTAG pins are already defined in TMS320F28379D, right? 

    Please find below ss of our schematic of JTAG Pins and GPIO115 Pins, its a custom board, wherein we are using TMS320F28379D and DRV8305.

    We are unable to make GPIO115 high on our custom board, if we set GPIO115 as 0, we don't get any error.
    GPIO_writePin(115, 0); // Update EN_GATE pin

    Wherever, we set GPIO115 high, we get the below error.
    GPIO_writePin(115, 1); // Update EN_GATE pin

    C28xx_CPU1: GEL Output:
    Memory Map Initialization Complete
    C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
    C28xx_CPU2: GEL Output:
    Memory Map Initialization Complete
    C28xx_CPU2: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
    C28xx_CPU1: Error: (Error -1135 @ 0x856A) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0x856A) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU1: Unable to determine target status after 20 attempts
    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
    C28xx_CPU2: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU2: Error: (Error -1135 @ 0x856A) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201)
    C28xx_CPU2: Unable to determine target status after 20 attempts
    C28xx_CPU2: 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 Gautham Angadi
    TI__Mastermind 36526 points

    Hi,

    I'm sorry, but I will not be able to look into this until next week.

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 140 points

    Hi

    Are you available now?

    Please look at this thread, wherein, I have identified the part in my code which is causing the error:
    (1) C28xx_CPU1: Error: (Error -1135 @ 0x8B25) - C2000 microcontrollers forum - C2000Tm︎ microcontrollers - TI E2E support forums

  • 0 in reply to Gautham Angadi
    TI__Mastermind 36526 points

    Hi Gautham,

    I am available now, I replied to your other thread. Thank you for the additional information.

    Best Regards,

    Ben Collier