• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1034 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.

MSP430 emulator problems ("Error initializing emulator: Could not initialize device interface")

a b63478
Prodigy 20 points

Hi,

I have several problems with CCS (v. 4.1.1.00014) and the emulator.

First I tried to work with it on a Win 7 notebook but I couldn't get CCS recognize the emulator. The hints in this forum ("copy msp430.dll") did not work out.

Then I wanted to uninstall CCS. This didn't work either. And again there was nothing in the forum that could help me ("delete folder manually ... " lol.)

Now I have CCS on Win XP OS. This was okay for a while, however now (maybe one or two weeks later) I have the same error again and I really can't guess what's the problem. The MSP is okay and I don't think that the emulator is damaged because it is still listed in the device manager and windows makes a sound when the emulator is plugged in or out.

Reinstalling CCS didn't improve it, too.

Do you have an suggestions?

Thanks!

Markus

EDIT: I found out that the problem is related to a Microsoft Sidewinder connected via USB. I think there might be a address collision in some way, but I'm not sure. Anyway, the emulator works as long as the Sidewinder isn't connected.

  • 0
    TI__Guru**** 480021 points

    a b said:

    EDIT: I found out that the problem is related to a Microsoft Sidewinder connected via USB. I think there might be a address collision in some way, but I'm not sure. Anyway, the emulator works as long as the Sidewinder isn't connected.

    Thanks for following up with the cause of the conflict! This will help us in our investigations.

  • 0 in reply to Ki
    Prodigy 10 points

    Hi,

    I had the same error message this morning. I wasn't using any other USB ports but simply switching to a different port resolved the issue.

    Morgan