CDCE62005 programming

Paul,

The clock generator CDCE62005 needs configuring before being enabled.

[TI] Yes

Configuration involves setting the frequencies as well as the output type (which is LVDS I presume)

[TI]  Configuration includes Input paramteters, VCO settings, output dividers and output type.  It supports LVDS, LVPECL and LVCMOS.

It can store the configuration in EEPROM, but is there a programmer to configure it (via an SPI interface).

[TI]  The CDCE62005 has an SPI port for programming.  The device can be programmed prior to attachment to the board by a distributor.

The EVM has a TUSB3210 USB interface and some nice software to configure it, however it would be nice if it had a breakout for the SPI to enable external CDCE62005's to be configured.

[TI]  Are you asking about an EVM for the CDCE62005 alone or are you asking about one of the DSP EVMs containing this clock generator such as the C6678 EVM?  Since you posted to the C6000 Multicore forum I will assume you are asking about the EVM contianing a DSP.  The CDCE clock generators on the DSP EVMs are programmed at power-on by the FPGA.  There is no external programming interface.  The DSP can write to registers in the FPGA to change the clock programming.

I also noticed that the USB-TO-GPIO dongle has the same part on it (TUSB3210), but is configured for I2C (SMBUS/PMBUS etc)

Would it be possible to use this ?

[TI]  To do what?  This cannot be used with the DSP EVM to communicate with the clock generators.  It is used to communicate with both the PMBUS to the power supply devices and it can be used to communicate with the USB devices if a header were added.

How does the EVM do it - is it at boot time using the FPGA ?

[TI]  FPGA - see above

I would like to replace the FPGA with an MSP430 for power and clock sequencing anyway

[TI]  This is a reasonable plan.  We will be doing something similar with our KeyStone-II EVMs.  They will contain an LM3S2D93 Stellaris Microcontroller and a UCD9090 to configure the clock generators and control the power, clock and reset sequencing.

Tom

Tom,

I believe you may have MISunderstood the questions, because they are identical to mine. I will clarify

For example, we do NOT want a distributor to program the EEPROM for us initially. We would like to be able to burn the CDCE62005's EEPROM while the IC is soldered on our own card. If there was a breakout header on the EVM card's SPI lines, we could use it to interface to our own card via a cable of some sort. Of course, our own card have a header connected to the CDCE62005's SPI lines.

So, how can we burn the CDCE62005's EEPROM using the software for the EVM, if the IC is soldered on our own card?

Regards,

Robert

Robert,

I am still confused.  If you are building your own board with a CDCE62005 clock generator and an MSP430 for clock and power control, then the MSP430 would be used to program the CDCE device.  I do not see why you would want to use the DSP EVM.  For development, you can also have a header on the SPI port to allow an external SPI controller to write the bytes ihnto the CDCE62005.

Tom

Tom

I do NOT know where you thought that there was a uC in the circuit - there are *NO* controllers of any kind on this card. Basically, we are looking at using this part on a variety of cards, and we would like to have the ability to burn the INternal EEPROM either with it soldered onto the card or not soldered on the card, but by ourselves withOUT the distributor.

So, how do we burn the INternal EEPROM on the CDCE62005 on our card that does NOT have any controllers on it, using your software that comes with the EVM card?

Robert

Robert,

I apologize for the misunderstanding.  I read the statement above and assumed that this meant your design will contain a micro:  "I would like to replace the FPGA with an MSP430 for power and clock sequencing anyway."  The alternate solution is either having a distributor pre-program the CDCE62005 devices before assembly or programming them on the board after assembly with an external SPI controller.  There are numerous SPI controllers / programmers available.  We have not qualified a specific device but a quick search on Google provides devices like the Cheetah programmer at: http://www.totalphase.com/products/cheetah_spi/.

Tom

Thanks Tom

What a shame..this is NOT an ideal solution as we would have to do a lot of our own programming. It would have been nice to simple use a breakout header on the CDCE62005EVM card and use your 'ready to go' software. This is what Analog Devices does with their Clock Generator EVMs - other than the part itself, they are identical to the TI EVMs except they actually included a breakout connector to allow for programming an EXternal device. We would prefer to use a TI device as they all have much shorter startup and lock times.

Shouldn't TI consider doing a new revision of the CDCE62005EVM and place a $0.35 header and a $0.10 jumper on it to allow for burning an EXternal device?

Lastly, will there be a newer CDCE6200xx with more outputs? The CDCM6208 looks good, but it lacks an internal EEPROM.

Robert

Robert,

Again I have a misunderstanding.  I asked for clarification previously about which EVM your were discussing and i assumed that you were asking about the DSP EVM.  Now it is clear that you are asking about the CDCE621005 EVM.  I need to defer to the clock team as I am not familiar with their features.  My expertise is focused on the Multicore DSP EVMs.

Tom

Tom,

No worries - we are involved with both. The DSP EVM because it uses the CDCE62005, but the CDCE62005 EVM because it would have potentially been an excellent tool to program our own CDCE62005 on all of our cards... which include data acquisition and a DSP card - NONE of which have a uC or FPGA tied to the SPI lines of CDCE62005.

The DSP EVM uses an FPGA to configure the CDCE62005.. making NO use of the internal EEPROM. We do indeed want to make use of the internal EEPROM. However, we do NOT want to write an application nor buy special hardware to burn a CDCE62005 IC on our card, which does NOT have a uC or FPGA on it. We would like to be able to burn the CDCE62005 using the already existing software tool/GUI that is supplied with the CDCE62005 EVM, but obviously this card was NOT designed with any foresight whereby a header connector making available the SPI lines would have made it in effect a 'dongle' to program the EEPROM of an EXternal CDCE62005.

So, we are dumping the CDCE62005 and going with a different solution using a uC - basically spending more money because of this problem.

Robert

Hi
We cancelled this project using the device, but were going to use a simpler solution -
a pin configurable device CDCM61004
I am not sure why it needs such a low jitter clock anyway  
as its mainly just a processor; other devices are using spread spectrum oscillators for example
In fact one of the reasons we discarded it is because its quite a 'needy' in terms of additional hardware:
- Requirement of a vcore programmable power supply, exact boot sequencing, the EVM is on a 12 layer board etc.

Hi,

As you mention, since the CDCE62005 requires too much development and there is inexplicably NO breakout on the EVM card, we may evaluate the CDCM6208 paired with a microcontroller instead.

Regards,

Robert

I thought programming the clock generator was relatively easy compared to the power controller.
If I recall it has an ARM processor on it that requires programming.
There is a very nice design package for it though.
Good luck with it all.

Yes Paul,

Since we are forced to develop more than what we initially wanted, we may as well byte the bullet and place a flexible uC and have it perform ALL of the initialization - this way there will not be any more surprises.

Regards,

Robert