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.

Code composer V5.1 - problem debugging

Other Parts Discussed in Thread: MSP430F5438

Hi,

 I was using CCS 4.2 for the MSP430 and everything worked fine. I installed CCS version 5.1 and I can't debug anymore. The "Connect target" icon is still shaded.  When I launch the debug, I get the message "Target must be connected before calling the function". However another collegue also installed CCS 5.1.0.09000 and even if he gets the same target error message, the "Connect target" icon becomes available and debugging works afterwards. Do you know how to solve this problem? I updated the 2 dlls (msp430.dll and hil.dll) according to http://processors.wiki.ti.com/index.php/MSP430_JTAG_Interface_USB_Driver

Thanks,

Frank

 

  • Hi Frank,

    what MSP do you use?  Did CCSv5 ask and do an upgrade of the firmware on your FET? 

    Have you tried upgrading the firmware as per the instructions on this wiki?  Would you be able to and keep us informed if this helps?

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

    Best Regards,
    Lisa

  • Thanks Lisa,

    Regarding p://processors.wiki.ti.com/index.php/MSP_Debug_Stack, since we have a 1.4 FET, the only thing done is the expected automated  "Upgrade process to MSP430.DLLv3" process. The FET version is now 3.02.01.009. (However if the FTP would be  programmed from the FET-MSP430 software, the available version to download is 3.02.03.002 which is a newer version.). That's all I did from that site.

    I also downloaded msp430.dll_developer_package_rev_3.02.01.009.zip from http://processors.wiki.ti.com/index.php/MSP430_JTAG_Interface_USB_Driver. The only thing I did is copy the 2 dlls (MSP430.dll  and HIL.dll) to C:\Program Files\Texas Instruments\ccsv5\ccs_base\DebugServer\drivers and reboot the PC. There are 2 .exe files in the zip file:

    msp430.dll developer package rev 3.02.01.009\Driver\CDC\DPInst64.exe

    msp430.dll developer package rev 3.02.01.009\Driver\VCP\Certified\Setup.exe

    Should I call them? Is there anything else I should install?

    The processor is MSP430F5438.

    Best Regards,

    Frank

     

  • Hi Frank,

    please try the method described in the wiki I send you.  Please either allow CCS to upgrade and load the firmware or else (if the manual copy prevents this) please try using the start menu tool to program the FET.  Please keep us informed.

    Best Regards,
    Lisa

  • Hi Lisa,

    This is exactly what I did. Just to mention that the problem is that the Connect target icon remains shaded after initiating a debug session. Please read my first message again.

    May I have CCS v4 and CCS v5 simultanously installed on a PC. I think I'll reinstall CCS v4 and use it for a while.

     

    Best Regards,

  • Hi Frank,

    ok can we just check a couple things.

    1 - CCSv5.  Please restore the dlls to as installed.  Please confirm whether, as on your colleagues machine, CCS automatically updates your FET and things work. 

    If this does not work.  Could you please allow your colleagues installation to upgrade the FET and then try on your computer.

    2 - CCSv4 CCSv4 will not work with the v3 dll.   In order to go back and forth between the two versions you need to upgrade and downgrade.  There is a start menu utility to do exactly this.  Make sure you restore the v4 dlls to as they were.  Downgrade the FET, try v4.


    Please keep us informed.  Depending on the above further diagnostics might need to be next.  Have v5 and v4 together is no problem .. I am exactly in that situation working with the MSP and upgrading and downgrading.

    Best Regards,

    Lisa

  • Hi Lisa,

    Just let clarify some points:

    1- The FET is already updating by itself to version 3.02.01.009. Seems to be ok, Right?

    2-When you say: "CCSv5. Please restore the dlls to as installed" which steps do you mean exactly?

     

    Regards,

    Francois

     

     

     

     

     

     

  • Hi Francios,


    What I meant is that I just wanted you to go back to the as installed state.  From your posts it seems you have been downloading beta versions and/or manually replacing the dlls.   I wanted to double check if this might be involved in why your pc has issues, or whether with a clean install/as installed you start getting things to run like your collegues. 

    Best Regards,

    Lisa

  • Hi Francois,

    I just thought to check if there is any update here?  Hopefully starting from an as installed state got your computer working like your colleagues.

    Best Regards,

    Lisa