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.

TMS320F28069M: TMS320F28069M

Part Number: TMS320F28069M
Other Parts Discussed in Thread: MOTORWARE

Before asking questions, I would like to thank you for your kindness.

I am using TMDSCNCD28069MISO controlCARD with HVMTP inverter board.

Not long ago, in an experiment, while removing a wire, the control card burned.
It is presumed that a short occurred by removing the wire without considering the capacitor.

Our team immediately prepared for the experiment again with a new control card(same model, different release version 0.4 --> 0.2, check with photo below).

However, the 'instaSPIN_MOTION_F2806xM.exe' program could not identify the motor.

The error message is

"C28xx: Trouble Reading PC Register: (Error -1142 @ 0x0) Device blocked debug access because it is currently executing non-debuggable code. Choose 'Rude Retry' to disable polite mode and force the operation. (Emulation package 5.1.73.0)"

The connection with the previous one was exactly the same, and what has changed is that the release version of the control card was changed from 0.4 to 0.2 and there is an accident, short, with overcurrent.

Therefore, we assume that the HVMTP inverter board to be damaged due to a short or different problem is needed due to a difference in the release version of the control card.

Attach a picture of the damaged control card and the new control card and the inverter board we are using.

The motor we were trying to control is a 350W IPMSM.

The short occurred in the process of removing the remaining wires after using and remove 220V AC as the power source.

  • Please use the external +15VDC power supply for providing the power to controlCard, and check if the +3.3V is good and the switch positions is correct on the controlCard. Go through the controlCard and high voltage kit user guides as below.

    instaspin_labs.pdf

    C:\ti\motorware\motorware_1_01_00_18\docs\labs

     

    readmefirst_instaspin_motor_kits.pdf

    C:\ti\motorware\motorware_1_01_00_18\docs\boards\kits\docs

     

    qsg_hw_cncd28069miso.pdf

    C:\ti\motorware\motorware_1_01_00_18\docs\boards\control\f2806x\docs

     

    qsg_hw_hvmtr_r1p1.pdf

    C:\ti\motorware\motorware_1_01_00_18\docs\boards\drive\hvkit_rev1p1\docs

    The explanation of this error together with some possible workarounds is shown in the following reference, and you may try to use Code Composer Studio to further debug the root cause of this problem.
    software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html