LMS7002M API and reference frequency about limesuite HOT 6 CLOSED

I agree, the reference clock can be moved to IConnection.

Some notes about reference clocks:

• SXR and SXT can have separate reference clocks, but it is most likely that they always will be set to identical values.
• CGEN reference clock is always equal to SXR reference clock.
• Fixed reference clock boards can depend from used crystal. There are EVB7 boards that use one of the 30.72MHz or 52MHz crystal.

Also it would be a good idea to match units in the APIs, so possibly switch from MHz to Hz.

from limesuite.

SXR and SXT can have separate reference clocks, but it is most likely that they always will be set to identical values.

Right the XBUF config can have different clocks in some configurations. Perhaps we can have an additional set of calls

• GetTxReferenceClockRate() //without overloading, calls GetReferenceClockRate()
• SetTxReferenceClockRate() //without overloading, calls SetTxReferenceClockRate()

Also it would be a good idea to match units in the APIs, so possibly switch from MHz to Hz.

I have made a mistake sometimes with the Hz vs MHz. :-) I like to have absolute units when possible. Hz would be preferable in my opinion.

from limesuite.

Since the parameters will be changed to Hz, we might as well change the frequency parameter types from float to int64_t.

from limesuite.

I dont know if using a 64-bit integer is worth the trouble. Like: we might end up with strange precision issues when representing frequencies with repeating decimals, like 33.333... MHz. And we would loose the ability to represent sub-hz frequencies, like CORDIC precision. Maybe in reality, this isnt such a problem but I would stick with double for all units (Hz, volts, dB, etc) unless efficiency required it.

from limesuite.

Use ref freq API: 72c316b

from limesuite.

And using Hz has its own issue: #39

Closing

from limesuite.