AWRL6432BOOST: Runtime temperature calibration in non-low power mode

jungbum shin

Prodigy 140 points

Part Number: AWRL6432BOOST
Other Parts Discussed in Thread: AWRL6432, AWRL1432

Tool/software:

Hello, TI experts,

I'd like to ask temperature calibration usage for runtime in non-low power mode.

In low power mode,

MMWave_openLink() function is performed temperature calibration and compensation at initial state after deep sleep wake-up.

1. rl_fecssTempMeasCfg() : This API configures for temperature measurement

2. rl_fecssTempMeasTrig() : This API triggers measurement

3. Compare temperature current bin and old bin.

4. rl_fecssRfRuntimeCal() : Temperature calibration compensation

but in non-low power mode,

It is just performed at initial state after booting once. so I'm trying to create function for runtime temperature calibration in dpc_excute().

Can I use these APIs in dpc_excute() function while loop for temperature calibration in non-low power mode? Is there any side effects?

Please let me know if I have wrong understanding.

Thank you.

Best Regards,

5 months ago

0 Cesar 5 months ago

TI__Guru*** 148944 points

Hi,

The answer provided in this thread for AWRL1432 also applies to AWRL6432

(93) AWRL1432BOOST: Runtime temperature calibration - Sensors forum - Sensors - TI E2E support forums

Thank you

Cesar

0 jungbum shin 5 months ago in reply to Cesar

Prodigy 140 points

Hi, Cesar

MMWave_openLink() function is just once called initial state in non-low power mode.

In low power mode, it is called every initial state after deep sleep.(compare temperature pervious and current bin difference in that function and set bin index)

So, low power mode is automatic.

but, non-low power mode is not automatic, just calling once after booting.

I think temperature calibration and compensation is performed by rl_fecssRfRuntimeCal() in MMWave_openLink().

so, In non-low power mode, for temperature calibration and compensation every cycle, rl_fecssRfRuntimeCal() is needed to call every cycle in processing while loop of dpc_excute().

Is this a possible implementation?

Could you check my understanding?

Thank you.

Best Regards,

0 Cesar 5 months ago in reply to jungbum shin

TI__Guru*** 148944 points

Hi,

rl_fecssRfRuntimeCal() must be called only one time if there is no low power mode.

If low power modes is used than rl_fecssRfRuntimeCal() must be called every time the device comes out of low power mode.

thank you

Cesar

0 jungbum shin 5 months ago in reply to Cesar

Prodigy 140 points

Hi, Cesar

Thank you for your answer.

I'm little confusing, the reason why In MMWave_openLink(), check previous and current temperature and set.

In non-low power mode, rl_fecssRfRuntimeCal() is called once at init state. so temperature comparing and setting is not performed every cycle. just only booting time.

When the rl_fecssRfRuntimeCal() function is called once at init state,

if the temperature is compensated for the entire runtime, does such temperature comparison happen automatically? Or does compensation happen continuously without such temperature comparison?

In MMWave_openLink(),

Thank you.

Best Regards,

0 Cesar 5 months ago in reply to jungbum shin

TI__Guru*** 148944 points

Thank you for the additional information. I understand now your concern.

Let me check with the firmware team and get back to you before end of the week.

Cesar

+1 Cesar 5 months ago in reply to Cesar

TI__Guru*** 148944 points

Hi,

I was able to discuss with the firmware team regarding this issue.

Your understanding is correct.

For the 1432/6432 devices, the RunTime Calibration is controlled by the application and not the firmware like on 6843/1843 devices.

So, this means that the application must decide when to perform the temperature measurement and, based on the results decide to perform or not the RunTime calibration.

So, for the non-low power mode the application code must be updated to perform the temperature measurements and RunTime Calibration.

The frequency of these measurements must be decided by the application developer.

Thank you

Cesar

0 jungbum shin 5 months ago in reply to Cesar

Prodigy 140 points

Hi, Cesar

Thank you for your checking and explanation.

Best Regards,