Hi Glenn, Dave,
Looks like the clock measuring mechanism is only if you use a usr_clk input.
It may be tricky to give the adc_clks the same functionality, due to the way
the ADC clocking infrastructure is done, but it shouldn't be too hard to
have the toolflow conditionally remove the clock measuring software and
gateware if you're not using a user clock.
Thanks,
Henry
G Jones wrote:
I am also interested in this. I see that the clock measure and reset
functionality seems to be implemented in
/pcores/opb_clockcontroller/hdl/user_logic.vhd
All of the logic in there seems like it should work, but when you look
at the system.mhs file, the relevant signals are connected to dcm_2 in
my case, which has its CLKIN signal connected to net_gnd, which explains
why it always reads 0. It would be great if this could be connected to
the ADC's DCM, but I don't know how to access that as I don't see it in
the mhs file.
Glenn
On 6/5/08, *David MacMahon* <[email protected]
<mailto:[email protected]>> wrote:
Does anyone use the clkmeasure command on the ibob? It always
returns...
Clock frequency: 0.0000 Mhz
Current phase : 0 degrees
...for our ibobs that are using ADC clock (that is definitely more
than 0.0000 MHz). Which clock is it supposed to be measuring? If
it's not used or usable, can we please eliminate it? It takes up
valuable software space.
Likewise for the "clkreset" and "clkphase" commands.
Thanks,
Dave
