AWR1443: Profile Configuration- Range Bin Parameter Limits

Here are some good resources to help with creating your own configuration file.

1.  Use mmWave Studio to calculate the chirp parameters
2. Table 1 in the Configuration File Format section (3.5) from the mmWave SDK User Guide. This User Guide can be found in the Docs folder of the mmWave SDK (C:\ti\mmwave_sdk_<ver>\docs). This table identifies and provides a description for each parameter.
3. To find the ranges of the Profile Cfg parameters, you can refer to the documentation on the profileCfg struct. This can be found in C:/ti/mmwave_sdk_<ver>/packages/ti/control/mmwavelink/docs/doxygen/html/structrl_profile_cfg__t.html

To specifically address your question, these range bins represent the number of ADC samples to capture in a chirp for each RX.

The reason the parameter doesn’t work below 64 is because the valid range for the “number of range bins” parameter is 64 to MAX_NUM_SAMPLES.

Where MAX_NUM_SAMPLES is such that all the enabled RX channels’ data fits into 16 kB memory, with each  sample consuming 2 bytes for real ADC output case and 4 bytes for complex 1x and complex 2x ADC output cases

For example:

• 4 RX, Complex ADC output -> MAX_NUM_SAMPLES = 1024
• 4 RX, Real ADC output -> MAX_NUM_SAMPLES = 2048
• 2 RX, Complex ADC output -> MAX_NUM_SAMPLES = 2048
• 2 RX, Real ADC output -> MAX_NUM_SAMPLES = 4096

The reason why the minimum is 64 is an API choice that was made on the BSS firmware. There is no such restriction from the hardware. However, the BSS firmware is not something we will provide a custom version of.