TMDSSOLARPEXPKIT: My Solar Explorer Kit board is not responding after connecting AC source while testing the Build 3

Hi Yue,

From your screenshot it looks like CCS could be losing connection to your board through the USB JTAG interface. I think this should be the first thing to check.

Your board may still be running after CCS loses connection. After losing connection probe the PWM output and see if a signal is still present. If a signal is still present and everything seems to be operating OK, it may be a JTAG issue.

Is your USB cable shielded to prevent EMI? Signal interference could be causing your JTAG interface to lose connection.

Additionally, have you read through the document related to the example program you are using on ControlSuite? Check your configuration with the "HW Setup Instructions" in this document.

Directory: C:\ti\controlSUITE\development_kits\SolarExplorer_v1.1\SolarExplorer_PVInverter_F2803x\~Docs

Best,
Kevin

Hello Kevin,

Now when I started the demo, everything is connected, by this I mean I could check the variable in real-time using "continuous refresh". Only when I write "1" to ClearInvTrip then it started disconnecting. By the way, I know how the demo should be running like since I have already gone through the whole process before successfully. The JTAG is losing connection, but it's connected when I started it. I am sure JTAG connection was fine when I started the debug (I mean after pressing F8 in debug mode,not building the project), so I think it's not a JTAG setting or JTAG port issue. The lost of connection must be caused by other problems other than the connection itself. About USB cable shielded possibility, I think it's zero because of the same reason I stated above...

BTW, I have read HW guide as well as the document included with the demo. As I said, I have run the demo successfully before... 

Thank you.

Best,

Yue

To better describe my problem, before test, I have rebooted the board, reset the emulator and reload my programs already. Below are the error messages shown:

C28xx: Error: (Error -1135 @ 0x3F60CE) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.48.0)
C28xx: Unable to determine target status after 20 attempts
C28xx: 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

Attached is the screen recording video of the whole experiment.

Hi Yue,

That error appears because the JTAG is losing connection during debug after setting those values and stepping up the inverter. Have you tried performing the test with a different cable to make sure it is unrelated? One with shielding would be recommended to rule out the possibility of any interference from the inverter starting to cause the emulator to lose connection.

For build 1 did you try probing the PWM output after this disconnection occurs to see if the C2000 is still running without issues? This will help us understand if the system is still operating after the disconnection occurs or if a trip is causing the system to halt.

Best,
Kevin

Hello Kevin,

Thanks for your reply, I have tried using another cable already, yet the result remains the same.
About the PWM, in build 2 and build 1, when disconnection occurs, it's outputing no waveform by oscilloscope. Furthermore, multimeter shows no AC/DC voltage outputs in corresponding output ports.

This occurs to me that when I was testing the build 3 in grid connected mode, I accidentally connect the AC side to the variable AC voltage source at somewhere 50 volts, although I did not notice anything particular and shut it down immediately after found it out, I thought everything should be fine, but thinking back it might have caused some problem.

Best regards,
Yue

Hi Yue,

If you noticed the board not working after this accidental connection, something on the board may very well be damaged. If you are up for it, you could try (carefully) probing the FETs and components that are related to the inverter as a starting point, since that seems to be where the issue resides. If you notice anything that is shorted replacing the part might do the trick.

Hope this helps,
Kevin

Hello, Kevin,

Thanks for the reply, I have tried finding the damaged parts, however I still cannot find which part is damaged. Is there a way that I can send you the board to Ti and have it repaired?

Best regards,

Yue

Hi Yue,

I'm sorry you are having trouble tracking down the part causing issues. Unfortunately that is not a service TI provides nor can we provide a replacement at this time, being that the board was previously in a working condition.

Best,
Kevin