Hi,

This information is defined in the Radar Interface Control Document. This document is included in the Device Firmware Package (DFP)

You can download the document from the release page. Please see in the document for " 5.8.2 Sub block 0x0181 – AWR_BPM_CHIRP_CONF_SET_SB"

Thank you

Cesar

Thank you for getting back to me, Cesar.

I have already seen this and that is why I thought the bpmChirpCfg.constBpmVal should be 0x3 as per the chart in the documentation you provided. But Kuashal in the other thread said 0x2 and I am hesitating.

Can you confirm one or the other?

Thanks!

George

Let me check with mmwave link team and get back to you

Cesar

Great, thank you!

Hi Cesar, 

Do you have an update from your mmwave link team?

Thanks, George

Hello George,

Based on mmwave SDK both bits need to set for each Tx.

But I have raised an internal request for further confirmation. I'll update you on this by this week.

Regards,

Jitendra

Hi Jitendra,

Great, thank you! Also, when you get a response, if you can clarify what you mean by both bits need "to be set" for each Tx, that would be great! 

Looking forward to hearing back from you!

George

Hello George,

Based on the latest internal feedback: off bit for Tx BPM can keep to '0'.

Firmware considers only bit for chirping time to set the BPM to that Tx.

Regards,

Jitendra

Hi there,

Thank you for asking the mmwave team about this.

Maybe that is my issue: Rather than having it be 0x3U to be used for Tx0 to transmit 180 deg chirp (which is bitmask 0011), I should do 0010 (which is 0x2U). This could be a possible fix, since you mention that the firmware only considers the ON bit for that BPM for that Tx. 

Furthermore, if I wanted to configure Tx1 to transmit 180 deg phase shift, I could do 1000 which is 0x8U. Correct?

Thank you!