• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 850 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.

TMS320F28335: Uniflash connection problem

Darko Trogrlic
Prodigy 250 points
Part Number: TMS320F28335
Other Parts Discussed in Thread: UNIFLASH

Hi,

I am having JTAG connectivity issues with TMS320F28335 on a custom board. HW is not the problem because until a while ago everything worked fine. I am guessing this is an issue with Uniflash or driver.

Currently working on Win10 (x64) with Uniflash 4.5.0.2056, using XDS200 USB Debug Probe. Error is:

[28. 1. 2020. 15:19:16] [ERROR] C28xx: 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 8.0.27.9)

None of the topics covered in http://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html seem to help.

Device manager says the drivers are up to date.

Do you have any idea how to debug this.

Thanks in advance.

  • 0
    TI__Mastermind 45046 points

    Hi Darko,

    I'd recommend looking at the App Note below. It is targeted specifically at C2000 devices:

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

    Have you tried using CCS to create a target config and test the connection on there? Might suggest that over Uniflash for debugging.

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 250 points

    Hi Kevin,

    Thank you for replying. I have been using CCS3.3 with XDS510 USB until recently when I could no longer connect to the device, so I decided to try using XDS200 just for programming the chip. Because usually when Connection with CCS doesnt work, the one with Uniflash and XDS200 works fine, and its good enough for programming.

    Today I borrowed XDS110 from a collegue, and it worked fine. So Uniflash + XDS110 works just fine.

    I opened the device manager and I think I see the problem:

     

    As you can see my PC looks at the XDS200 as an UART, while XDS110 is seen as TI debug probe.

    I went through the document you suggest http://www.ti.com/lit/an/spracf0/spracf0.pdf, and I found that this is a common problem, explained in "6. Reprogram Emulation Controller: This step ensures that the device that functions as the emulation controller has the correct firmware". 

    So, as suggested in the document, I followed the instructions from https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/21086, and this seems to explain only how it should be fixed for XDS100.

    My question is if the procedure is the same for XDS200, and if it is, can I use the same file (XDS100_wUART.ept) for XDS200.

    Thanks

  • 0 in reply to Darko Trogrlic
    TI__Mastermind 45046 points

    Hi Darko,

    Darko Trogrlic said:
    My question is if the procedure is the same for XDS200, and if it is, can I use the same file (XDS100_wUART.ept) for XDS200.

    I believe this procedure is only related to XDS100 debug probes. The XDS200 should not need to be reprogrammed.

    I would suggest installing the latest CCS version along with XDS200 debug probe support. Create a new target configuration for your respective device and debug probe, test the connection to verify it works within CCS, then try and connect and program.

    Best,

    Kevin