STM32H755 - RTC->SSR & RTC->SHIFTR

[ravo]

Dears, I have issues with setting RTC shift register.

I have setup RTC with AsynchPrediv = 127 & SynchPrediv = 255 and is working normally.

I tried to periodically setting RTC->SHIFTR with value 100 each 5 secs. Then wait for the shift operation to complete and immediately I read SS back using register RTC->SSR register. But RTC->SSR provide "random values" in PREDIV_S range (0 - 255). I expect that it should be lower than 100 but close (not higher)

Where could be problem ?

Thanks in advance

Radim

Example code:

 

 

int main(void)
{
 unsigned this_ssr, tick, tr, dr;
 reset_backup_domain();
 ...
 /* Initialize all configured peripherals */
 MX_GPIO_Init();
 MX_USART3_UART_Init();
 MX_RTC_Init();
 ...

 // Turn on shadow registers to speed up RTC operations
 HAL_RTCEx_EnableBypassShadow(&hrtc);
 ...
 
while(1)
{
 __HAL_RTC_WRITEPROTECTION_DISABLE(&hrtc);
 HAL_PWR_EnableBkUpAccess();
 RTC->SHIFTR = 100; // test value 
 // Wait for the shift operation to complete
 while ((hrtc.Instance->ISR & RTC_ISR_SHPF) != 0) {}
 HAL_PWR_DisableBkUpAccess();
 __HAL_RTC_WRITEPROTECTION_ENABLE(&hrtc);
 
 /* Read all 3 registers. */
 this_ssr = READ_REG(RTC->SSR);
 tr = READ_REG(RTC->TR);
 dr = READ_REG(RTC->DR);
 
 HAL_Delay(5000); // wait cca 5 sec
}

 

 

 

[waclawek.jan]

> I expect that it should be lower than 100 but close (not higher)

Why would you expect that?

Note, that as consequence of shift, SSR can even get higher than the synchronous prescaler - description of SSR register warns for that.

JW

[ravo]

Dear  @waclawek.jan ,

thanks for response. Yes of course I have omitted this, I of-course read TRM but I must have been so blinded! Thanks for mentioning this, this is clear for me. But I have follow up problem with adjusting RTC:

I would like sync RTC clock to precise using SNTP timestamps (I have verified timestamps, received correctly, calculated time difference and remaining msec.

(1) When using LSE for RTC clock I can use RTC->SHIFTR to correct msec offset and (RTC tuned with 3-6 msec diff) (LSE = 32.768kHz, prescaller async = 127 & sync = 255 ) to produce 1Hz

(2) Firstly I tested with HSE clock and it was annoying me there... when selecting HSE for RTC clock ( 25 Mhz divided by 25 to make 1000kHz RTC clock source with async = 99 and sync 9999 (or tested also with async=124 and async=7999) I have still errors (after writing to RTC->SHIFTR it looks that subseconds is not tuned and their are hopping between hundred msec in their full range for example +172; +544; +260; +186; -271; -268). It looks that there could be something wrong with prescallers settings here.

 

Both codes are tested verified that RTC is ticking normally, and there are exactly same code except MX generated RCC settings and ASYNC/SYNC prescallers for RTC.

Do you have Ideas what could be wrong ? Or the HSE as clock input for RTC is not suitable for this task ?

Many thanks in advance for your help

Regards

Radim

[waclawek.jan]

>  it looks that subseconds is not tuned and their are hopping between hundred msec in their full range

Software error, not taking into account the changed synchronous prescaler properly in the shift amount calculation?

Try only *one* shift, noting down the deviation before the shift, amount of shift, and deviation after the shift.

JW

 

[ravo]

Dear @waclawek.jan 

I just tried to setup RTC time and msec only one-time after initialization (after first SNTP packet received) and then I only calculate differences (so without calling SET RTC time and HAL_RTCEx_SetSynchroShift )

I am attaching log of timestamps, offsets, etc... from both LSE and HSE, it is abou 15 seconds periodic

In LSE if I disable periodic synchronization, you can see cumulative difference (last column), and here if I turn periodic sync + shift it works ok.

But for HSE version, it look like that values are in waves, or saw... hard to say

Radim

[waclawek.jan]

Are you sure you are running from a crystal oscillator in the HSE case?

What hardware is this, exactly? What is the HSE arrangement?

JW

[ravo]

I suppose that it is running from 25 MHz :) I verified the HSE clock by scope using MCO output and is working fine.

I am using NUCLEO H755 board https://www.st.com/en/evaluation-tools/nucleo-h755zi-q.html

I solder xtal, capacitors and change SBxx resistors to adapt HSE instead of default clock 8MHz - STLK_MCO from STLINK. All periferials working normally, and ALARM on RTC produce 1sec interrupts. I am attaching both IOC files, and screenshot for quick verify

Radim

 

 

[waclawek.jan]

All that looks and sounds well, and I have no further ideas how to explain your observations, sorry.

JW

[ravo]

Dear @waclawek.jan 

Thanks for your comments. Do you think that this is not related to fact, that I don't have PREDIV_S non-zero multiple of 256 as noted in 49.3.16 Calibration clock output in TRM document:

"When COSEL is set and “PREDIV_S+1” is a non-zero multiple of 256 (i.e: PREDIV_S[7:0] =
0xFF), the RTC_CALIB frequency is fRTCCLK/(256 * (PREDIV_A+1)). This corresponds to a
calibration output at 1 Hz for prescaler default values (PREDIV_A = Ox7F, PREDIV_S =
0xFF), with an RTCCLK frequency at 32.768 kHz."

---

---

But I have here 30 pulses in 1 seconds with period * 32 ms + (at end one which is 16 ms positive pulse + 24 ms pause ) which correspond to TRM.

But I don't know if this could also affect SHIFTR. What do you think ?

Regards Radim

[waclawek.jan]

At this point, I'm confused what are you actually doing.

I thought you are reading out time including SSR to compare to SNTP timestamps; but now you brought out RTC_CALIB output. So which one is it?

The calibration output is probably an extra issue in itself.

JW

[ravo]

Please apologise me, maybe I'm mixing two things together which are not related. I just remember one my older issue with calibration output, when I start playing with RTC clock on STM32. When in MX Cube select calibration output 1Hz and then observe that there is no 1Hz. But It depends on correct value of async and sync prescallers.  as noted in TRM manual. But now I don't play with calibration...

So now I am doing only RTC time setting and syncing with SNTP protocol. I am using middleware LWIP + SNTP addon without FreeRTOS as standalone.

Simply periodically I send and receive sntp packet. Here is "simplified pseudo code" I get 4 timestamps:

T1,T2,T3, T4

do some calculation and converting them to UNIX time in usec

request_offset = T2 - T1; // client->server

response_offset = T4 - T3; // server->client

delta = (T4 - T1) - (T3- T2);

theta = ((T2 - T1) + (T3 - T4)) / 2;

T4_new = T4 += theta; // new T4 timestamps which I would like write to RTC with msec precision.

 

I setup RTC time & date from T4_new timestamp

{

SNTP_TimestampToDate(timestamp, &date);

SNTP_TimestampToTime(timestamp, &time);

HAL_RTC_SetDate(&hrtc, &date, RTC_FORMAT_BIN);

HAL_RTC_SetTime(&hrtc, &time, RTC_FORMAT_BIN);

}

 

And with remaining msec

RTC_msec = (remaining miliseconds in last second in T4_new )

subsecond_shift = hrtc.Init.SynchPrediv - RTC_msec * ( hrtc.Init.SynchPrediv + 1) / 1000;

HAL_RTCEx_SetSynchroShift(&hrtc, RTC_SHIFTADD1S_RESET, subsecond_shift );

 

 

and if I have RTC clocked from LSE it is working good with about 3-5 msec noise

But with HSE I have these issues.

[waclawek.jan]

OK I see. And, just to be sure, the HSE_25MHz.txt  file you've posted above are results taken *without* the feedback/correction, i.e. the time read out from RTC is only compared to NTP time, RTC is not set from NTP time (except for the first time), correct?

How do you read out the current time from RTC and convert it to milliseconds, exactly? What are the bus clocks frequencies in relationship to RTC clock frequency?

Could you try to use a higher divider (e.g. 50) to make sure the RTC clock is below 1MHz?

JW

 

[ravo]

Thanks for theese suggestions,

>>> RTC is not set from NTP time (except for the first time), correct?

Yeas exactly I do this way... but logs look quite different that for LSE (there was cumulative msec_diff)

So I tried to change 25 -> 50 divider PeriphClkInitStruct.RTCClockSelection = RCC_RTCCLKSOURCE_HSE_DIV50;

So now RTC clock input should be lowered to 500 kHz and with ASYNC = 49 and SYNC = 9999 prescallers I still get msec_diff 156; 598; 22; 472; 919; 371; 816; 730; 643; ... so it did not still helped:

Update: For comparsion when RTC is working from LSE with same prerequisites (only one time set RTC without SHIFTR correction) so first diff is 817msec. And in this option it works as expected. 

But I must have working HSE :( So I will focus now why the msec_diff does not contain only increasing values. There must be something wrong there.

Regards

Radim

[waclawek.jan]

How do you read out the current time from RTC and convert it to milliseconds, exactly?

What are the bus clocks frequencies in relationship to RTC clock frequency?

JW