Problems using MSP-FET430UIF

John B said:

"The procedure entry point BZ2_bzBuffToBuffDecompress could not be located in the dynamic link library LIBBZ2.dll"

hi John, in the many years that I've been working with the MSP430 I can honestly say that i've never seen that error before.  congrats!  Assuming that you've correctly connected the FET to the MSP430, I *think* that the firmware upgrade failed and the FET is having troubles talking to the target.  one way to check this is to "upgrade" the firmware on the FET firmware to an different version.  You could try installing another another MSP430 software tool (like the Elprotronic FET-PRO430) which will also attempt to upgrade the firmware when you first use it.  if all goes well, your FET will be restored and you should be able to try again with CCS.  

if that doesn't work, try reinstalling CCS.  and if THAT doesn't work, call TI support and tell them your FET is broken and get a new one.

fyi... the XDS560 driver is completely unrelated to the MSP-FET430UIF.

Hi Adrian,

Thanks for the response.  I downloaded the Elprotronic FET-PRO430 LITE version and tried updating the firmware from there, it updates the firmware to v2.04.03.000, if I then go to CCSv4 and try to Debug Active Project it says I need to update the firmware, it updates to v2.04.04.000 and then I get the same error.  In CCSv4, when I Debug Active Project, the progress information window comes up and after a few seconds says I need to update the firmware, I click on update and it updates, seems to complete (the progress bar reaches the end and it says it's in the finishing stage) then in the details section of the progress information window the updating stuff disappears and it says "no operations to display at this time" then after a second or two the dynamic link library error pops up again.  However, it does seem to update the firmware fine in both cases, when I try and program through Elprotronic it fails the verify security fuse check and JTAG initialization... is it possible that the chips fuse is already blown?  I'm in the process of soldering up another chip to a new board to test that theory and will reply again with the results of the new chips test.

Well the 2nd chip and board came up with the same error.  Tried reinstalling CCS and again the same error occurred.  The chip is on a PCB, the 4-wire JTAG circuit is on a breadboard, everything looks fine so we're unsure what the issue is.  I don't think this would explain why the Elprotronic software didn't work,  but I'm using CCSv4 on the college's computers which also have CCS v3.1 Installed on them; CCSv3.1 is installed on the same drive but a different folder completely though I'm not sure if it could still cause any conflicts or not.  I can't recall off the top of my head why the school uses v3.1 but when we used it last year the instructor said it had something they use that the newer versions don't have, so I'm not permitted to uninstall the older version to see if it changes anything.

Unfortunately due to time constraints we've had to switch to a different MCU we're more familiar with, while not necessarily the most ideal choice for out project it will suffice.  I may come back to this after this quarter finishes to see if I can figure out what the issue was.  Thanks a lot for your help though, I do appreciate it!

- John B

Hi Jonh B...

Did you try to program your chip with IAR workbench?

in that way you coul test your FET  and JTAG circuit......

you can get a free evaluation version from IAR ystems webpage

bye

ilogic said:

Hi Jonh B...

Did you try to program your chip with IAR workbench?

in that way you coul test your FET  and JTAG circuit......

 

you can get a free evaluation version from IAR ystems webpage

 

bye

Thanks for the tip,  I will check it out after this quarter is done or possible in my free time, what little of it there is.  thanks for all your help guys, much appreciated.  Take care.

John,

I'm having the EXACT same error and problem with my CCS v4.2.4 update (from v4.2.3).  I tried reinstalling and get the same error.  I highly doubt it's a bad FET issue.  I'm running Win Vista.  We are in a time crunch and need to get this prototype out for testing.  My JTAG circuit is fine and works great with CCS v4.2.4.  I'm fairly certain that it's a CCS software problem.  What do you suggest?

Thank you,

Geof Galbraith

Sorry,

I meant my JTAG circuit works great with CCS v4.2.3....

Thanks,

Tried some more stuff...

I downloaded the latest Elprotronic Inc. FET-Pro430 sofware.  Using it, I updated the FET firmware to v2.04.08.002 and loaded a hex file just fine using the updated FET.  The board worked fine.  I then opened CCS v4.2.4 and tried debugging.  This time it didn't say that the FET firmware needed updating, however, the same error boxes descibed above came up again.  So I think this pretty much proves that it's a CCS v4.2.4 issue/bug.  Problem is, if I downgrade to CCS v4.2.3 again, will the updated FET still work?  This all really sucks.  What a hassle.

Any solutions???

Thanks,

Geof Galbraith

Hi Geof,

I have moved this to the CCS forum and will see if I can help you.

What happens if you do not downgrade CCS, however just downgrade the dll/FET Firmware version?    Could you please try that and keep us posted? 

The Elprotronic software can help you manage the firmware version on the FET to cycle it back and give that a try.   If CCS asks to update, you can then simply ignore it.

Best Regards,

Lisa

Thanks for the reply Lisa,

I thought of doing that and looked into it.  I only have the "Lite" version of the Elprotronic SW and cannot see where it allows me to load older FET versions.  Do you have any instructions or info that would help me out with this.  Also, where would I get the older versions from as they're not on the TI website?

Thanks,

Geof

Hi Geof,

The various versions are here.  In the Elprotronic tool you can find the option under Tools.  Please not you will need to make sure the elprotronic software has the correct COM port selected.

http://processors.wiki.ti.com/index.php/MSP430_JTAG_Interface_USB_Driver

You could alternatively try to manually downgrade yourself but I would try via Elprotronic first.

Best Regards,

Lisa

Hi Geof,

I just thought I would check whether the tips were helpful and whether there is any update with the enquiry.

Best Regards,
Lisa