• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 958 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/TMS320F28027F: Problem detecting/flashing MCU with XDS100V2 debugger

Simo Sihvonen
Intellectual 300 points
Part Number: TMS320F28027F

Tool/software: Code Composer Studio

Hi,

I have been evaluation the instaSPIN platform with the DRV8301-69M-KIT (with F28069M/F control card) and adapted that design to a non-commercial own design, except it uses the TMS320F28027F. The partly assembled board with the 3V3 voltage and XDS100V2 debugger connected is pictured below. Currently the board has only the necessary component placement for flashing and debugging testing where I'm stuck at the moment.

I have attached below the schematic from EAGLEcad, which shows the connections between the MCU and the debugger and the part from the "SPRS523K" document on what the connection is based on.

The real problem is that as a newcomer to the CCS, I'm still a bit lost around in it when it comes to making new target configurations and flashing bare bones MCUs. First problem is that I created a new target configuration for the XDS100v2 usb probe, but couldn't actually find the F28027F MCU on the device list. Only the F28027 or F280270. I did see the M and F variants for the F28052/54 MCUs, so I'm not sure if my target device is even correct.

Then as I try to debug the board with the lab_10a exercise from motorware for the drv8301kit using a f2802xF, just to try flashing the MCU (It's not going to do anything of sense of course as my schematic is different). But just work as a hello world for the flashing and debugging. As I try to debug I get the plethora of warning messages shown in the picture below. Which shows that I have the wrong device selected and for some reason the MCU is held in reset.

Hopefully with this info we can start to figure out how to solve this

  • 0
    Intellectual 300 points

    Just discovered a possible fault. I had pulled VREGENZ low, but had mistakenly left the VDD pins connected to the 3V3 line like the VDDIO. After cutting a trace on the on the PCB and isolating the VDDs from the 3V3 line, but still had 2u2 ceramic caps on them between ground. The VDDs then had only 0.7 Volts at them, so I assume the internal regulator is broken, because according to datasheet the voltage should be 1.9 Volts at the VDDs with VREG enabled. Also while the faulty connection wasn't fixed yet, the XRS pin had steady 0 Volts, even with a pull-up 4k7 resistor to the 3V3 line. After the fix, it only floated up to 1.45 Volts and this seems to me the internal regulator is busted. Does these functions make sense with the knowledge of the mixed up connections?

    Luckily I have a backup MCU, so I'll change it out.

    EDIT: Yep, the chip is fried, as the max voltage at the VDD pin is 1.995 V. Also it turns out there has been a labeling/packing mistake with my order from the TI store, as my other F28027F anti-static bag contained a PCM2707 USB DAC chip. This issue has been solved by the TI support.

  • 0 in reply to Simo Sihvonen
    TI__Guru 57255 points

    Hi Simo,

    I'm glad you were able to trace down the issue.  Thanks for following up with what resolved the problem.

    Good luck in your project!


    Thank you,
    Brett