On May 9, 2014, at 2:26 PM, Primiani, Rurik wrote: > I'm unclear why the sys_clk MMCM doesn't just have hard-coded clock > factors. Its input clock never changes and it's always outputting 100 > MHz and 200 MHz.
I think things are a little gray here. When the user specifies using "sys_clk" for the "User IP Clock Source", then I think sys_clk is in fact used and its MMCM is configured to output the rate specified in "User IP Clock Rate" rather than a fixed 100 MHz. > On the other hand, the aux_clk MMCM does seem to have its factors > hard-coded even though aux_clk can be an arbitrary frequency. Am I > missing something? I agree that aux_clk's MMCM usage seems suspect. > Side note: why are these clock factors derived in detokenize.m? Surely > there's a more appropriate place to do this? It does seem like an odd place to do this and I'm sure a more appropriate place could be found, but given that it's been there for a long time and it has worked there for a long time, I'm not sure I'd want to move it just for aesthetics sake. Dave
