• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 21 subscribers
  • Views 1155 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.

CDCE949 and FT2232D

Teddy Wong
Prodigy 30 points
Other Parts Discussed in Thread: CDCE949, CLOCKPRO, CDCE925

Dear Sir,

I want to use CDCE949 with FT2232D on my own board so that the user can program the CDCE949 by TI’s clock-pro software.

Should I need to program anything for the EEPROM that is attached to FT2232D?

Can I program this EEPROM by the PC via FT2232?

 

Regards,

Teddy.

  • 0
    TI__Expert 5725 points

    Hi Teddy,

    As you can see in the Performance EVM document on page 24 (where the FTDI chip part of the schematic is connected) you do not need an additional EEPROM in order to program the CDCE9xx with our SW.

    For more details go to page 24 on the link below

    http://focus.ti.com/general/docs/lit/getliterature.tsp?literatureNumber=scau022a&fileType=pdf

    Please let me know if you have further questions,

    Best regards,

    Mariajose

     

  • 0 in reply to mapefer3
    Intellectual 255 points

    Mariajose,

    With all due respect, I think you need to take a closer look at page 24 -- there *is* an EEPROM attached to the FT2232 -- it's designated U16. I don't see any comments to the effect of "do not install"...

    I've built an I2C pod which is an almost exact copy of the circuit diagram on page 24 -- right down to using the same level translator. It works fine with FTDI's demo code (in that I can see I2C transactions occuring on the bus), but doesn't work with ClockPro. All I get in the device list are the "local" devices. My scope doesn't show any activity on SCL or SDA when I hit Refresh.

    OS is Windows 7 Premium, 64-bit edition. The EEPROM on the FTDI chip is currently erased, so the chip is acting as if no EEPROM were connected. This means:

    - Chiptype FT2232D/C
    - VID 0x0403, PID 0x6010, USB Version 2.0
    - Config descriptor -- Bus Powered, 90mA max bus power, remote wakeup DISABLED, pulldown on suspend DISABLED
    - Manufacturer string "FTDI"
    - Product string "USB <-> Serial Cable"
    - Serial number enabled, auto-generate serial number, serial number blank, prefix "FT"
    - Port A: Hardware = RS232, High Current I/O off, VCP driver
    - Port B: Hardware = RS232, High Current I/O off, VCP driver

    The CDCE925 is obviously doing something -- I can see the 13.875MHz clock signal (from my crystal oscillator) on the PLL outputs.

     

    UPDATE 2011-01-12 19:57UTC: I've just figured out why Clock Pro can't access the hardware on Win7 64bit -- it's trying to load the 32-bit DLL. If you go into C:\Program Files (x86)\Texas Instruments\TI ClockPro\dll, delete FTI2C.DLL and rename FTI2C64.DLL to FTI2C.DLL, it'll work (more or less). Unfortunately FTDI's library seems to crash if you try and close the device, which ClockPro does rather a lot...

    UPDATE 2011-01-12 21:41UTC: I've got my scope on the I2C lines, and it looks like the chip never ACKs the address bytes that ClockPro sends during a refresh... Clock and data edges are fine, but the CDCE925 won't talk to the I2C host adapter. Do I need to do anything special with S0 to get the I2C port working, or can I just leave it floating high per the datasheet?
    I've tried with VDDOUT grounded and at 3.3V, tried swapping SDA and SCL, and checked pin continuity -- near as I can tell, everything's fine... Even tried a new chip, no difference.

  • 0 in reply to Philip Pemberton
    TI__Expert 5725 points

    Philip,

     

    Just confirmed that the EEPROM attached to the FTDI chip on U16 is not being used. Some of the footprints in the schematic are not necessarily populated. I just removed the U16 from the performance EVM and communication with the CDCE9xx was still possible.

     

    Effectively you would not be able to use the TI clock pro in a 64 bits environment. We will work on making this possible but I cannot confirm a release date when this will happen.

     

    Sorry about that. We have a programming EVM available in order to program the CDCE9xx family products, may be you might want to take a look before developing HW for this purposes, but the SW supports only 32 bits environment.

     

    http://www.ti.com/litv/pdf/scau026a

     

    The PC would not be able to talk to the CDCE925 in a 64 bits environment and I believe that is the reason for a missing ACK or I2C signals. The FTDI chip is the one that is creating the I2C signals.

    S0 can be left floating and through the pull up resistor it would be set to 1. That will be the case when SPI bit is set to 0 so S1 and S2 are set as I2C interface. This happens in a CDCE9xx with default EEPROM contents.

     

     

    Best regards,
    Mariajose