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.

CDCM6208 EVM connection + programming

Other Parts Discussed in Thread: CDCM6208, TUSB3410

The first few times I pluged my board to my computer through USB cable after having installed the GUI software, 'DEVICE COMM' and 'PLL LOCK' LEDs were illuminated, as well as the 'PLL Lock' and 'USB Connected' indicators on the GUI. I could change frequency options and all of that on the software.

Then I figured out that when I unpluged my board, my frequencies configuration did not remain.

What I understood was that I needed to use the EEPROM to load my program into the board. I had to install TUSB EEPROM Burner and tried to install different drivers.

Since then, when my board is connected to my computer, the on-board 'DEVICE COMM' and 'PLL LOCK' LEDs are NOT illuminated but the GUI 'PLL Lock' and 'USB Connected' DO are. Also, I can 'Read All' the registers of the CDCM6208 and every single bit is set to '0' except the bit 0 of the register 0.

In summary, I can't find any clear explanations on how to properly load a configuration into my board and I would like to get some help.

Thanks,

Simon

  • Notice that I successfully loaded the latest firmware of the CDCM6208 by using the 'TUSB3x10 EEPROM Burner' application and the 'CDCM6208Fw' firmware binary. But the board is no longer recognized by the GUI software (in the Device Manager, two TI drivers are located in the 'Human interface device' section).

    Simon
  • I managed to program my configuration on the board through the JTAG port to the MSP430.

    But I still can't have the communication between the CDCM6208 and the USB.

  • Hello Simon,
    it seems to me you mixed two descriptions which float around here on the forums with an application report which you seem to refer to.

    Let me clarify:
    The CDCM6208 has internal ROM which is fixed. A saved ROM page can be selected in the "pin mode". Otherwise the device can be re-programmed when switching to I2C/SPI serial interface.

    The customer EVM supports three modes of operation:
    1) Pin mode, select a certain ROM page by placing the pin header jumpers.
    2) Serial interface mode, program the device using the GUI software. (The GUI also contains all silicon ROM configs, so that you can "emulate" by writing the exact same registers settings through the serial interface.)
    3) Boot-Loader using MSP430, we placed a small MSP430 on the EVM. This way you can re-use the MSP430 Flash as an EEPROM for the CDCM6208. This way you can save your own custom register settings in a non-volatile memory. The MSP430 takes care of the start-up process (release RESET etc.) and configuring the CDCM6208 using SPI serial interface.

    The GUI software communicates to the CDCM6208 through an USB micro-controller - namely the TUSB3210 with a custom firmware. The TUSB3210 has a ROM only, too. Therefore there is a dedicated I2C EEPROM next to it.
    The information which you seem to have found on E2E is about patching the firmware for our GUI, not the MSP430 which you intended to use as an memory for your CDCM6208 config.

    Please refer to the application note "SCAA121" how to use the MSP430 as a boot-loader for CDCM6208.

    About how to get your EVM working again:
    1) Open all switches of SW3.
    2) Close SW4.
    3) use the TUSB3410 EEPROM burner (SLLC443) description to erase the whole EEPROM. Enable the "program full binary" option (yellow triangle). Select 512kBit. Program the full binary image while selecting the correct device type "TUSB3210".
    4) Disconnect and re-plug the USB cable. Go into the "Device Manager". Check in the USB device group that you see a device called "Texas Instruments Clock EVM Board" with a VID 0x451 and a PID 0x1E05.
    5) With SW1,SW2 switches set for SPI...you should be able to read from the device.

    When you are testing to program using the MSP430 and then reading back using the GUI: please ensure that you set all pin header jumpers to SPI.

    Please let me know when you need further information.

    Best regards,
    Patrick

  • Hi Patrick and thank you for your clear answer.

    I followed your instructions and it happens to be communicating again. Actually, I proceeded the same way before you answered except that I didn't notice the full binary option.

    This problem is solved but I do have to face another one and I would be pleased to see you helping me.
    I created a new topic you may find at e2e.ti.com/.../518823

    Thanks,
    Simon
  • Hello Simon,
    glad to read you got it working again. The team will check out your other request soon!

    Best regards,
    Patrick