Hi,
In the section of STCU2 in the "S32K3xx Reference Manual, Rev. 7,05/2023", there are some precautions before self-test.
For the two items circled in the image, I couldn't find the corresponding implementation code in the "
S32K3 Safety Peripheral Drivers version 1.0.3 |
"
.
1. Are these two parts implemented in the S32K3 Safety Peripheral Drivers?
2. If they are implemented, can you please help me locate them?
Thank you very much!
Solved! Go to Solution.
Hello,
1. Are these reset sources in table 287 automatically disabled by BIST after the user runs BIST_RUN?
Yes. I expect that hardly one of those modules can request reset in RGM while its content is filled with test patterns.
2. Similarly, regarding the second highlighted area about disabling communication peripherals, do we need to manually code the shutdown of these peripherals before running BIST_RUN?
Yes, this was the common practice.
However, such routines could be now part of SPD /SAF driver (I would expect that). Since I do not know SAF in details but I do have deep knowledge on STCU.
Anyway it should be in documentation to the SAF /SPD or in some precondition BIST functions.
Best regards,
Peter
Hello,
1. Are these reset sources in table 287 automatically disabled by BIST after the user runs BIST_RUN?
Yes. I expect that hardly one of those modules can request reset in RGM while its content is filled with test patterns.
2. Similarly, regarding the second highlighted area about disabling communication peripherals, do we need to manually code the shutdown of these peripherals before running BIST_RUN?
Yes, this was the common practice.
However, such routines could be now part of SPD /SAF driver (I would expect that). Since I do not know SAF in details but I do have deep knowledge on STCU.
Anyway it should be in documentation to the SAF /SPD or in some precondition BIST functions.
Best regards,
Peter
Hello,
FCCU RST is disabled by the BIST as description express:
Second the corresponding PCTLs can be controlled by ME module. basically the note ask you to disable clocks to peripherals before test is started.
This is most probably implemented by BASE module of AUTOSAR drivers. I do not expect that this is the part of SDP driver as it is general Mode entry functionality.
For details refer to reference manual : 47.1.4 Core clock gating
For example:
Best regards,
Peter
Hello Peter,
Thank you very much for your reply. I apologize if my previous questions were not clear. I still have two questions that I haven't understood clearly:
1. Are these reset sources in table 287 automatically disabled by BIST after the user runs BIST_RUN?
2. Similarly, regarding the second highlighted area about disabling communication peripherals, do we need to manually code the shutdown of these peripherals before running BIST_RUN?
I look forward to your reply. Thank you!