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.

CDCE6214-Q1EVM: EEPROM write from .tcs file

Part Number: CDCE6214-Q1EVM

Hi,

This is an inquiry from our customer.
Using TICS.Pro to write the settings to EEPROM with the .tcs file open will result in an error.

Is this operation correct?

There is no problem in writing the .hxt file to the EEPROM and reading it and saving it as the .hxt file. So, it seems that there is no problem with the connection with USB ANY2.

Can you tell us something from the attached error message?

On the other hand, after reading the .tccs file, pressing "Write All Regs" seems to be able to write.

Is it possible to write to EEPROM by this operation?

My customer inquired because it is necessary to send this IC to the END user after writing the data to the EEPROM using EVM.

What is the correct procedure for writing data from a .tcs file to EEPROM?

Best regards,

Hiroshi

  • Hi Hiroshi,

    Can you verify if the EEPROM was correctly written by testing the output frequencies of the chip? The error message might not be real.

    Regards,
    Hao

  • Hi Hao san,

    It is said that OUTPUT cannot be checked because it is a company that only writes data to Memory. They have been asked to make 100 copies and provide them to the end user.

    Customer comments
    ================================================
    As a result of clicking "Wite All Regs," it should be written to EEPROM. I confirmed it by the following procedure.

    // Click "Write All Regs" from the .tcs file to write to EEPROM
    // Read the EEPROM and save it in a .hxt file.
    // For writing to the device (making 100 duplicates), click "Wite File to EEPROM" to write the saved .hxt file.
    ================================================

    Is this procedure the correct way to write to EEPROM?
    I compared the original .tcs file with the .hxt file I created
    I didn't know if the contents of the EEPROM were the same.

    Best regards,

    Hiroshi

  • Hi Hiroshi-san,

    The procedures don't seem correct. Clicking "write all registers" only writes all the registers to the device (volatile memory). It does not write anything to EEPROM (non-volatile memory). After writing all registers, you need to then write the EEPROM using register commit method (only for the 1st device). Make sure you select the right EEPROM page. After writing to EEPROM, the user should power cycle the board, test all its functionalities and make sure that EEPROM is correct. 

    After that, read back EEPROM from file and now you get the final EEPROM setting. For all future devices, use direct access method and write this file to EEPROM. It is also recommended to read back the EEPROM again and compare that to what was written. All 64 bytes of EEPROM image should be exactly the same. In short, use register commit method for evaluation purpose and get the first EEPROM file. After EEPROM file is obtained, use direct access method in production.

    Regards,
    Hao