SparkFun Forums 

Where electronics enthusiasts find answers.

Discussions on how to get your MSP JTAG programmer up and running.
By harlem
#26565
When I finished to install IAR 3.42A, I overwrite the TI drivers with the OLIMEX v1.011, then I started the workbench and I choose the "Texas Instruments USB-IF" debugger option and when I going to begin a debug session, the program said if I want to update the FET firmware version.

First, I said no, but it didn't start the debug session, when I repeat the operation and when it ask the same question I said yes and it start a upgrade process that finished with and error, and debug didn't start.

After that, went I try to start a debug session the program says "No device found or is disconnected".

And now, went I try to use the "Elprotronic MSP430 Flash Programmer Lite" (with the OLIMEX driver) it also say "MSP430.dll initialization error. Check Comunication port setup"

But, the standalone firmware that can read and program microcontrollers is still working! But it don't connect to PC!

Is the MSP430-JTAG broken?
Can I restore the firmware to a previous version?
Can anybody help me, please?
By Bill_Ewing
#26613
I too have the same emulator, the Olimex MSP430-JTAG-ISO and I am using the free IAR KickStart IDE.

Like you mine doesn't work either.

But I think I see at least one thing that might be amiss for you. The message "Check Comunication port setup" sounds like it is for the serial port or parallel port version of the tool, not the USB tool (MSP430-JTAG-ISO) you indicated.

I will be watching to see what kind of help you get, and you should watch my forthcoming posts in case they help you.

Good luck,
Bill
By harlem
#26635
Oh yes, the MSP430-JTAG-ISO has a USB connector.

The message "Check communication port setup" is because the "Elprotronic MSP430 Flash Programmer Lite" can also work with the parallel version and it think that I configured it with a bad option because it can't initialize the JTAG, attached to USB port and it suggest to revise the setup to change the port for a parallel version.

I think that firmware of JTAG is corrupted and it happened in the IAR workbench v3.42 upgrade process.

I send a mail to Olimex but, by now, I don't have any answer.
By harlem
#26645
The firmware is well!!

I finally configure well the "Elprotronic MSP430 Flash Programmer Lite" and it works.

But there are an incompatibility with IAR Workbench.

Can anybody run it with IAR Workbench?
By harlem
#26653
Thanks for your attention Tsvetan,

but after some time of tests I don't be able to solve the error:

"Runtime Error!

Program: ...R\ Systems\Embedded Workbench 4.0\common\bin\IarPm.exe
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
"


BUT!!! I rescued the Olimex v.1.00.4 version from my hard drive!!

And eureka, it works fine!

I don't know, why it happens, but I can't work with 1.011, perhaps the problem is my computer but I see in the forum that I'm not alone.

For that persons that have the same problem, they can download the old version driver v1.00.4 from this direction:

"http://personales.ya.com/harlem/OLIMEX MSP430 USB drivers 1.00.4.zip"

I hope so, that it future revisions of the driver, the problem was disappeared.
By bmckenney
#32159
Here's another data point -- maybe it will help someone:

I am using IAR 3.42A (Kickstart) with

1) an Olimex MSP430-P1611 board, programmed with USB-JTAG-Tiny and
2) a TI MSP-TS430DA38 board, programmed with a MSP-FET430UIF (USB)

When I installed IAR and the P1611 (Olimex drivers 1.011) some months
ago, I concluded after some mix-and-match that there seemed to be a
version conflict focused on two files in [IAR]\430\bin: HIL.dll and MSP430.dll

IAR 3.42A included these files, dated 06-Dec-2006, but the Olimex driver
set included these files, dated 13-Oct-2006/31-Oct-2006. Now that I have
the TI board, I've concluded:

1) The USB-JTAG-Tiny Requires the earlier (Olimex) versions and
2) The TI USBFET Requires the later (V3.42A) versions of these files.

The symptom is a rather bland "Cannot initialize" message box.
Flipping between these two versions is a bit inconvenient but workable.
One solution might be to define a separate IAR programmer device, but
I don't know how to do this.
#34619
Well, I could echo bmckenney's entry, the difference is that I'm using a brand new (this should work) MSP430-1121STK2 and brand new (this should work) USB-JTAG-MSP430-Tiny from SparkFun/OLIMEX.

Since this is a SparkFun/OLIMEX forum, one would think the SparkFun/OLIMEX folks would read the entries. And, after having read them, you'd think, as cool as they and their products are, they would have had a fix/circumvention published here by now for this serious problem.

Wouldn't you think?
By OLIMEX
#35722
Marvm:
in our lab we have 15 computers and on all of them is installed EW-MSP430 kickstart revision 3.42 and on all of them MSP430-JTAG-ISO and MSP430-JTAG-TINY are tested/works and are used daily.
If something doesn't work on your computer, please check what other MSP430 software you have installed - from other customer reports I understand that Elprotronic software installed on same computer mix up the MSP430.dll paths .dlls and may cause such problem - reported by customer who after deleting Elprotronic soft and re-install of EW-MSP430 and our drivers managed to get it working, another issues I've read on Russian language forums is that same result may happend if you use "cracks" or keygens for IAR Workbench - it starts crashing.
We simply can't reproduce the results written in this post - none of our computers make problems with none of our debuggers, so it's very hard for me to give suggestion or advice.

Best regards
Tsvetan
By jradomski
#35737
OLIMEX wrote:Marvm:
in our lab we have 15 computers and on all of them is installed EW-MSP430 kickstart revision 3.42 and on all of them MSP430-JTAG-ISO and MSP430-JTAG-TINY are tested/works and are used daily.
If something doesn't work on your computer, please check what other MSP430 software you have installed - from other customer reports I understand that Elprotronic software installed on same computer mix up the MSP430.dll paths .dlls and may cause such problem - reported by customer who after deleting Elprotronic soft and re-install of EW-MSP430 and our drivers managed to get it working, another issues I've read on Russian language forums is that same result may happend if you use "cracks" or keygens for IAR Workbench - it starts crashing.
We simply can't reproduce the results written in this post - none of our computers make problems with none of our debuggers, so it's very hard for me to give suggestion or advice.

Best regards
Tsvetan
Never had any problems with the elprotronic software if the install directions are followed.. Their software alows the user to choose which interface they wish to use by a dll switcher dll.. The best thing to do befiore installing ANY other jtag interface (anyting but ti) is to archive the current dlls, and trachk all dll installs.. software like elprotonic and crossworks can easily work with multiple jtag interfaces.. with the proper setup so can IAR software..

for automated programming its hard to beat the elprotronic software..
User avatar
By leon_heller
#35738
I'm using the MSP-JTAG-TINY with IAR 3.42 on two PCs without any problems.

Leon
By OLIMEX
#35739
I just pointed out something based on our customer feedback

I'm sure that if installed properly every software will behave as needed, you just have no idea what some peoples are doing :)

I do remember few years ago we had call that our PIC programmer doesn't work, after asking any possible questions like cables, power supplies etc etc I just asked for the code the customer wanted to burn in the PIC so we can try to reproduce his problem in our lab - he sent me blinking LED code on HTML web page, and he was trying to program the HTML web page in the PIC and wondered why the LED doesn't blinks

many of our customers are beginners and when they write "your board doesn't work with XYZ software" I'm prepared to expect everything :)

Best regards
Tsvetan