sBoot watchdog test - FDTI time and Watchdog timeout value

[Irshad2225]

Hi,

In my current application, the internal watchdog timeout is 128ms.

While performing sBoot watchdog test, sBoot is checking FDTI time shall be greater than or equal to the internal watchdog timeout. 

In the Current configurator, I cannot configure the FDTI value beyond 100ms.

How can this test be performed with an internal watchdog timeout of 128ms?

Regards,
Irshad

[alejandro_e]

Hello @Irshad2225,

Thanks for reaching out to us. Please provide the following information for better support:

• Which version of SAF are you using?
• To which 'internal watchdog' are you referring to?
• Please provide any other details that might help me understand your setup better.

Thanks

[Irshad2225]

1. SAF version: SW32G_SAF_2.0.2_QLP01_D2410
2. SWT_0
3. SWT_0 timeout is 128ms

[alejandro_e]

Hello @Irshad2225,

Thanks for the details. To configure SWT_0 with a timeout of 128ms you need to use the value 6,144,000 in its respective Timeout register, offset 0x0008, base address 0x4010_0000 [page 224, S32G3 Reference Manual, Rev. 4, 02/2024]: 

This is because the SWT module uses FIRC as the source clock, which is 48MHz [page 887, S32G3 Reference Manual, Rev. 4, 02/2024]:

Therefore Timeout register[ticks] = Clock freq[Hz] *Timeou[s]= 6,144,000.

You can check the example Swt_Ip_Example_S32G399A_M7 available in the RTD for more reference.

Let me know if you have more questions.

[Irshad2225]

Hi, 

The SWT is configured with 128ms and it's working.

My main query is about sboot SWT getting failed because it expects the FDTI time to be greater than or equal to the SWT timeout value. Hence, the test is failing due to a failed condition.

With the current SWT timeout of 128ms, I am not able to configure FDTI time beyond 100ms in the configurator.

at line 218, its getting failed. 

Regards,
Irshad

[alejandro_e]

Hello @Irshad2225,

Sorry for not understanding your request before. And you are correct, the FDTI cannot be configured above 100ms, independently of the configuration, you can see that in the sBoot documentation:

You would need to adjust your implementation to accommodate for the limits of FDTI.

I apologize for the inconviniences

[Irshad2225]

Hi,

Could you provide any justification for the range?

[alejandro_e]

Hello @Irshad2225,

Good question. I have searched in the internal documentation and I found that it has been a recurrent topic for other customer as well, I have seen some discussion of possibly removing the restriction for other components of the S32 family, however I don't know if this has been considered for the S32G chips. I will raise this topic with the internal team and see if it can be done in the S32G family.  

I will come back with an update on this topic as soon as I can,

Thanks for your patience. 

[Irshad2225]

Hi @alejandro_e,

Any Update?

[alejandro_e]

Hello @Irshad2225,

I have not receive any update yet, I will ask for one and come back when I get it.

Sorry for the delay, I hope it does not cause any inconveniences.

Best regards

[alejandro_e]

Hello @Irshad2225,

I have received feedback from the internal team, here is what they shared:

"

Please check the answer as below:

• Will the removal of the FDTI restriction be included in the S32G SAF package?

         A: It will include S32G SAF package.

• When can we expect this change to be included in a release? 

         A: S32G_SAF_2.0.3

• Is there a temporary workaround to use FDTI with a value above 100ms?

         A: The customer can modify the generated code in sBoot_Cfg.h, but this is only a temporary workaround for testing purposes and not suitable for production use.

" 

Sorry for the late solution, please let me know if you have any other question.

Thanks