• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 22 subscribers
  • Views 231 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.

CDCI6214: Error programming CDCI6214

Danilo A.
Mastermind 28660 points
Part Number: CDCI6214

Hi Team,

We would like to ask your help regarding our customer's inquiry below.

We are programming the clockgen chip CDCI6214 through on-board FPGA. CDCI6214 programming procedure list the following three steps

1.Apply RESETN=LOW. 
2.Apply REFSEL=MID (leave tri-stated)
3.Apply EEPROMSEL=MID (leave tri-stated).

Unfortunately RESETN, REFSEL and EEPROMSEL pins from the clockgen chip are not connected to the FPGA. When the FPGA is ON, they are connected as follows

RESETN - pulled high to 1.8V
RFSEL - pulles low through 4.75k ohm resistor
EEPROMSEL - pulled high through 4.75kohm resistor

Could this be a problem when trying to program the clockgen through EEPROM Direct Access. Because we are able to program the EEPROM directly without having to toggle RESETN and put RFSEL and EEPROMSEL in MID state. But the success rate of programming is not 100%. For every 10 boards we try to program only 7 gets programmed and the remaining 3 does not.

Regards,

Danilo

  • 0
    TI__Mastermind 20900 points

    Hello Danilo,

    sorry for the late response. 

    The power up with REFSEL=MID and EEPROMSEL=MID starts the device in fall back mode, where the I2C interface is activated no matter the EEPROM content.

    If you have not activated "pinmode" (disabling I2C) then you can also program the EEPROM when you start from a EEPROM page (which you are doing.).

    The 70% success rate of EEPROM programming can have multiple reasons:

    - instable power supply

    - EEPROM word write time is longer. Note, that the 8ms are typical. Ensure that you poll the EEPROM_BUSY signal.

    Please check both and probably allow more time between each EEPROM word write.

    Please let us know, if that solves your issue.

    regards,

    Julian