IWR1443BOOST: MMW Demo Frame periodicity

The frame periodicity in CLI is speficied in ms. Internally though mmwavelink API has a format of 1 LSB = 5 ns (you can see this in doxygen of mmwavelink or Radar Interface Control Document (ICD) as part of dfp release), hence the strange looking conversion formula. Per this, the max possible you can set is 2^32 * 5e-9 = 21 s. However the ICD says typical range is 1 ms to 1000 ms.

As far as duty cycle is concerned, it is a typo in the user guide, it should say maximum instead of minimum (we will take action to correct documentation in a future release). The 50 % is not required to be strictly adhered to but more from the stand-point of validation coverage (not talking about SDK (software point of view) validation, but chip (RF stuff etc) validation) and power consumption (e.g datasheet at www.ti.com/.../awr1443.pdf provides power consumption measurement for 50 % duty cycle in Table 5-4).

Your problem is probably something else, not the bigger idle time, let us know more details if you cannot figure it out. Just a minor side note: we use name "idle time" to designate the idle time between chirps, refer to the time diagram in section "Configuation (.cfg) File Format in the SDK user guide, what you are referring is what we usually call "inter frame period" but in the context in which you used it there is no ambiguity in understanding what you mean.