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.

Unknown Device error after upgrading to CCS5

Other Parts Discussed in Thread: MSP430F249

I am attempting to make a software mod to a 3 year old product based on the MSP430.  The original developers (hardware and software) have left the company.  The original development was done on an old machine with a single user license using CCS3.  Since there are 3 of us left here in the group who might make software tweaks to the device we decided to spend the money to get a single user floating license version of CCS5.  CCS5 is installed and working fine ( Version: 5.5.0.00077 ) on my PC (Windows 7 Pro SP1 64-bit).  After making the changes I hooked up the MSP-FET430UIF emulator, and attempted to debug.  CCS noted that the firmware on the emulator needed to be upgraded, and I followed the directions for the upgrade.  After upgrading I get an error indicating that the device is unknown.

After perusing these forums I have attempted to use the IAR compiler instead which changed the FET firmware revision also, but also failed to detect the device.  I downloaded FET-Pro430-Lite which also wanted to update the firmware, and also failed to communicate with the device.

Finally I found a post on this forum by Lisa - TI which said CC5 wasn't intended for use with MSPs, and that a downgrade to V2 on the FET could fix the problem.  Granted, that user had downgraded to CC4 from CC5 when he had the problem.  In any case all I've proven is that V2 isn't compatible with CC5, and that CC5 will attempt to upgrade the firmware before debugging.

This was a working unit prior to connecting the FET to the JTAG interface and attempting to debug, so I don't believe the processor is damaged.  The voltage is 3.0 volts.

I have seen enough chatter online to believe it's some sort of compatibility issue between the FET, CC5, etc., but can't find a definitive answer anywhere that says to use a particular version of CC5, msp430.dll, and FET firmware.

Any suggestions?

  • Hi Rich,

    the msp FET is compatible with v4 5 and 6 ... however differing dll versions are supported.  This is why you been asked to upgrade.

    Some things to check

    - what do you see in the device manager?  What you should see is the FET recognized as a CDC usb device as an virtual com port.   If not try a different port or not using a hub. However if the same pc worked before this is likely not the case but just a verification.

    - would you be willing to try v6?  (If you recently purchased v5 you should be eligible for the updgrade)

    - did you try with the correct elprotronic software?  They have multiple versions intended for different FETs as they sell a FET themselves

    - if possible verify on another pc

    What msp are you using?  is your project set for the correct part?  

    Best Regards,
    Lisa

  • Lisa, I'd be happy to try V6.

    Per your old discussion I did check the device in Device Manager and found it to be configured as CDC.

    Do you have a link to the V6 download?  Will V6 set the firmware for the FET to the appropriate revision?

    Thanks for the quick reply!

    Rich

    EDIT: Sorry, missed the request for the MSP device on first reading.  We are using the MSP430F249.

  • And our CCS5 license was just purchased last week.  Hopefully that's recent enough to be eligible :-)

  • Hi Rich,

    Yes, you should be eligible.   The email associated with you license should have recieved something in the inbox regarding the procedure.    It should contain something similar to this:

    • Find your row for TMDSCCS-ALLF03-v5
    • Click MANAGE and then click UPGRADE – GET NEW LICENSE
    • Click E-mail license - you will receive two (2) emails: Instructions and License File with attachment (.lic)
    • You MUST follow these instructions to save this new License File (.lic) before you can use your upgraded version 6
    • You can download the CCSv6 image at:  http://processors.wiki.ti.com/index.php/Download_CCS

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

    Another thing to check.   How did you bring the old project into ccs?  Have you been able to verify in the device manager? 

    Best Regards,
    Lisa

  • Lisa,

    I am still having the same issue.  I am using a 4 wire JTAG interface with the Vcc, Gnd, and RST! coming from the MSP-FET430UIF.  I have tried it with Vcc set to 3V (the default setting) and 3.3V.  Reset is pulled up to Vcc through a 47K resistor.

    The exact error is "MSP430: Error connecting to the target: Unknown device"

    The hardware is getting power.

    Compiler version is 4.3.1.  CCS version is 6.0.0.00190.  FET is configured in Device Manager as COM4 in CDC mode.  According to FET-Pro430 the FET firmware revision is 3.04.00.020 which I presume is the revision that CCS6 updated it to be.

    As for how I imported the CCS3 project originally, I didn't do anything special.  CCS5 seemed to recognize it and understand it.  Same when going to CCS6.  To verify that the problem isn't something related to the import I created a new project using the CCS File/New>/CSS Project dialog with the empty main.c.  I added for loop that prints "Hello world\n" just to have something to build and debug.  Same problem - doesn't find a device.

    We no longer have the original PC that was used with CCS3 online, so it's not a simple test to see if that would still work after a manual downgrade of the FET firmware, and I am not sure if there's any value in trying a fresh CCS6 install on another machine since this one sees the FET and it appears to be loaded correctly in Device Manager.

    Which version of msp430.dll should be used?  Is there a place to force the tool to use a specific instance of that dll?

  • Lisa, thanks for your help yesterday.  We discovered this morning that the ribbon cable between the FET and the device had a damaged conductor.  Once we repaired that we are working fine.  Always fun to inject those type problems when you upgrade tool versions and make software changes at the same time. :-)

  • Hi Rich,

    glad to hear you found the issue.   

    Thanks for updating and all the best with development.

    Best Regards,

    Lisa