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.
For a while I have been using the version of IAR workbench that came with my kit (ver.4) without any problems. I recently tried to upgrade to the latest version available, 4.21 (slac050v) primarily because I intend to move towards targets not supported by the older version.
Since then, I am unable to download any code to the boards and debug it. The code assembles and links fine (I use assembler only), but the debugger gives me an error message saying it cannot communicate with the device. I use the TI USB FET that came with my kit, and which works fine under the older IAR version. Same hardware, connected in the same way, doesn't communicate with the new version of the software. I tried every single option available under options/FET debugger to no avail. The devices listed are "Automatic" and "HID0006". Either of them selected doesn't work (in the older version, if either was either selected downloading/debugging worked fine)
What am I missing?
I have now verified the problem on multiple computers, with various operating systems (XP, Vista, Win7). It is perfectly reproducible. The error message in all cases is:
"Fatal error: Failed to initialize. Check if hardware is connected. Check if drivers are installed. Try to restart the computer. Tools using the parallel port are not supported on Windows Vista Session aborted! "
The problem isn't solved even by installing the latest MSP430.dll and HIL.dll from http://wiki.davincidsp.com/index.php/MSP430_JTAG_Interface_USB_Driver
This is a showstopper bug for me.
I have verified that the problem is indeed in one of msp430.dll and/or hid.dll
By copying the old versions of these libraries over the newer version of the software, it works again.
FWIW I copied over msp430.dll and hil.dll from \Program Files\IAR Systems\Embedded Workbench 5.0\430\bin to \Program Files\IAR Systems\Embedded Workbench 5.4 Kickstart\430\bin
The details for the working files are as follows:
msp430.dll size 225280 date 2/14/2008 version 2.3.3.0
hil.dll size 32768 date 2/14/2008 version 1.2.2.0
The non-functioning versions are 294912 and 32768 bytes respectively, date for both is 9/22/2009, versions 2.4.1.4 and 1.2.6.0. Also the newest versions downloaded from the site in my post above are non-functional (versions 2.4.2.0 and 1.2.6.0 respectively).
BTW I will not verify this as an answer since it's not a real solution, it's a kludge.
Hello,
I don't have an old version of the two files mentioned.
Could you provide this files?
Thanks
Timo
I'm not sure if I have the right to redistribute those files. But if I did (wink) I would probably use a file hosting service, such as http://www.mediafire.com, followed by a random string, such as "/?mu04lywjhmj" (wink).
Greetings
This is great news! I am just learning this product and embedded systems and have spent soooo much time just trying to get the tools working. I am running a vista 64 bit machine after my XP 32 bit machine traveled south. I had to revive the XP machine in order to be able to communicate with the msp430 ez rf2500 and then only with the older iar kickstart (ver 4.1). I just uninstalled all the versions of workbench and will install the new version (4.21.8). See http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/165/t/31674.aspx Is this the "newest" version you are referring to that still needs the older dlls. Thanks for all your research. I had shelved this endevor for some time in order to resurrect my 32 bit machine and frustration.
Happy Trails
Bryant
Shenle! You rock. Thank you for tracking this issue down and for ah -not- providing a solution!
just a heads up to anyone that might run into this thread....
the dlls that are mentioned above are updated very regularly, so the dll download mentioned above is very outdated. if you want the latest and greatest versions of the dlls, they're included with CCS and IAR. their exact directory paths are mentioned here: http://processors.wiki.ti.com/index.php?title=MSP430_JTAG_Interface_USB_Driver.
as of today, the latest msp430.dll is v2.4.4.0 so make sure that you're using this version or newer if you want support for all devices and the newest features.
adrian,
I seem to be having the same problems that you have experienced in the past and was wondering if you got a workspace in IAR working. I have been pulling my hair out since I installed the new 4.21 version and would really appreciate it if you would give some guidance or let me have an eww file to try out.
Thanks,
Jeremy
Dear adrian,
The new latest and greatest versions on the dlls posted on the site both you and I referenced still don't work. I will keep using the old, very outdated but functional versions I'm using now.
Also, thanks for removing my comments from the MSP430 JTAG Interface USB Driver page. No need to confuse anyone who goes there by making them think that thew downloadable dlls may have issues with compatibility. Right?
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
Hi shenle,
Using a two year old DLL is not really a solution. But have you ever check if you have installed the newest USB VCP drivers? The DLL you use was made to work with no certified USB drivers. In the meanwhile we changed the driver to a certified one. If you now take a new DLL and try to run in it with an old driver version it won’t work.
Perhaps you could check your driver version or install the new VCP drivers.
Regards Florian
I've had the same problem -- version 4.21 just doesn't download to the device. TI's debug interfaces for the 430 have always been extremely unreliable but now I can't get it working at all, so I've been having to use AVR parts on new designs and trying to maintain old products with older versions of IAR.
Previously when IAR said no device was attached I could sometimes get it to work by unplugging the USB FET (which was in some locked up state where the red and green LED were running), restarting IAR, and power cycling the target. Now, nothing.
**Attention** This is a public forum