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.

Compiler/TMS320F28069: Control Stick hardware Gets Hot.

Part Number: TMS320F28069
Other Parts Discussed in Thread: CONTROLSUITE, LAUNCHXL-F28069M,

Tool/software: TI C/C++ Compiler


Hi everyone, this is Mike.

I made my own PCB based on the Control Stick F28069, it is already out of the market. It went well at the beginning. Connecting to the PC, downloading the firmware and so on, but then, after one hour of working with it, it began to get hotter and hotter that, in some briefly time, it started to disconnect from the PC. Gets too hot and Code Composer Shows the next message.

Error connecting to the target:
(Error -1015 @ 0x0)
Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 7.0.100.0)

If it is cold then I can work with it but just for one or two minutes

I have read around this forum and I think I'm not the first one with this problem, but couldn´t find a reason (just replacing the controller and the LDO) but I wanna know if that circuit schematic, found on ControlSuite ( C:\ti\controlSUITE\development_kits\F28069 controlSTICK\~F28069controlSTICK_HWdevPkg\R1) is so sensible so I have to be aware ESD, or if do I have to put many no used GPIOs, to ground?

LAUNCXL-F28069 works the same application with no error, a little hot but it seems pretty stable. I checked with many care my circuit so I'm pretty sure it is ok with the routing.

I'm afraid to assembly my PCB again, with new components, and then it fails. So I have to know how to take care assembling this microcontroller.

I have worked with other microcontroller the same way and nothing has happened.

Please some help!

Regards

Mike

  • Mike,

    Is it possible that during board assembly a resistor was soldered instead of one of the de-coupling capacitors?

    Regards,

    Peter

  • Peter

    Thanks

    Not really, it has the next shape, it downloads the firmware, it runs pretty well, after one hour it blowed up

  • Peter

    Is it possible to get it hot by firmware?

  • I've re-assemblied my PCB with an old TMS320F28069PN that I had (while the new one is coming)

    I found the next:

    • It  connects to the pc and downloads the firmware in a good way.
    • It starts to get hot when the code is running (42 °C ,107.6 °F)  with no circuit connected to this circuit.

    The other circuits tied to this pcb works properly as they passed the testing production procedures, but I'm not gonna test the whole project, I think I'm gonna connect lead by lead to see if it something else (maybe the harness or the bad weld)

    My question is:

    Can the code make the circuit to fail if it is a lot of data proccesing? I am doing RMS algorithm, a frequencymeter, a menu with a LCD 16x2 and two relays at the output.

    We tested the other circuits with the LAUNCHXL-F28069M and it reaches 35°C (95°F) with the same code

  • Mike,

    These temperatures are too hot to be generated just by running code. I suspect you must have a short somewhere that is drawing a lot of current. One of the possible causes could be a short on of the GPIOs. Could you measure the current going into the device?

    Regards,

    Peter

  • Here at the lab we have this temperature: 31°C, 87.8 °F. It is hot, Summer is coming (xD). I have run my application. With those temperatures I reported in my last comment ( 42 °C ,107.6 °F ) the microcontroller TMS320F28069 has a deviation from the ADC, it is little but I think could be a problem. I think I cannot measure the current now, since the PCB is mounted in the cabinet it is supposed to be.

    I will report this current when the new TMS320F28069 arrives.

    Thanks for your attention to this, Peter

    Mike

  • The FTDI was shorted out inside

    Regards

    Mike

  • Mike,

    Thanks for the update,

    REgards,
    PEter