Replies: 1 comment
-
|
what the hell! right?
The external clock (XCLK) is first divided by a pre-defined value to ensure the input to the PLL is within a specific range (6-27MHz). Constraints: Calculation: Are you kidding me? 2400MHz (VCO) !!! no wonder it is on fire! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
either i am going crazy, or i am crazy!
i don't understand, what kind of clocking is this? on ov5640, in the esp driver, we have this:
set_pll(sensor,/*pll_bypass*/ false,/*pll_multiplier*/ sys_mul,/*pll_sys_div*/ 4,/*pre_div*/ 2,/*root_2x*/ false,/*pclk_root_div*/ 2,/*pclk_manual*/ true,/*pclk_div*/ 4);and then we have this:
or in full, we have these:
and in other part, in a nutshell, we have this:
but, i don't get it!
and After trying the various combinations, reading various documentations spread around the net, and from the various feedback, the clock tree is probably as follows:
and then they say you have to use 24MHz for input clock to get the full range clock working to get maximum frame rate. if so, why the fuck they are dividing the input clock??? first divide by 2 and then by 4? am i crazy? what am i missing? while creating 24MHz clock is so hard and unstable.
Beta Was this translation helpful? Give feedback.
All reactions