• Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 2199 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.

XDS100V2 on Pandaboard

jyothi K
Prodigy 20 points

Hi,

I am trying to debug the Pandaboard ES (OMAP4460) using XDS100v2 emulator. I have created target configuration file selecting the processor as OMAP4460 and am able to build the hello world project using the created configuration file but am unable to debug hello world application using XDS100V2.

I am getting the following error as shown in snapshot please help me in this context.

Thanks,

Jyothi

Tenet Technetronics

  • TI__Guru*** 130875 points

    Hello,

    did you try installing the FTDI drivers separately?  We have seen some instances where this has unfortunately been necessary.

    Best Regards,

    Lisa

  • in reply to Lisa TI
    TI__Guru*** 130875 points

    A few further things to check.   Did you install the XDS100 drivers along with CCS?  Can you verify your XDS100 is correctly programmed?

    Best Regards,

    Lisa

  • in reply to Lisa TI
    TI__Guru*** 130875 points

    Hi,

    just wanted to check whether there were any updates to your enquiry.

    Best Regards,

    Lisa

  • in reply to Lisa TI
    Prodigy 20 points

    Hi Lisa,

    I installed XDS100 drivers along with ccs. I even tested the connection of Jtag to pandaboard using the test connection it works fine, the above problem occurs only when i debug an application (C application). Can you please give me a correct way to install ccs as well as XDS100 drivers and debugging an application  from the beginning  if i went wrong above.

    Thanks,

    Jyothi

    Tenet Technetronics

  • in reply to jyothi K
    TI__Guru*** 130875 points

    HI Jyothi,

    hmm one of the only thoughts we have at this time is ... are you inadvertently already running Linux on the board?  This has been know to cause some issues when connecting to the core.

    Best Regards,
    Lisa