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/MSP430F2122: Wrong Identifying On CCS and debugger problems

Part Number: MSP430F2122
Other Parts Discussed in Thread: MSP430F2471, MSP-FET, MSPDS

Tool/software: Code Composer Studio

Hi everyone,

Why does the error message, error connecting to the target, exist on CCS but my chip and my project is the same?

My chip is MSP430F2122 and my setting of project is MSP430F2122, too.

The error code said, The target setup(MSP430F2471) does not match the actual target type(MSP430F2122).

How should I solve it?

Is the chip  broken?

The error message of wrong Identifying do not show anymore.

There is other trouble with debugger.

The same target board can work with MSP-FET430UIF but MSP-FET can't

Sincerely,

Norton

  • Hi Norton,

    Can you double check the project settings in CCS? You can do this by right clicking on the project the navigating to "General". Can you check that the variant selected is the MSP430F2122?

    Best regards,

    Caleb Overbay

  • Hi Caleb Overbay,

    I have checked this.
    It is MSP430F2122, and the same project can debug with other MSP430F2122 chip without any error.
    What kind of problem can cause this trouble?
    Does the chip have a bad paste on the pad or PCB?
    This is a new project of mine, and I made 5 pieces of the same PCBs for testing and creating this CCS project.

    Sincerely,
    Norton
  • Hi Yu,

    The only other thing that could explain this is if the part is actually an MSP430F2471. Can you take a picture of the marking on top of the part and post them so I can verify which device it is?

    Best regards,
    Caleb Overbay


  • Hi Caleb Overbay,

    Is this the picture you want?

    Sincerely,

    Norton

  • Hi Norton,

    Thanks for providing the image. I'll need to discuss this with some other team members and get back with you shortly.

    Best regards,
    Caleb Overbay
  • Hi Norton,

    What programmer are you using to program the device (e.g. MSP-FET, MSP-FET430UIF, etc)? Is it possible for you to try programming the device using a different programmer and see if you get the same results? Also how many devices are currently experiencing this issue?

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    Because the project is still being built , I used only 'debug ' of CCS to program the chip.
    Until now, I have only this chip with wrong identification.
    But when I tried to program again yesterday, it can not be programmed.
    CCS told me the error message is Unknown Device.
    I have no idea about the PCB have bad pad or the chip is broken.
    Please tell me the way of solving the problem or if I have this problem again how I can solve.

    Sincerly,
    Norton
  • Hi,

    When you program the MSP430 you have to use a debugger even when using 'debug' in CCS. So what is the device that is connecting the MSP430 to your PC and is it possible to attempt using a different debugger?

    I'm not sure how to solve the issue yet and I'm working with others within TI to try to come to a solution.

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    As the following picture is the debugger that I use.

    The serial number pasted backside of the debugger is 1407001FA.

    BTW, I wanna ask you the differences between the white debugger and the black debugger in the picture

    I did program for our product several days ago, but I have a trouble below,

    Some of the chips can not be programmed with the black one but white one can.

    After that, I continue to work with my project with black one on CCS6, and I got the error message, Unknown Device. Even a new empty project which is created on CCS6.

    There is only WDT in the main.c file in the project created on CCS6.

    So, Are there anything wrong with my debugger or there is something wrong with my PCB or chip?

    Sincerely,

    Norton

  • Hi,

    Thank you for providing this information. The black debugger in your picture is the MSP-FET. It is our newest debug probe. The white device is the MSP-FET430UIF and is the predecessor to the MSP-FET. You're description of the issue is leading  me to think this could either be a problem with the debugger, or the way the MSP430 is connected to the debugger. I have a few more questions to better understand the issue:

    1. How many devices are currently experiencing this issue?
    2. Can you provide a schematic of the connections between the MSP430 and the debugger?
    3. When programming the device, is the debugger supplying power to the MSP430  or is the target board supplying the power?
    4. Initially you were seeing an MSP430F2122 be identified as a MSP430F2471
      1. Are you seeing this error anymore?
      2. Or is it just the unknown device error?

    I think the schematic is the most important piece of information here. If you're not comfortable posting it on the forum, you can send me a friend invite and private message me on E2E.

    Best regards, 

    Caleb Overbay

  • Hi Caleb Overbay,

    Thanks for replying me.

    These are the answers of the question you ask,

    1. We make about 520 pieces of our product and about 20 pieces (almost 4%), we have a connection with agent and told then about the problem.

    We have sent the trouble chips to then and we still wait for the reply.

    2. I have send you a friend invite. When you reply on it, please send a private message to me and I will send you the whole schematic.

    3. Target board is. There is a power circuit for supplying power to the whole PCB. And the power source is power supply or AC power.

    When programming, I use a power supply.

    4. I have not seen the problem anymore now since I changed the debugger to the white one.

    About the debugger and the environment, I can give you some more information.

    We have programmed, created and any other things about MSP430 with the white debugger for a very long time.

    Since the CCS6 was published, we bought two black debuggers. One is from Mouser and the other is from ti shop.

    But there are some troubles with the debugger from Mouser, so we return to Mouser.

    After that, we still use the white debugger for programming or creating with CCS4.

    Until now, I think I should upgrade to a new environment and use a newer tool, so I have discuss with others in our company.

    And I am using both black debugger and white debugger on both CCS4 and CCS6. Major use with CCS6 and the black debugger.

    We programmed for our product last week and have the trouble.

    On the other hand, I have almost finished programming and have some trouble about programming error(like the picture below), so I change the tool to the white debugger.

    After that, I can program successful. I used the tool for reading debugger version, the version of the black one become 1.00.00.000(picture below).

    These are some other information. Hope they are useful.

  • Hi,

    I received your friendship request and sent you a message. I recommend updating CCS to the latest version. You can find v7.2 on this download page. After that I would try using the MSP-FET (black debugger) again and see if you have any issues. If you connect the MSP-FET to the updated CCS and try to program the MSP430, it will automatically prompt you to update the firmware on this MSP-FET.

    Best regards,
    Caleb Overbay
  • Hello Caleb Overbay,

    I always do upgrade for MSP-FET when CCS shows the message that I need to upgrade.
    I've told that the version become 1.00.00.000, but it can work.
    And it sometimes has the error message, *.out load failed.
    I have no idea about whether the MSP-FET or the wires between chip and FET is broken.
    BTW, I have sent you schematic via private message.
    Please make a check on it. Thanks a lot.

    Sincerely,
    Norton
  • Hi,

    I have reviewed your schematic and noticed that when programming, you are supplying VCC to the device via the target board but do not have it connected to the debugger. Figure 2-2 of the MSP430 Hardware Tools User's Guide shows how to properly connect to the MSP430F2xx via a Spy-Bi-Wire interface. As noted in the figure, you need to connect the MSP430 VCC to pin 4 (VCC_TARGET) of the debugger (MSP-FET or MSP-FET430UIF). Without this connection the debugger will have difficulty communicating with the MSP430. Sometimes it may work and sometimes it may not. I highly recommend making this change, or you will encounter even more trouble programming the MSP430 regardless of which debugger you are using.

    Best regards, 
    Caleb Overbay

  • Hi Caleb Overbay,

    The status is same as original when I use the way you told me.(add a wire between VCC_TARGET and VCC on target board)

    These are my operation below,

    1. I did not change any wires or connects of the hardware and debug with black debugger.
      Sometimes it could work and sometimes it could not. (This is the original status)
      I changed nothing but debugger(white debugger in this status), it can work.
      BTW, we have used the connect in the schematic I gave you and the white debugger for a long time and there is nothing wrong.
    2. I added the wire between VCC of target board and the debugger like you told me.
      Still, the white one can work and the other can't.

    CCS shows like the picture below with the black debugger even I click on 'Run'.

    But it can run normally with the white debugger.

    Sincerely,
    Norton

  • Hi Norton,

    Even though the white debugger has been working without the VCC_TARGET connection, doesn't mean it will always work. The debugger needs to be able to know the VCC of the tool to be able to apply the appropriate voltages to the RST and TEST lines. Without the VCC_TARGET connection you are operating out of spec and will most likely encounter an issue at some point.

    In your screenshot you've provided it looks like you have the part in debug mode. Does this mean you were able to load the code onto the part using the MSP-FET (black debugger)? This is something you weren't able to do before adding the VCC_TARGET connection correct?

    Also can you tell me what pins of the MSP-FET you are connecting the Spy-Bi-Wire interface to (CN3 on your schematic)? Pin numbers and their description would be best.

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    Both of the two debuggers can load the code into chips.

    It seems like there are some bothers of error signal or other error with MSP-FET.

    After clicking on 'Run', it can run several codes and become to the status like the screenshot.

    When I change into MSP-FET430UIF, this won't happen

    I use an external board as the bridge between debugger and the target board.

    The connect is the same as the picture of datasheet screenshot you give me.

    I have made them on schematic. I think the figure is more clear than the words.

    Please make a check on it.

    As the following picture is the external board and the file is the schematic.

    Sincerely,

    Norton

    Protel Schematic.pdf

  • Hi, 

    Thanks for the additional information. I'm still working on this for you but I need to speak with some colleagues who are more familiar with the MSP-FET. I'll get back to you soon.

    Best regards, 
    Caleb Overbay

  • Hi Caleb Overbay,

    Thanks for your help.
    Wait for your news.

    Sincerely,
    Norton
  • Hi Norton,

    Thank you for your patience! So that we can try to recreate the issue and find a solution can you provide the following:

    1. What is your IDE and IDE version?
    2. What operating system are you using?
    3. What MSP Debug Stack (MSPDS) version are you using?
      1. This can be found in CCS by following Help --> About Code Composer Studio --> Installation Details --> TI MSP430 tool-chain --> MSP Debug Probe drivers
      2. Then in the bottom window pane, scroll down to the MSPDebugStack version:

    Best regards, 
    Caleb Overbay

  • Hi Caleb Overbay,

    1. What is your IDE and IDE version?
      >> My IDE is CCS6
      >> I have use CCS4 for a long time until several months ago, and there is no any questions on CCS4.
      >> Because the company which I work in owns the license of CCS6, I upgraded to CCS6 then.
    2. What operation system are you using?
      >> Windows 7 Professional x64
    3. What MSP Debug Stack (MSPDS) version are you using?
      >> I can not check this information on my CCS?
      >> How can I solve it or how can I get the information to you?

    Sincerely,

    Norton

  • Hi Norton,

    Have you tried updating to CCS v7? As of CCSv7 all versions of CCS are free of charge. Also, in the screenshot you've posted, if you scroll down further you should see a folder titled "TI MSP430 tool-chain". Is this folder not present?

    Alternatively, if you installed CCS in the default path you can find the MSPDS version by going to C:\ti\ccsv6\ccs_base\DebugServer\drivers. Then right click on MSP430.dll and select Properties. Once the window opens, select the Details tab and then you will see the Product Version.


    Best regards,
    Caleb Overbay

  • Hi Caleb Overbay,

    As your suggestion, I am now trying to install and update my IDE upon to version 7.
    If there is any question on CCS7, I will create a new post.
    On the other hand, most of the projects (about 95% project) are created by CCS4 and few projects are creater on CCS6,
    Will the project can be imported to CCS7 directly and they can work without any problem except debugger?
    And the last about IDE, I have not uninstalled CCS4 and CCS6, can they exist with CCS7 in the same PC? Or should I uninstall the old version?
    I decide to uninstall all of the old versions after I finish testing with the newest version of CCS with out any problem.


    There is not folder titled "TI MSP430 tool-chain" in the installation detail.
    But according the path you've told me, the version of MSP430.dll is 3.9.1.2.
    This is the window below, but the language is Chinese.

    BTW, do these issues have uses for the main trouble of MSP-FET and MSP-FET430UIF?
    I have used MSP-FET430UIF for my project late in these days.

    Sincerely,
    Norton

  • Hi Norton,

    Be sure to let me know if the issue is resolved with CCSv7.

    The projects you've created with older versions of CCS should import correctly into the newer version. It's also ok for multiple version of CCS to exist on your computer.

    I'm gathering this information and giving it to our team responsible for the MSP-FET. With this they will try to recreate the issue and find the root cause. Thank you for your patience throughout this process! I'll keep you updated as I learn more from my team.

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    Of course to let you know if the issue still exist in CCS7.
    You should wait for me for several days, because I need to do some other things for my team these days.
    Once I start to work with CCS7, I will keep contact with you and upload the information and other news.
    By the way, I have finished installing CCS7.
    From now on, I will use CCS7 as the major IDE of my project.
    I will make my MSP-FET and MSP-FET430UIF into the original status and try them.
    After several time of testing, I will report to you.

    Sincerely,
    Norton
  • Hi Caleb Overbay,

    I have continued to test the debuggers with CCS7.

    There are some information that I can offer you now.

    1. Both of my debuggers first use with CCS7, it asked me to upgrade my debugger and I agree with it.

    2. There will be the errors of "Unknown device" or "*.out load failed" sometimes if I use MSP-FET(the black one).

    3. As usual, it can work normally with the MSP-FET430UIF(the white one).

    4. All of the wires between JTAG and target board are all same as the schematic I gave you.
    I have not changed any hardware, and the VCC_TARGET pin is still N.C.

    If you need any information, just let me know.

    I will do my best to support you to solve the problem for my trouble.

    Sincerely,

    Norton

  • Hi Norton,

    The VCC_TARGET connection is required for correct operation of both debuggers. Otherwise, you are operating out of spec and I can't advise on the expected behavior. Please ensure all tests include this connection. Can you make this change and let me know if you are still having issues?

    Best regards, 
    Caleb Overbay

  • Hi Caleb Overbay,

    I made the change of connecting VCC_TARGET and issue still exist with the MSP-FET.
    But the error message don't appear every time I pressing "debug".
    After changing, "Unknown Device" is not shown anymore but "*.out load fail" still exist.

    These are some trouble I met after I connect to the VCC_TARGET.

    Sometimes it will crush and stuck at the same view like the picture below.

    And sometimes it tells that, The voltage 1562 value is not correct/allowed for the USB FET.

    The values would be different on every time the error was shown.

    Both of my two debuggers have the same trouble, but the VCC_TARGET is connect to 3.3V actually.


    I have met the problem, "*.out load fail" before, but it is fine to do everything after I press "Debug" again.
    I asked this issue before, but I have not got any solutions until now.

    Sincerely,
    Norton

  • Hi Norton,

    Thanks for the additional information. This really looks like the VCC connection between the MSP430 and the MSP-FET is incorrect. Just to confirm, you're connecting the VCC_TARGET pin of the MSP-FET to the VCC of the MSP430?

    Have you measured the voltage to make sure it is actually 3.3V as well?

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    I connect the VCC_TARGET of MSP-FET to the same VCC as MSP430.

    The VCC which I supply to MSP430 and VCC_TARGET is made by the chip AIC1734-33.
    And I measure the output of the IC and the VCC I connect to MSP430 is 3.29V.

    Sincerely,
    Norton
  • Hi Norton,

    Everything we've uncovered so far suggests that this is a hardware issue involving incorrect or faulty connections to the MSP430. Can you verify that they GND being connected to the MSP-FET is the same GND being used for the MSP430?

    Also, can you probe the VCC_TARGET, RST and TEST lines when a failure occurs and to ensure that VCC is staying at 3.3V while trying to connect to the part?

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    OK, I will make sure the connect between MSP430 and debugger.
    I use MSP-FET430UIF these days and I have not met the trouble.
    As usual, there is the error with the MSP-FET.

    I have check the connection again, and this is the result below.
    The GND is connected to the same GND as MSP430.
    The VCC_TARGET is connect to the same VCC as MSP430, and it is 3.3V exactly even of the error code exist.
    The RST and TEST line has connect to the MSP430 with the same wire with the screenshot of JTAG datasheet you gave me last time.

    Thus,
    You have said that it is a hardware issue, but how can MSP-FET430UIF work normally but MSP-FET can't?
    If there is an incorrect connection in hardware, it can work with any debugger, right?
    I have tried all of the external boards we made which connect between debugger and the MSP430 and it work all the time without any trouble.
    Still, the trouble is the same as the status I have told you.

    At the last, I will still tried to test the debugger we have.
    And if there is some part that I should check, please tell me.
    Thank you very much.

    Sincerely,
    Norton
  • Hi Norton,

    Firstly I'd like to thank you for your patience throughout this process. You've been very cooperative and understanding.

    It looks like all the connections are correct between your target board and the debugger (both MSP-FET and MSP-FET430UIF). I see that you have a 2.2nF capacitor populated on the RST line. This is the maximum recommended capacitance on the RST line and it's possible that the connection to the MSP-FET is adding some additional capacitance. Can you try reducing this capacitance to 1.1nF and retesting?

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    Thanks for keeping this issue in mind.
    We made a new PCB these days and I will use a smaller capacitor and than tell you about the result.
    After I finish testing with a smaller capacitor, I will let you know about the result I get.
    Thanks for help and sorry for wasting your time to wait for me.

    Sincerely,
    Norton
  • Hi Norton, 

    No need to apologize. Thanks for letting me know there will be a delay. Just reply to the thread when you've finished your testing. 

    Best regards, 
    Caleb Overbay

  • Hi Caleb Overbay,

    To reduce the wasting time, I have made a reply before I finish the whole brand new PCB.

    And this pcb use the other mcu.

    I have the same result as previous status after I replace the reset capacitance with 1.2nF(There is no 1.1nF that I can use).

    This is the description of operations below.

    I have started to make new PCBs, and I usually paste MCU and JTAG for debugger first and do a code update test.

    As the suggestion you gave me, I have change the capacitance to a smaller one.

    As usual, MSP-FET430UIF can finish work without any errors but MSP-FET show the error code like the figure.

    This time, there is only MCU under the operation of code update.

    But the PCB should be finished is more suitable.

    BTW, I have some other questions to discuss with you.

    1. Except capacitance, there is still a resister from reset pin to VCC.(Maybe you can make a check with the schema I gave you.)

    will the resister have the affection with the debug or upload operation?

    2. Is the pin VCC_TARGET used for giving the power to MCU from debugger or just let the debugger and the MCU have the same voltage level?

    Sincerely,

    Norton

  • Hi Caleb Overbay,

    I have used MSP-FET430UIF for my current project, and all things seems well.
    But it still have some problems with MSP-FET.
    To be honest, we bought two MSP-FETs and with the similar trouble, we have returned one of the two MSP-FETs.

    Otherwise, what is the purpose of connecting VCC_TARGET with the VCC of the target mcu?
    Does it use for offer power to mcu?

    Sincerely,
    Norton
  • Hi Norton,

    The pull-up resistor you have on the RST line is recommended and is necessary for proper operation. The VCC_TARGET connection is not for supplying power to the MCU. For your particular setup, the MCU should be receiving power from the board it is populated on. The VCC_TARGET connection is used for ensuring the MCU has the correct voltage level needed for programming and that the debugger and the MCU are using the same voltage level.

    Best regards,
    Caleb Overbay
  • Hi Norton,

    I just wanted to checkup on the status of this and see if you were able to resolve the issue?

    Best regards,
    Caleb Overbay
  • Hi Caleb Overbay,

    Thanks for your kind attention.
    Unfortunately, I have not solve the problem after I connect the pin to VCC_TRAGET.
    And now I use the MSP-FET430UIF which I can use in a normal status to do all the things and projects.
    I have talked to my boss with this issue, and he made me to add the pin of VCC_TARGET in the connector of JTAG next time we build a new PCB.
    I will tell you the status after I create the next project or the next PCB.
    Sorry for forgetting to give you a feedback after you reply me last time.

    Sincerely,
    Norton

**Attention** This is a public forum