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.
Part Number: LMK04828
Hello TI experts,
I have a question which I tried to solve in the thread:
...and it turned out that the problem was that on the eval board of TI the ADC sample clock disappears when the ADLY is set to 950 ps and when "ADLY Input" is set to "Divider". However when we set "ADLY Input" to "Divider + DCC" then the ADLY is not affecting the output signalThe datasheet is not very explicit on the "DCLKoutX_ADLY_MUX". It states on page 57: "This register selects the input to the analog delay for the device clock. Used when DCLKoutX_MUX = 3." on the other hand on page 35 in the diagram it looks like DCC is after the ADLY stage.
Now my question: Why does this bit influence the output signal when only the ADLY is changed?
Hi Goran, I have assigned a responsible engineer to your post. He will get back to you soon. Kind regards, Lane
To design your own Clock Tree solution, visit WEBENCH Clock Architect !
More information Clock and Timing System products: http://www.ti.com/clock-and-timing/overview.html
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
To design your own Clock Tree solution, visit WEBENCH Clock ArchitectMore information Clock and Timing System products: http://www.ti.com/clock-and-timing/overview.html
In reply to Timothy T:
In reply to Goran Marinkovic:
>"You are correct about the figure 13. The DCC and Analog delay are swapped. The DCC block to be consistent should also be labeled HS/DCC, for half step & duty cycle correction. Please refer to Figure 12 which gives the detailed flow of the output channel." Fine. > "The be consistent on ordering an mux values, Figure 12 should have the top input connect to before HS/DCC and the bottom after HS/DCC." I think the drawing is ok since you may define the lower input on the MUX to be DCLKoutX_ADLY_MUX = 0 and the upper to be DCLKoutX_ADLY_MUX = 1. And the drawing is more clear if there are less crossing of wires. >"About the control of this feature, referring to figure 12. You can see the DCLKoutX_MUX (2 bits) selects from one of four sources. The forth being the analog delay path. When using this forth analog delay path, there is a second control DCLKoutX_ADLY_MUX which selects the HS/DCC mode. On page 19, it is clarifying the mode of operation being analog delay. However the typo may be the omission of the DCLKoutX_ADLY_MUX = 1." Sure, it is a tpyo. Since the path should be DCLKoutX_MUX = 3. According to the datasheet DCLKoutX_ADLY_MUX makes only sense if DCLKoutX_MUX = 3. Which is consistent with my reports. The following makes never sense: DCLKoutX_MUX = 4! Hence please correct your datasheet for example as follows: DCLKoutX_MUX = 3 and DCLKoutX_ADLY_MUX = 1. This works (except the reported settings causing the reported problems) "As for the ADS54J60EVM, I think the ADLY input (DCLKoutX_ADLY_MUX) on the LMK04828 : SYSREF and SYNC tab should have been placed next to DCLK source (DCLKoutX_MUX) on the LMK04828 : Clock Outputs tab." "Having set the DCLKoutX_MUX = 3 and DCLKoutX_ADLY_MUX = 1, you should find the ADLY output works for the full range?" Yes, this is what we do, and yes it works as we confirmed by measurement and documented in the logs before. "I was able to confirm that without enabling HS/DCC (DCLKoutX_ADLY_MUX = 1), I noticed the same issue you had." What are the next steps? Whatever you do, let me guess it will take some time. Hence, please keep me posted when your experts find out why this happens... I try to understand the problem rather than having to rely on a empiric finding. Cheers... or as well 73 to you Goran
Goran MarinkovicThe following makes never sense: DCLKoutX_MUX = 4! Hence please correct your datasheet for example as follows: DCLKoutX_MUX = 3 and DCLKoutX_ADLY_MUX = 1.
I've added it for update.
Goran MarinkovicWhat are the next steps? Whatever you do, let me guess it will take some time. Hence, please keep me posted when your experts find out why this happens... I try to understand the problem rather than having to rely on a empiric finding.
I've discussed this with a designer and I'll keep you posted.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.