• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 542 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/MSP430F2013: CCS/MSP-FET: MSP430: Error connecting to the target: Unknown device

Errol Kowald
Intellectual 540 points
Part Number: MSP430F2013
Other Parts Discussed in Thread: UNIFLASH, , MSP-FET, MSP430F2012

Tool/software: Code Composer Studio

I have three custom MSP430F2013 boards, all the same. Two can be programmed with CCS V10 / MSP-FET/SBW without issue, but the third will not program initially, with CCS complaining "MSP430: Error connecting to the target: Unknown device". If I then close CCS and run UniFlash 4.5.2056, it detects that a MSP430 is attached but requires a manual selection of the device. Once done, the hex generated by CCS can be selected and uploaded without fail. If I then close UniFlash and reopen CCS, it then has no issues uploading.

This happens only with one board. The others are fine, although I've seen similar responses in previous MSP430F2013 projects, especially with the old MSP-FET.

None have a reset cap to gnd. The cable from MSP-FET to the MSP430 is less than 150 mm long. The board is self powered running on 3500 mV and both UniFlash and CCS are set to that value.

CCS attempted to update the MSP-FET firmware when I began this project a week ago after it sat idle for 2 years. UniFlash managed the update without error.

What is going on?

  • 0
    TI__Mastermind 26420 points

    Hello Errol,

    "Error connecting to target: Unknown device" indicates there is an issue with the communication between the JTAG FET and the MSP430 on the board.  The fact that the issue seems to be intermittent (only on 1 of 3 boards, and that it sometimes works with other software) leads me to believe your programming circuit is just barely meeting the timing and signal quality needed by that specific MSP430 or this board is experiencing noise.    

    Why do you not have a cap on the Reset line?  For SBW, I would recommend .1nF to 2.2nF as described in figure 2-2 of the MSP430 hardware tools user's guide. 

    You can also try changing the SBW speed in the target configuration file in CCS, to see if that has any effect.  

    Thanks,

    JD

  • 0 in reply to JD Crutchfield
    Intellectual 540 points

    Hello JD,

    thanks for the reply. I don't understand why CCS has difficulty while UniFlash doesn't, unless of course, UniFlash is running the link slower. I haven't changed any settings on either CCS or UniFlash, so I assume that they are both running full speed. I also don't understand why CCS always works fine after the initial programming by UniFlash.

    I will try slowing down CCS. Looked in the settings but found nothing. I see that it must be done in the target configuration file. Do you have any details on how to do this?

    I have no cap to gnd on the reset line because when I do, SBW won't work at all. Even with 1 nF.

    If I were to add a reset cap I would have to switch it in circuit when deployed & out during programming

    I've seen various implementations of the reset circuit for the MSP430F2013. Some have the cap to gnd, some without. From my research on the subject, the cap is only there to ensure that the reset happens after Vdd rises fully. If Vdd rises quickly, the reset cap is not necessary. As I understand it, the cap is not there to reduce resets due to noise injection.

  • 0 in reply to Errol Kowald
    TI__Mastermind 26420 points

    Hey Errol,

    It seems that CCS and Uniflash are somehow driving the JTAG slightly differently.  Could be speed or even just the timing or commands, etc.  

    As for slowing SBW down, in your CCS project you will find a target configuration folder with a .ccxml file in it.  Open this file in CCS and on the right side click target configuration under advanced settings.  You should be able to navigate to MSP430 in the tree, and you will see JTAG/SBW on the right side.  I believe the default is medium, I would change it to slow.  

    Thanks

    JD

  • 0 in reply to JD Crutchfield
    Guru 33653 points

    JD Crutchfield said:

    Why do you not have a cap on the Reset line?  For SBW, I would recommend .1nF to 2.2nF as described in figure 2-2 of the MSP430 hardware tools user's guide. 

    Cap on reset line is only for start up and holding reset pin (state) stable during running (in noisy environment).

    Cap is irrelevant for SBW (when reset / data line is driving by master / slave device). To be more precise, best for SBW (running on max speed) is no cap on target device reset pin.

    Errol Kowald said:

    I've seen various implementations of the reset circuit for the MSP430F2013. Some have the cap to gnd, some without. From my research on the subject, the cap is only there to ensure that the reset happens after Vdd rises fully. If Vdd rises quickly, the reset cap is not necessary. As I understand it, the cap is not there to reduce resets due to noise injection.

    This is correct. And I don't see any reason why any SBW master device up to 4 MHz SBW clock should have problem with target device without cap on reset pin, on 40 cm (non shielded) flat SBW cable.

    BTW, this is only 2KByte flash device, and without cap on reset pin on 6 MHz clock, my flasher will do it (by SBW+) in 0.2 sec.

    d:\msp>flash -f test_msp430f2012.txt -vc 33 -s 2 -e -w -v

    File: "test_msp430f2012.txt"
    @F800 2048 bytes
    Total Size: 2048 bytes

    Found SBW+ at COM8

    VCC 3,3V

    Fast Mode

    Get Device
    # JTID Fuse Device Proc
    0  89   OK   2955  00A0

    Erase
    Time: 32 ms

    Write
    Time: 53 ms  Speed: 37,3 KB/s

    Verify
    Time: 22 ms  Speed: 87,7 KB/s

    Release Device

    Total Time: 188 ms

    d:\msp>

**Attention** This is a public forum