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.

EZ430-RF2500 Failed to initialize



Hello,

 Just got my EZ430-RF2500 kit and I am having problems getting the debugger to work. What i have done is the following:

1. installed the USB drivers from the CD
2. inserted the USB device. It detects and the driver installs.
3. Tested the Sensor Monitor that came with the kit, and it works like a charm.
4. Installed IAR embedded workbench kickstart
5. Opened and built the "Flashing the LED" project included with Embedded Workbench
6. Set the debugger connection (project->options->FET debugger->setup->connection) to "Texas Instruments USB-IF" (have also tried LPT-IF to no avail)
7. Selected "msp430x2xx (asm - SpyBiWire)" as active (also tried "msp430x2xx (asm)")
8. Started the debugger (Project->Debug)

This just gets me a "Fatal error: failed to initialize. Check if hardware connected (etc)." Restarting the PC and re-plugging the USB dongle has no effect.

I have tried this both with the MCU board that came with the EZ430-RF3500 and with the small EZ430-T2012 boards, though still with the RF2500 USB dongle.

I do this on a regular HP desktop pc running Vista with the latest service packs. Looking elsewhere in the forums (https://community.ti.com/forums/t/329.aspx) it seems there might be a conflict with another USB driver, but I have tried disabling all HID drivers that can be disabled and still get the same result (I do indeed have a HP remote control, though I can't see which one is the driver for that). Looking in the Windows Device Manager when I plug the USB dongle in, I get two new devices: Ports (COM & LPT)->MSP430 Application UART (COM3) and Universal Serial Bus controllers->USB Composite Device.

 Is there any way to see if there actually is a conflict, or could it be something else? And what's up with the COM3 driver? (Disabling it does not help.)

  • Oh, the Embedded Workbench version is:

     IAR Assembler for MSP430
    V4.11B/W32 (4.11.2.9)

  • This just in: It works when I downgrade to

    IAR Assembler for MSP430
    V4.10E/W32 (4.10.5.9)

    so I don't suppose it's got anything to do with the drivers, at least.

  • I have a similar problem and I know mine is related to drivers. I have two computers: a desktop with few usb devices attached and a laptop that has had more USB stuff installed, uninstalled and reinstalled than I can remember. The desktop works flawlessly with IAR 4.11B. The laptop worked previously with 4.11B. Then I had to reconfigure some things due to a conflict with Bluetooth drivers and virtual com ports. I've got everything working except for the EZ430. Going to Project->Options->FET Debugger and checking the USB Selection it shows HID0033:COM3. My Bluetooth drivers have already claimed COM3 and I can't seem to change that. So my question is: How do I change the com port that the EZ430 driver uses? I've searched all the configuration places I can think of. I've uninstalled and reinstalled, etc. Any insight would be appreciated.

  • i presume you have an HP latop. if you do you need to go to the device manager and uninstall the HP quick launch buttons under the human interface devices tab. this helps in removing the error message. IAR downloads the code onto the ez430 and then hangs.

     

    If you use CCS it seems to work absolutely fine after uninstalling the driver. Please note that every time you restart your computer the HP quick launch button will automatically resintall itself. so i think you may need to remove it permanently. i am looking for a solution to make IAR work

  • I think it problem with the USB drivers bcoz I to got the same problem in the beginning and solved it after reinstalling the demo software

  • Hi Jon,

    I have the same problem with you. I'm using the HP laptop.

    What I did is to go to the device manager and uninstall the HP quick launch buttons under the human interface devices tab. this helps in removing the error message, and the project works.

**Attention** This is a public forum