• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 491 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/FDC2214EVM: No USB FET was found

Guoxing Gu
Intellectual 590 points
Part Number: FDC2214EVM
Other Parts Discussed in Thread: LDC1614, LDC1614EVM, FDC2214

Tool/software: Code Composer Studio

Hi,

I am going to do my own application program to control FDC2214EVM. I was following the CCS user guide to start my first test project "Blink the LED" with the FDC2214EVM, and ended up with "No USB FET was found". The CCS is version 901, and my operating system is Win10. I am including the error screenshots and problem remarks. The USB connection was proper as the sensor solution GUI works fine with data-streaming. 

I also followed a few troubleshooting steps found on TI web and still not able to get rid of the issue. Could someone help with it?

Regards,

Gu

 

  • 0
    TI__Genius 17440 points

    Hi Gu,

    I believe your problem is that the FDC2214EVM does not have debugger hardware, which is what the code is looking for. Section 3.1 of this application note discusses that hardware. If you look at your COM ports in Device Manager, you will only see the EVM and no debugger. We have some python sample code available to talk to the MSP430 on the EVM directly. 

    Best Regards,

  • 0 in reply to Kristin Jones93
    Intellectual 590 points

    Hi Kristin,

    Thank you for the link to Q&A.

    Based on Q&A40, the commands are text/string based. Is there any stand alone guide or application note providing more details of the syntax?

    I am not familiar with Python and am going to download/install the opensource  Python, then run the code included in Q&A41. But I could not find the numbers included in the class crc8 in LDC1614 datasheet, hence having difficulty in understanding where and how the numbers are related to the 28 registers (x00-x7F)? Could you please give an explanation?

    Regards,

    Gu

    class crc8:
        def __init__(self):
            self.crcTable = (0x00, 0x07, 0x0e, 0x09, 0x1c, 0x1b, 0x12, 0x15, 0x38,
                0x3f, 0x36, 0x31, 0x24, 0x23, 0x2a, 0x2d, 0x70, 0x77,
                0x7e, 0x79, 0x6c, 0x6b, 0x62, 0x65, 0x48, 0x4f, 0x46,
                0x41, 0x54, 0x53, 0x5a, 0x5d, 0xe0, 0xe7, 0xee, 0xe9,
                0xfc, 0xfb, 0xf2, 0xf5, 0xd8, 0xdf, 0xd6, 0xd1, 0xc4,
                0xc3, 0xca, 0xcd, 0x90, 0x97, 0x9e, 0x99, 0x8c, 0x8b,
                0x82, 0x85, 0xa8, 0xaf, 0xa6, 0xa1, 0xb4, 0xb3, 0xba,
                0xbd, 0xc7, 0xc0, 0xc9, 0xce, 0xdb, 0xdc, 0xd5, 0xd2,
                0xff, 0xf8, 0xf1, 0xf6, 0xe3, 0xe4, 0xed, 0xea, 0xb7,
                0xb0, 0xb9, 0xbe, 0xab, 0xac, 0xa5, 0xa2, 0x8f, 0x88,
                0x81, 0x86, 0x93, 0x94, 0x9d, 0x9a, 0x27, 0x20, 0x29,
                0x2e, 0x3b, 0x3c, 0x35, 0x32, 0x1f, 0x18, 0x11, 0x16,
                0x03, 0x04, 0x0d, 0x0a, 0x57, 0x50, 0x59, 0x5e, 0x4b,
                0x4c, 0x45, 0x42, 0x6f, 0x68, 0x61, 0x66, 0x73, 0x74,
                0x7d, 0x7a, 0x89, 0x8e, 0x87, 0x80, 0x95, 0x92, 0x9b,
                0x9c, 0xb1, 0xb6, 0xbf, 0xb8, 0xad, 0xaa, 0xa3, 0xa4,
                0xf9, 0xfe, 0xf7, 0xf0, 0xe5, 0xe2, 0xeb, 0xec, 0xc1,
                0xc6, 0xcf, 0xc8, 0xdd, 0xda, 0xd3, 0xd4, 0x69, 0x6e,
                0x67, 0x60, 0x75, 0x72, 0x7b, 0x7c, 0x51, 0x56, 0x5f,
                0x58, 0x4d, 0x4a, 0x43, 0x44, 0x19, 0x1e, 0x17, 0x10,
                0x05, 0x02, 0x0b, 0x0c, 0x21, 0x26, 0x2f, 0x28, 0x3d,
                0x3a, 0x33, 0x34, 0x4e, 0x49, 0x40, 0x47, 0x52, 0x55,
                0x5c, 0x5b, 0x76, 0x71, 0x78, 0x7f, 0x6a, 0x6d, 0x64,
                0x63, 0x3e, 0x39, 0x30, 0x37, 0x22, 0x25, 0x2c, 0x2b,
                0x06, 0x01, 0x08, 0x0f, 0x1a, 0x1d, 0x14, 0x13, 0xae,
                0xa9, 0xa0, 0xa7, 0xb2, 0xb5, 0xbc, 0xbb, 0x96, 0x91,
                0x98, 0x9f, 0x8a, 0x8d, 0x84, 0x83, 0xde, 0xd9, 0xd0,
                0xd7, 0xc2, 0xc5, 0xcc, 0xcb, 0xe6, 0xe1, 0xe8, 0xef,
                0xfa, 0xfd, 0xf4, 0xf3)
        def crc(self, msg):
            runningCRC = 0
            for c in msg:
                c = ord(str(c))
                runningCRC = self.crcByte(runningCRC, c)
            return runningCRC
     
        def crcByte(self, oldCrc, byte):
            res = self.crcTable[oldCrc & 0xFF ^ byte & 0xFF];
            return res

  • 0 in reply to Guoxing Gu
    Intellectual 590 points

    Hello,

    Could someone help with the programing issue mentioned above? I can use similar way to do my program on FDC  2214 once I have a good understanding of the numbers in the table relating to the 28 registers (x00-x7F) of LDC1614EVM?

    Thanks,

    Gu

  • 0 in reply to Guoxing Gu
    TI__Genius 17440 points

    Hello Gu,

    My apologies for the delay responding. The numbers in the table are not related to the registers in the LDC1614 (or any device). They are precalculated CRC-8 values for polynomial coefficient indices of 8, 2, 1, and 0. They are used to ensure that the data passed to and from the MCU has no errors. The "CRC-8 check" section of question 40 contains more information about this process.

    Unfortunately we don't have any application notes detailing the syntax.

    Best Regards,

  • 0 in reply to Kristin Jones93
    Intellectual 590 points

    Hi Kristin,

    I have figured out the CRC-8 check numbers required for FDC2214.

    Thank you. 

    Gu