This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR1843BOOST: MRRBeamsteering demo enters assert when NUM_SUBFRAMES = 1

Part Number: AWR1843BOOST

Tool/software:

Hi,

I want to build the demo project for only 1 subframe, so I open one of the following define macros:

Fullscreen
1
2
3
4
/**! @brief The USRR only mode of operation. */
//#define SUBFRAME_CONF_USRR /* One subframe USRR20. */
/**! @brief The MRR only mode of operation. */
#define SUBFRAME_CONF_MRR /* One subframe MRR80. */
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Then NUM_SUBFRAMES constant is automatically defined as 1 since SUBFRAME_CONF_MRR_USRR is not defined:

Fullscreen
1
2
3
4
5
#ifdef SUBFRAME_CONF_MRR_USRR
#define NUM_SUBFRAMES (2U) /* one for MRR80, one for USRR20 */
#else
#define NUM_SUBFRAMES (1U) /* one for MRR80, one for USRR20 */
#endif
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Then code enters assert in MRR_DSS_initTask -> MmwDemo_dataPathConfig_1D_FFT_HWA_Common -> MmwDemo_config1D_EDMA_sf1

This seems very logical to me because size of dataPathObj[NUM_SUBFRAMES] member of Mrr_DSS_MCB is NUM_SUBFRAMES:

However, MmwDemo_dataPathConfig_1D_FFT_HWA_Common function tries to achieve dataPathObj[1] regardless of NUM_SUBFRAMES:

Is this demo verified for configurations with just 1 subframe?

Thanks for any help...