Hybrid MDLL for Low
jitter Clock Gen
Instructor: Dr Benton Calhoun
Md. Fahim Foysal (gfm7vw)
Maliha Maliat (kaj4aq)
This project presents a new hybrid MDLL (Multiplying Delay lock loop) architecture that can reduce the jitter of an on-chip oscillator circuit with low power consumption which comprises a dual feedback loop feature. The primary negative feedback loops reduce the jitter within the MDLL whereas the additional negative feedback loops minimize the variance in delay time across each stage of delay. Incorporating both sets of negative feedback loops in a DLL further diminishes the clock signal jitter. Measurement results of the hybrid MDLL-based clock generator with dual negative feedback loops designed in 65nm TSMC process show 2.5-ps periodic jitter and 9.32-fs rms jitter at 200MHz with a power consumption of 328 µW.
Design review 1 file: Design Review I
Feedbacks:
publications: Good.
review quality: Your summaries are pretty good and focus on metrics
simulation quantity: built working basic RO. One comparison table.
Simulation quality: Good progress was made to get a working component, although it's simple. Would be nice to see you exercise some design tradeoffs. The P-f plot is unclear; is it non-monotonic? Seems like something could be wrong.
The comparison table would be better to show as some plots that compare metrics to show a design space; where in the design space are you trying to explore for your project?
report: Good simple summary of prior work. Work on getting more specific about the research questions or interesting tradeoffs you will explore
tasks: Too simple
You need to be more specific with a target research question or tradeoff(s) that you plan to explore before the proposal.
Project proposal file: [Project Proposal ]
Feedbacks:
Problem - your research question deals with lower jitter and power
Approach - The approach explores hybrid architectures
Design - clock gen circuits
Novelty - Pulls from several references
Outcomes -
Refs - a SOA scatter plot
wiki page - not created
Plan - Simple - I suggest adding detail.
Timeline/tasks -
Simulations - Const-gm and RO; Need to make rapid progress with sims! Need to figure out how to simulate jitter.
Design Review II file: Design Review II
Feedbacks:
more pubs: ok
Design description:
Simulation quantity:
-- Good; multiple components working along with DLL
Simulation quality:
-- schematics hard to read; plots hard to see legends; you MUST clean up the quality, especially of the schematics -- Fig 4, 8: what does negative efficiency mean?! -- Fig 7: why is the ripple negative?
-- it is not clear that you are using "efficiency" and "ripple" correctly; the plots are wrong if you are using those terms in the conventional definitions.
Report:
-- Very nice progress!
-- Make sure you do a good job telling the story of your project; WHY are you investigating this? What is the hypothesis / claim? What reasons do you have for exploring this? How well (or not) is it working? How does it compare to prior work (very important!)?
Presentation file: ECE6332_Foysal_Maliat_Final Presentation
Feedbacks:
Approach (1-2 sentences): Target lower jitter at mW of power.
MDLL improves jitter performance and has phase control scheme; deterministic jitter and random jitter are 2 types. MDLL reduces jitter but deterministic jitter accumulates over time, so we propose method to reduce that at low power. Found [4] w/ dual feedback. Combined DVVC w/ MDLL for hybrid.
s5.bias - Do have bias ckt on s6. Stability of bias? A. <you said this out loud but did not show on a slide> s7. Why is MDLL lower jitter? (where are MDLLs on s4 SOA?) A. <> s9. Are those ideal supplies in the schematic? A. <>
s12. How did you simulate the jitter? A. Cadence takes input signal for jitter; made RO w/ jitter – did NOT provide input Q. did it compare realistically to SOA? A.
Results (1-2 sentences):
s15/s16. Why is power for hybrid so much higher? A. there are more circuits switching <not a convincing answer – it’s not clear that the power would be SO much higher!
Strengths / Weaknesses: strength: impressive amount of implementation, mostly copying papers but combining 2 elements weakness: you’re unclear on how you captured jitter in the sim, and the quantifiable results aren’t compared apples-apples with SOA Answers to Q&A were not very clear / convincing
Comments:
Q. s4. Why is jitter showing a floor? How do you propose to beat by 10x-100x? A. are those SOA measured? A. yes <comparing sims to SOA measured>
Final Presentation preview