AWR6843: rtiGetCurrentTick

Cherry Zhou

Mastermind 22235 points

Part Number: AWR6843

Hi team,

Here's an issue from the customer may need your help:

The following figure shows the RTI-related code generated using the HAL tool:

When fetching the RTI current tick, tick = RTI_CNT_FRCx - (RTI_CMP_COMPx - RTI_CMP_UDCPx)

Why the above design? From the customer's understanding, the values of RTI_CMP_COMPx and RTI_CMP_UDCPx should be consistent because the UDCP values are loaded into the COMPx registers, please see figure below:

Could you help check this case? Thanks.

Best Regards,

Cherry

over 2 years ago

0 Kevin Ortiz over 2 years ago

TI__Expert 3525 points

Hi Cherry,

Just checking, is this related to below issue?

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1206719/awr6843aop-awr6843isk-rti-free-running-counter

Best Regards,

Kevin

0 Cherry Zhou over 2 years ago in reply to Kevin Ortiz

TI__Mastermind 22235 points

Hello Kevin,

Yes, this query is submitted by one customer, you could merge it as one if needed.

Thanks and Regards,

Cherry

0 Kevin Ortiz over 2 years ago

TI__Expert 3525 points

Hi Cherry,

RTI_CMP_UDCPx is a value of periodicity we want to generate compare interrupts at. In other words, if this value is 100, then we will generate compare interrupts every 100 tick. The value of RTI_CMP_UDCPx is automatically added to the value of RTI_CMP_COMPx every time a compare interrupt occurs. For example, see below configuration:

RTI_CMP_COMP1 = 50

RTI_CMP_UDCP1 = 100

Once the counter reaches 50, then RTI_CMP_COMP1 value will be updated to 50+100=150. Then, at count=150, the RTI_CMP_COMP1 will be updated to 250 and so on.

Therefore, the function rtiGetCurrentTick() returns the tick of that specific compare cycle.

Best Regards,

Kevin

Sensors

Sensors forum

AWR6843: rtiGetCurrentTick