Documentation for SCST for S32K14x talks exclusively about S32K144

[Matthias_LEHMANN]

Hello,
we're building an ASIL-B System using the S32K142. We've licensed the SCST to get the required diagnostic coverage for the core. Any download option on the NXP website as well as the actual licenses at the official distributors only make a difference between M0 and M4 core. However after having purchased the license and downloading the "official" library, many places in the documentation exclusively refer to the S32K144, e.g.

• the filename of the downloaded archive is SCST_M4_S32K144_RTM
• The release notes .txt file often refers to S32K144. One line mentions that S32K14x are support, but the next line says, the library was only tested with S32K14.
• the user manual ("M4_S32K144_SCST_User_Manual", Rev 1.5 / Feb 27th 2020) says in section 1.3 that only the S32K144 is a supported device.
  • as an add-on question: also in this document, three compilers are listed as "supported". Does this exclude the SCST from being used with other compilers? We were planning to use the ARM compiler V6 ,which is also safety certified.

Other documents like the Safety Manual, Test specification or safety concept (all date back to 2017) don't refer to any specific controller models.

Can you please explain the reason for this inconsistency and confirm if the downloaded SCST version is fully compatible with the S32K142, both from a technical point of view as well as from a formal / documentation / test coverage, etc. point of view.

Thank you

Matthias

[Matthias_LEHMANN]

Thanks Martin.

It would be great if the documents could be updated some time in the future to avoid this type of confusion in future.

Do you also have a statement on the question about the compiler? What's the implication of using a different compiler than one of the three mentioned in the documentation (i.e. the ARM compiler in our case)?

Best regards

Matthias

[martinkaspar-r3]

The mentioned specific compilers & versions are used for the product testing and thus we guarantee the functionality when theses compilers are used. If another compiler version is used, e.g. a newer one, typically we do not expect any issue, but still it is a customer responsibility to use. If another compiler is used (from another vendor) then mostly it will not work easily. The customers can approach the NXP sales/marketing to request a specific compiler/version support as a paid service.

[martinkaspar-r3 · Accepted solution]

The package supports all S32K14x family members because they share the same core as S32K144 which was used for testing, all the artifacts are also applicable to the family members