if you set MOD = 0 when you use the chip as integer-N the eval software crashes, see attached pictures.
To use Integer-N mode: once your FRAC value = 0, then it doesn't matter what the MOD value is.
This is because: RFout = Fpfd * (INT + (FRAC / MOD))
if FRAC = 0, RFout = Fpfd * (INT + 0)
So for your application, set MOD to anything but 0.
The software hasn't been enabled to handle the divide by zero. So it will crash.
do I need to have MOD different from zero when I program the chip as well?
In other words if I use 4350 in Integer-N mode, do I have to set mod different from zero in R1?
Retrieving data ...