AWR1642: To support 1024 unique chirps which exceeds the maximum support unique chirp number 512

Hi Andy,

You can use advanced frame configuration and define 2 sub-frames with 512 chirps in each sub-frame. Configure 2 profiles and configure 512 unique chirps and use FORCE_PROFILE option to switch between the 2 profiles across sub-frames. This would avoid the need for real time configuration of chirps. This would give you 1024 unique chirps in a frame, though the dither parameters, BPM bits etc. will remain same across sub-frames, but the chirps will be associated with different profiles across sub-frames giving the uniqueness to the chirps.

Thanks,
Sumeer

Hi Sumeer,

Understood and thanks for your comments. I checked the SDK 1.0 code, the advance frame configuration is supported in the mmwavelink level but not supported in the mmwave level, right? Will it be supported in the mmwave level in the next sdk version? If not customer has to implement it by themselves.

For advance frame configuration, is the process same with common frame configuration through using the chirp available and frame start event?

BR,
Andy

Hi Vivek,

Thanks for your comments.

The advance frame configuration cannot satisfy with the customer's requirement, we tried to do sensor reconfiguration after one frame process completion in below steps.
Sensor stop -> flush cfg -> update the profile, chirp and frame configuration -> sensor start.

In the mmw demo, there is below code to generate clock timeout event.

/* start the clock; this is to handle the case when there
are no active chirps and DSP received the STOP request*/
Clock_setTimeout(gMmwDssMCB.frameClkHandle,
(1+(UInt)(gMmwDssMCB.cfg.ctrlCfg.u.fullControlCfg.u.chirpModeCfg.frameCfg.framePeriodicity/100000)));
Clock_start(gMmwDssMCB.frameClkHandle);

The timeout is too long, we tried to decrease the timeout value, then sometimes it entered the below fault branch. I didn't find what would cause the issue, would u pls help instruct what maybe the cause and how to fix it?
MmwDemo_dssMmwaveEventCallbackFxn()
{
......
case RL_RF_AE_CPUFAULT_SB:
{
/* BSS fault */
DebugP_assert(0);
break;
}
......
}
Thank u very much & BR,
Andy

Hello Andy,
Could you clarify what was the requirement that could not be met by the advanced frame config?

Regards,
Vivek

Hello Andy,
You are right, this particular case would not be satisfied with advanced frame config if they need 512 unique chirps in the ramp up and ramp down. In that case you can transmit single frame (in frame config) with the offset values of the ramp up sequence and then reconfigure the chirp config offsets with the reducing start times and transmit another frame.

Regards,
Vivek

Hi Vivek,

Thanks for your comments. About reconfiguration, is it able to just reconfigure the chirp at MSS? Or is it also need to do sensor stop and restart?

BR,
Andy

Hello Andy,
Once you trigger the frame using sensor start you need to wait till all the frames have transmitted (in this case say you have configured only one frame in the frame config). After that time you can reconfigure the chirp config and frame config and give a sensor start again with the new configuration.
If you wait till the frame transmission is done you need not give SensorStop since it will automatically stop after the number of configured frames are transmitted.

Regards,
Vivek

Hi Vivek,

Let me understand again, in my use case with only one frame it is just need to reconfigure the chirp and and give a sensor start again, why it is need to do frame reconfigure again?
Thanks & BR,
Andy