• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 714 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.

CCS/TMS320F28379D: TMS320F28379D disconnected from CCS during system run.

Pemendra Kumar Pardhi
Prodigy 140 points
Part Number: TMS320F28379D


Tool/software: Code Composer Studio

Respected Sir/mam,

I have generated the code from MATLAB 2019b for voltage source inverter control and system  is operated from CCS 9.1.0. I am able to change the value of variable from expression. but issues is that after few time Taget is disconnected from CCS and got masage on console      

IcePick_C_0: Error: (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 8.2.0.00004)
C28xx_CPU1: JTAG Communication Error: (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 8.2.0.00004)
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

 How i can solve this issues.

Thank 

 

  • 0
    TI__Guru 57255 points

    Hi Pemendra,

    Can you give more details about your system's hardware? 

    1. Is your VSI hardware a baseboard that either a controlCARD or LaunchPad plugs into?
    2. Or is this custom hardware?


    If (1), I might recommend for you to consider removing the capacitor that bridges the isolation gap (C26:A in the F28379D controlCARD).  The capacitor is not always needed, and has been shown to disconnect CCS in some circumstances while it's run in a system (such as high dV/dt or noisy systems).

    If (2), I would recommend analyzing what isolation you have in your system.  And adding isolation, if you don't have any implemented currently.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 140 points

    Dear Brett,

    Thank for reply

    I have LaunchPad. Actualy i am using VSI (with DC link capacitor ) with grid connected system. whenever sudden change is occure on grid voltage then LaunchPad is disconnected from CCS. Othervise system is working perfactaly i am able to change the varible values.

    As per describtions noise are occure on current but not in voltage.

    how i can resolve this issues    

     Thank 

    Pemendra 

  • 0 in reply to Pemendra Kumar Pardhi
    TI__Guru 57255 points

    Hi Pemendra,

    Thanks for those notes.  I would recommend looking into isolation. Where do you have isolation in your system, or do you not have it currently?

    • For example, is JP1, JP2, & JP3 on the LaunchPad populated? 
      • If they are populated, is the baseboard self-powered such that those jumpers can be removed?


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 140 points

    Dear Brett,

    Thanks

    I have provide the isolation between controller and switches by gate driver circuit.

    The LaunchPad is powered by PC through the USB cable.

    The JP1, JP2, JP3, JP4 and JP5 are not isolated. 

    How i can check the these JP are polluted or not?

    Give me suggestions

    Thanks

    Pemendra  

  • 0 in reply to Pemendra Kumar Pardhi
    TI__Guru 57255 points

    Hi Pemendra,

    Thanks for the additional information.  I believe I have a decent understanding of what your system looks like now.

    From being in your shoes, I can tell you that debugging this type of disconnection issue is difficult.  Most likely this is an EMI type event.

    Some thoughts:

    1. Computer to LaunchPad connection:  Make sure your USB cable is a shielded one.  I don't believe the ones we ship with this kit are shielded.  Instead you could add ferrite beads to improve EMI immunity, if desired.  I have seen this improve the robustness of the debugger significantly in the past.
    2. On the LaunchPad:  You can try to use an oscilloscope to capture the quality of the JTAG pins during the 'sudden change event'.  It might be difficult to isolate and determine root cause though.  Just be careful with your oscilloscope as you do this (VSI ground is not the MCU ground, etc).
    3. Use CAN, SCI or some other protocol to communicate to your host with (instead of JTAG).  It is likely to be more robust & tolerant to errors.
    4. If the 'sudden change event' is something like a relay being flipped, you may be able to utilize EMI shielding tape to help mitigate the problem so that the noise stays next to the relay.  If it's not something like a relay this may not help.



    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 140 points

    Thanks

    Dear Brett

    issue is resolved

    Thanks gain.

  • 0 in reply to Pemendra Kumar Pardhi
    TI__Guru 57255 points

    Hi Pemendra,

    For future readers that may have a similar problem & also my curiosity, could you tell which of these helped resolve the issue (or was it something else)?

    Glad that you've found a resolution!


    Thank you,
    Brett