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: TMDXIDDK379D connection failures

Part Number: TMS320F28379D
Other Parts Discussed in Thread: TMDXIDDK379D, TMDSCNCD28379D

Good morning,

I am using the C2000 Design Drive Kit TMDXIDDK379D with the supplied e-machine.TMDSHVMTRPFCKIT.  As specified, I imported the project TMDSIDDK_v2.0\IDDK_PM_Servo_F2837x, and was able to run it up to 2nd compile level.  In the 2nd compile level I was able to connect (with a lot of trying) and set parameters and turn the motor open loop.  The problem is that the connection constantly fails after a very short time. (I am assuming that it is a communications failure)   Further, reconnecting is also difficult with many failures.  As it stands now, the development kit is not usable for the purpose intended because of the difficulty in starting the program and the subsequent frequent failures.  I am connected to a fast computer so that should not be an issue.  I am wondering if there are some settings that would make the system more robust for continuous use.

thanks

  • Is your debugger disconnecting from the target board? What is the dc voltage feeding into inverter?

  • the error messages appear in red and say can't read variables.  I am powering through ac power port.

  • If possible, use a variable dc power supply with a current limit and try it out. You can go back to AC power when all your tests are done and probably use it for standalone operation if needed.
  • Imre,
    I'd like to understand if we are dealing with a debugger loss of power or a loss of power to the F28379D. When running and debugging can you comment on the status of the LEDs on the TMDSCNCD28379D control card?

    LD1 indicates the control card is powered, A:D1 indicates the XDS100v2 emulator is powered.

    The emulation on the control card gets its power through A:J1, USB connection and is isolated, so it should be somewhat immune to noise from the kit.

    Have you been able to try as Ramesh suggested with only DC input to see if that helps?

    Matt
  • good morning,

    I am compiling level2.  

    LD1 is always on

    A:D1 is lettered on board but never goes on (do not see the actual led)

    A:D2 next to A:D1 (green) is always on

    Just before the loss the blue LEDs A:D3 and A:D4 (blue) turn on momentarily.

    No I did not try the DC power supply yet.  It is a bit troublesome because I will have to relocate.  If no other thing to try, I will do it.

    thanks,

  • Just to further elaborate, on failure the Expression window shows this for all variables:

    IsrTicker unknown Could not read 0x0000B018@Data: target is not connected

    SpeedRef unknown Could not read 0x0000B03C@Data: target is not connected

    ......

    And the Console error messages are:

    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.0.803.0)
    IcePick_C_0: Unable to determine target status after 20 attempts
    IcePick_C_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
    C28xx_CPU1: Error: (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 8.0.803.0)

    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

    This happens almost immediately after proper execution begins.  With this going on, the development system is not usable.

    Imre

     

  • Imre,
    You were correct, A:D2 is the emulator power was a typo on my part. If all these are lit, even during the run, then we most likely don't have total power loss.

    I would like to confirm the following:
    1)Currently you are on build level 2, was build level 1 working/trouble free before you switched to 2?
    2)On page 15 of the IDDK UG, the build configurations are shown and RAM configuration is suggested for debug; can you confirm you are in RAM config vs the Flash config?

    Best,
    Matthew
  • Matthew,

    I am in level 2 but level 1 had similar issues.  I confirmed that I am in RAM conflagration. 

    Unfortunately I also had a disaster of sorts.  Component RT1 sparked and blew in the power section.  Motor was not running.  I am now looking for an external power supply that I can use at my desk.  Hopefully nothing else fried.  Some days ago I did look at the DC bus With a high voltage probe and it looked pretty clean.

    Thanks,

    Imre

  • Imre,
    Wanted to see if you were able to supply the DC directly or otherwise?

    Matt
  • Matt,

    Apologies for not getting back to you sooner. When I applied the DC directly it became apparent that the board was fried. The DC supply showed over current on application of power. I may try to repair it sometime in the future but I can’t devote any more time to it now. We are building a SiC based inverter from scratch and am waiting for boards to come in. We chose this processor for the computing potential but kind of underestimated the resulting complexity.  Rough learning curve.  I will have to do my experimentation on the incoming hardware. Thanks again.

     

    Imre

  • Hi Imre,

    I agree that there is a lot to this processor & that the ramp can be challenging.

    I did want to make you aware of our Multi-day Workshop which is built around the F2837xD.  It explains the device, its features and provides some lab exercises for learning.  It may be a good investment of time to go through, or at least be a good resource to reference.
    http://processors.wiki.ti.com/index.php/C2000_Multi-Day_Workshop


    Thank you,
    Brett