• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 615 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/TMS320F28069M: error connecting to target with XDS100v2 usb emulator

Motor_Enthusiast
Intellectual 820 points
Part Number: TMS320F28069M
Other Parts Discussed in Thread: UNIFLASH, LAUNCHXL-F28069M

Tool/software: Code Composer Studio

I am using XDS100v2 usb emulator for debugging and programming of TMS320F28069M device.

In some o the boards there is no problem in programming and debugging but in some of the boards I get the following result:

Error connecting to the target:
(Error -1135 @ 0x0)
The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
(Emulation package 6.0.628.3)

Also in one of the boards I can read and program the device with Uniflash but it is not possible with Code Composer Studio. 

I am confused and it is hard to understand why does that such a problem occur in some of the boards? (The components and schematic is exactly the same for all boards)

Best regards

  • 0
    TI__Guru* 80640 points

    I would look at the configuration of the boot pins shown here:  http://www.ti.com/document-viewer/TMS320F28069/datasheet/boot-rom-litsprs698-0453#litSPRS698-0453  

    To ensure stable connection to the emulator you will want to put the device into Wait boot mode.  I suspect that some devices are running code from a secure region of memory when you try and connect and this will not allow the emulator to connect.

    The F28069M is unique in this regard in that there are some areas of ROM that have the InstaSPIN code and it is secure from the factory.  So, even if you do not have the security module (CSM) enabled this will be still be in effect if that code is in use.

    Let me know if this stabilizes things across all units.

    Best,

    Matt

  • 0 in reply to MatthewPate
    Intellectual 820 points
    In my schematic GPIO37/TDO has a pullup with 10k, TRST has apull down with 2k2 and GPIO34 is an output with default position set to Low. I also connected GPIO34 to GND with a cable. But unfortunately, this did not solve the problem.

    With my colleague's computer we can download code to the mcu, he does not have any problem. After he downloads the code to the MCU, I can also download code with no problem to the same mcu. But with a fresh MCU with no code inside I cannot download the code with the problemmatic mcus. This seems to be a bit more strange. What could be the reason?
  • 0 in reply to Motor_Enthusiast
    TI__Guru* 80640 points
    Are you using a TI based EVM, i.e. F28069MCNCD or LAUNCHXL-F28069M? Or is this a custom board?

    I a colleague's computer worked I would look at any differences in the ccxml or CCS settings. Is there an external emulator involved or is it on the EVM?

    Matt
  • 0 in reply to MatthewPate
    Intellectual 820 points
    I am using my own board but we have made the schematic according to TI demo board. For the emulator I am using XDS100v2 usb emulator and it is our design with FTDI chip. There are no differences in settings in my colleagues computer. Moreover, it is strange but in some boards he also had same problems some time ago, but now he did not have such problem.
  • 0 in reply to Motor_Enthusiast
    TI__Guru* 80640 points

    Thank you for the updated info, metastability is always one of the more difficult issues to root cause given the "on/off" nature of the failure.

    I'd like to take a step back and use the following app note to diagnose the issue when it occurs again:

    http://www.ti.com/lit/spracf0  

    By noting in which stage of the flow chart we can get to it will help point to the pontential problem at bit quicker.

    If you could reply back with the information outlined in the app note we can go from there.

    Matt

  • 0 in reply to MatthewPate
    TI__Guru* 80640 points
    Wanted to see if you had a chance to review the document referernced in the above post.

    Best,
    Matthew