Question about MCAL LLCE Driver Timeout Setting

[zyz]

In the EB configuration, the default timeout value for LLCE is set to 1 second. We intend to reduce it (e.g., to 10ms) to avoid prolonged blocking in abnormal conditions, which may impact business responsiveness.

However, upon reviewing the LLCE driver code, we noticed this parameter is used in multiple places, some involving interactions with the S32G's LLCE core. Thus, we are uncertain about the minimum safe threshold to avoid potential errors.

Could you please clarify:

1. What is the minimum recommended timeout value to ensure stability?

2. Are there any constraints or best practices to follow when adjusting this parameter to prevent adverse effects on the LLCE core?

[chenyin_h]

Hello, @zyz 

Thanks for your reply.

I understand your point, but by checking it internally, it is confirmed that these timeout values in MCAL depend on customer application request, usually we do not provide any recommand value. I apologize.

From the experience, these values depends on the customer application requirements/protocol/spec/standard(like AUTOSAR,etc.), it varies for different use cases.

BR

Chenyin

[zyz]

Hi，chenyin_h，

I understand what you mean, but in scenarios like the one below, I don't see how it relates to the customer's application requirements.

[chenyin_h]

Hello, @zyz 

Thanks for your post.

There are max/min values existed, which are shown below, but no recommended values from RTD's perspective, the timeout value itself depend on the customer application request.

BR

Chenyin

[zyz]

I understand this parameter should be configured per user requirements, but we can only evaluate it based on our specific needs. Since multiple driver interactions with the LLCE core depend on this parameter, we cannot assess the appropriateness of the timeout values for these scenarios. We're concerned that setting it too small may cause frequent LLCE response timeouts.