AWR2243: After RFInit, call MMWL_ RunTimeCalibConfig will send the asynchronous event of the slave's Run time Calib Report every 1s

HuaChao Sheng

Part Number: AWR2243

The Parameters We set：

（1）Run time config：

（2）CalMonTimeUnit：

In the MMWL_App function , after the completion of RfInit, the MMWL_RunTimeCalibConfig function is called in the MMWL_DeviceConfig, as shown in the diagram below:

At this time, the master-slave (2-chip cascade) Run time Calib Report will be triggered (we believe this is correct)

（3）

However, during the normal chirp transmission process of the RF (we set the RF to automatically transmit frames), the slave will continue to send asynchronous events, such as the Run time Calib Report, every 1 second or so. After about 10 seconds,

The RF no longer sends chirp, but the asynchronous event Run time Calib Report of the slave continues to trigger. The screenshot of the serial port is shown below：

The red line is the printed information of the normal RF chirp transmission. As you can see, only the Run time Calib Report is printed after it.

How can I solve this? Thank you!

over 1 year ago

0 Pradipta Bandyopadhyay over 1 year ago

TI__Mastermind 32825 points

Hi,

As per the ICD

If the calibration reports are enabled, you should receive the reports every 1 sec for the internal calibrations. So this is expected behavior. If you do not want the reports you can disable them. You will only be notified if a calibration failure happens.

Thanks,

Pradipta.

0 HuaChao Sheng over 1 year ago in reply to Pradipta Bandyopadhyay

Prodigy 40 points

Hi,

Yeah, I know. My question is:

We configured RF to automatically send frames. If the calibration reports are enabled, and the frame will stop sending after about 5 seconds. Host had not received any error report. If the calibration reports are disabled, frame was sent normally.

0 HuaChao Sheng over 1 year ago in reply to HuaChao Sheng

Prodigy 40 points

We want to find the reason, and how to solve it.

0 Pradipta Bandyopadhyay over 1 year ago in reply to HuaChao Sheng

TI__Mastermind 32825 points

Hi,

As per the mmwave radarss release notes

Can you follow the above workaround as you are using the overrides. Let me know if this resolves the issue at your end.

Thanks,

Pradipta.

0 HuaChao Sheng over 1 year ago in reply to Pradipta Bandyopadhyay

Prodigy 40 points

Hi，

It still hasn't solved our issue.

Let's change the question: we want to calibrate in real time based on temperature changes. How can we do it? Are there any sample programs?

0 Pradipta Bandyopadhyay over 1 year ago in reply to HuaChao Sheng

TI__Mastermind 32825 points

Hi,

The AWR_RF_TEMPERATURE_GET_SB API can provide you the temperature information. Based on that you can perform your calibrations.

Currently there is no sample code for this exact purpose.

Thanks,

Pradipta.

0 HuaChao Sheng over 1 year ago in reply to Pradipta Bandyopadhyay

Prodigy 40 points

Hi,

Yeah, that's what we done.

We still have some questions.

1) Why does opening the report always trigger asynchronous events and affect the automatic sending of chirp?

2) Run time config is as follows:

CalTempIdxOverrideEn must be Enabled? If we enable CalTempIdxOverrideEn, Are these three parameters (CalTempIdxTx & CalTempIdxRx & CalTempIdxLodist) fixed values or do they change with temperature?

0 Pradipta Bandyopadhyay over 1 year ago in reply to HuaChao Sheng

TI__Mastermind 32825 points

Hi,

Let me check on this internally once and get back to you by next week.

Thanks,

Pradipta.

0 HuaChao Sheng over 1 year ago in reply to Pradipta Bandyopadhyay

Prodigy 40 points

Hi,

Ok, Thank you very much.

0 Jitendra Gupta over 1 year ago in reply to HuaChao Sheng

TI__Guru 69960 points

Hi,

As per your configuration, I see that you have not enabled run-time calibration (calibPeriodicity =0), then you should receive run-time calibration reports from that device.

I assume you can invoking oneTimeCalibration manually from the application (Please confirm), which is generating async-event for oneTimeCalibration report.

Have you enabled Monitoring feature as well with the above flow?? What is monitoring report mode in that case?

And when you say frame stops, i.e. no ADC data received from that device over CSI2?

Ideally with infinite frame configuration if frame stops in b/w, then BSS must send the failure async-event (e.g. CPU fault) you are sure that you are not getting any??

You can optionally proceed with async-event report disable for calibration, as I see from the report that all the calibration status are passed, so you disable run-time calibration report option in the application.

Regards,

Jitendra

0 HuaChao Sheng over 1 year ago in reply to Jitendra Gupta

Prodigy 40 points

Hi,

(1) yeah,I invoked oneTimeCalibration manually. and I had not enabled any monitors.

(2) We observed from the FPGA that there was no ADC data from the slave chip, but there was ADC data from the main chip (we used two chips in cascade).

(3) Just no adc data(slave chip), no any fault from BSS

0 Pradipta Bandyopadhyay over 1 year ago in reply to HuaChao Sheng

TI__Mastermind 32825 points

Hi,

We will need to check as to why the slave device is not providing data. Can you help with the below points.

1) Please refer to Q4 in the below FAQ. Please collect the logs from BSS and MSS form the slave chip so that we can get more idea as to what is happening on the slave side.

(+) [FAQ] Queries related to mmWave DFP - Sensors forum - Sensors - TI E2E support forums

2) Also, please measure the current on the slave chip. By the current consumption graph we can understand if the slave is chirping or in idle state.

Thanks,

Pradipta.