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.

CCS Version 5.1.1.00031 debugging with MSP-FET430UIF - Error connecting to the target

Other Parts Discussed in Thread: CC430F6137, MSP430F149

Hi,

I am trying to debug a project for the CC430F6137 device under CCS v5 with a TI MSP-FET430UIF rev1.4.

As this is the first project that I have debugged since the upgrade to CCS v5, the first time the debugger was launched, the firmware in the FET was updated and this appears to have been successful.

However, the following message is received when an attempt is made to debug the project "MSP430: Error connecting to the target: Unknown device".

I have looked on the forums and found information about using the 'Test Connection' button, but both the Test and the Save buttons are greyed out in the Target Configurations window:

Are there any other options that I should be setting here?

I have also tried using dbgjtag, but there is no configuration file <ccBoard0.dat> present in the C:\Users\<username>\AppData\Local\.TI directory.

Please advise how I should proceed.

Regards,

Chris

  • Hi Chris,

    if you have v1.4 and not 1.4a hardware, the upgrade process is a bit different for you to go to the required dll v3 for CCSv5.  Please see this wiki with more details.  Also, another thing you can do is try from the start menu upgrade tool.   This is in the start menu under Texas Instruments->MSP-FET430UIF Debug Interface.

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

    Please keep us informed.

    Best Regards,
    Lisa

  • Hi Lisa,

    My earlier post was a bit misleading, I do have a v1.14a FET (I was trying to distinguish it from a v1.3 FET).

    I had already seen the Wiki article that you mentioned, but it didn't help me to resolve the issue.

    When I go to Start -> Texas Instruments -> MSP-FET430UIF Debug Interface, the only option I have available is "MSP-FET430UIF v3 to v2 Downgrade", which implies that the FET has the updated revision of the MSP430.dllv3.

    Are there any other settings buried within the vast array of CCS options that may be impacting the launch of the debugger?

    Thanks,

    Chris

  • Hi Chris,

    odd since I have both an upgrade and downgrade utility there that got installed with CCSv5.

    Have you checked what is in your device manager?  Is it at least coming up correctly as a CDC device and virtual COM port?  Have you tried a different USB port or a fresh workspace?

    What if you try letting a free tool like elprotronic do the upgrade?  www.elprotronic.com ... they have a free flash programmer.

    Please keep me informed how the above goes.  I am wondering if something got messed up with your install however if the upgrade may not have gone smooth and you don't have the upgrade utility.

    Best Regards,
    Lisa

  • Hi Lisa,

    Here is the data shown in the device manager:

    indicating that the FET is correctly recognised.

    I downloaded and installed Elprotronic FET-Pro430 v3.05 and used this program to "upgrade / repair" the firmware in the FET, which it did without reporting any problems.  For info, I still only have a Downgrade option in the start menu.  I closed Elprotronic, re-opened CCS and tried again to debug our project.  No change, same error:

    I have tried from a different USB port and even on a different PC with another installation of CCS ... always the same issue.

    Where do I go from here, as without the debug capability, our team can not advance and we are losing valuable project time.

    Regards,

    Chris

  • Hi Chris,

    there are two further things we can check

    - please try the patch posted here as there are some devices (potentially yours included) that had known issues with dll v3

    http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/t/155784.aspx

    - please check how you are powering the board.  Another bug in the dll is to do with the power in certain cases.  How are you powering the board?  External?  Via JTAG?  Do you have the capability to try one or the other?

    Please keep us informed. 

    Best Regards,
    Lisa

  • Hi Lisa,

    Our board consumes very little (max consumption is the radio in tx), so I was powering from the JTAG port.  I tried launching debug with external 3V applied to the board, but no change.

    Please can you check the link in your last post, when I click on it I get a message "Group Not Found".

    Regards,

    Chris

  • Hi Chris,

    ok I will get you any feedback/the patch if possible as soon as I am able.  I have been pulling in a couple colleagues who worked on this (including the colleague who made the patch) in the background here so lets see what happens.

    Best Regards,
    Lisa

  • Hi Chris,

    we are at a bit of a loss here as we actually just tested a couple times with the same CCS version and same FET version and same chip.  We saw no issues at all.

    Could you please double check a few things

    - once again check the power to the board

    - are you using an EVM or your own board?  Do you have another board you could try?

    - can you connect to Elprotronic to flash something/read the flash?

    - do you have your virtual bluetooth ports that might be on the pc disabled?  Do you have other devices connected that might be having some type of an effect here?

    - do you have full administrator priviliges and was CCS installed with them?

    Best Regards,
    Lisa

  • Hi Lisa,

    We are using our own prototype board.  I have tried a few of our prototypes, but with the same problem each time.

    I have done some tests with the latest revision of Elprotronic and the FET with DLLv3 - I can read the memory on one of our older products (MSP430F149) but not with the new prototype pcbs using the CC430F6137 device.

    With this information, I have revisited the connectivity required between the micro and  the FET and have realised that the bespoke cables we use to connect our prototype boards to the FET are not compatible with devices with multiplexed JTAG pins i.e. the TEST connection is not made between the FET and the device.

    I will modify an interface cable to add the TEST connection and let you know if this resolves the issue.

    Regards,

    Chris

  • Hi Lisa,

    I have now built up a new 2-wire JTAG communication cable following Figure 2-2 of SLAU278h.  With this new cable I can communicate with the CC430f6137, so it was our programming cable that was causing the connection error all along.  Apologies for leading you down the wrong track when it was our hardware error.

    Thanks for your help in narrowing down the issue.

    Regards,

    Chris

  • Hi Chris,

    No problem at all.  I am very glad to hear things are working and thanks for the update.  All the best with development.

    Best Regards,
    Lisa