Hi team,
If the DPLL input is programmed into non-volatile memory to use the XO pin by default, how to change the input to INx pin instead?
Can this be programmed, or is achieved by external circuitry?
Regards
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.
Hi team,
If the DPLL input is programmed into non-volatile memory to use the XO pin by default, how to change the input to INx pin instead?
Can this be programmed, or is achieved by external circuitry?
Regards
Hi David,
If customer would want to change default input clock after having programmed EEPROM the customer would have to re-program the EEPROM to reflect this change.
LMK05028 supports up to 100 cycles of EEPROM config changes.
Regards,
Vicente
Hi Vicente,
Thanks for the response. Adding several questions here.
1. The customer is considering re-program the EEPROM using I2C without TIC Pro GUI, is this possible? Is there a way to know the register address and description?
2. What happens if the EEPROM configure changes more than 100 cycles? Does this cause any malfunction to the device?
Regards,
Hi David,
1. Have customer refer to section 9.5 of DS which goes over programming and register information. Programming information starts on page 67.
2. After 100 cycles, TI cannot guarantee DS performance. The more write cycles you perform on non-volatile memory, the more the EEPROM health degrades which affects storage integrity.
Regards,
Vicente
Hi Vicente,
Thanks. Is it possible to export the GUI register setting to txt file or csv file?
If customer would want to change default input clock after having programmed EEPROM the customer would have to re-program the EEPROM to reflect this change.
Also, customer the customer wants to switch input from XO to INx while the device is locked to XO(When the device is working). Is there any way to achieve this?
Regards
Hi David,
This is possible.
I understand the XO is used as a reference only in holdover mode when primary input is lost. When the device is locked and working, INx is used.
Regards,
Vicente
Sorry forgot to acknowledge your config question.
Yes, inside TICSpro GUI, you can export HEX register values as .txt file.
Regards,
Vicente
Hi Vicente,
Thanks for the response.
With the GUI export function I only found register addresses as below, is there additional setting required for full register values?
R0 0x000000
R1 0x000100
R2 0x000200
R3 0x000300
R4 0x000400
R5 0x000500
R6 0x000600
R7 0x000700
R8 0x000800
R9 0x000900
R10 0x000A00
・
・
・
Regards,
Hi David,
if all register values are 0, there is an issue with your configuration...
I loaded the EVM default configuration and exported the register values as .txt file without any issue.
Regards,
Vicente