• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 81 subscribers
  • Views 62 views
  • Users 0 members are here
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.

Original question:

TMS320F28386S: Implementing XDS emulator to my board.

TMS320F28386S: Implementing XDS emulator to my board.

Nir Givon
Intellectual 340 points
Part Number: TMS320F28386S

As I asked in the previous question, I wanted to implement the XDS onboard.

TI's replay was that this should work with no issues.

Now I have the new board with the SDX and here is the error I get:

Error connecting to the target:
(Error -151 @ 0x0)
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.
(Emulation package 9.3.0.00042)

My guess is that the problem is that the EEPROM is blank.

How can I solve this?

Thanks!

  • 0
    TI__Mastermind 24750 points

    Hi Nir,

    Please take a look at following link and follow the instruction to reprogram EEPROM. Let us know if it resolves the issue.

    e2e.ti.com/.../faq-sticky-enable-xds100-usb-serial-port-on-launchxl-f28069m

  • 0 in reply to Santosh Jha
    Intellectual 340 points

    Thanks for the fast replay.

    After step 5: "Tools >> Read and Parse", I get the fallowing message:

    ERROR - Read EEPROM failed Device 0

    the option "Device -> Erase" is greyed out.

    How ever, if I only select "Tools >> Read"

    I get the fallowing print:

    Read EEPROM successful Device 0
    0000 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0010 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0020 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0030 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0040 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0050 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0060 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0070 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0080 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    0090 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    00A0 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    00B0 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    00C0 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    00D0 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    00E0 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..
    00F0 : FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .. .. .. .. .. .. .. ..

    So it can reed the EEPROM.

    Any ideas?

  • 0 in reply to Nir Givon
    Intellectual 340 points

    I used the fallowing case to resolve the issue

    (+) XDS100: Problem of MProg program eeprom to configuration FT2232H - Code Composer Studio forum - Code Composer StudioTm - TI E2E support forums

    I used the newer "FTProg" application and the template attached to the case to update the EEPROM.

    Now it works :-)

    Thanks!

  • 0 in reply to Nir Givon
    TI__Mastermind 24750 points

    Great!!

    Thanks for confirming that it resolved your issue.