topic Re: S32K144 Driver vs PAL? in S32 SDK

S32K144 Driver vs PAL?

alwin_lutz — Wed, 20 Nov 2019 19:15:02 GMT

What is the difference between the S32K "ADC Driver" and the "ADC PAL" (using the S32K144). What would the criteria be to choose either?

Thanks,

Re: S32K144 Driver vs PAL?

raresvasile — Thu, 21 Nov 2019 09:20:51 GMT

Hi,

As extracted from the SDK documentation:

PAL - Peripheral Abstraction layer
- Interface abstraction for a family of peripherals (E.g. LPUART + LINFlexD_UART + eSCI + FlexIO_UART + etc.)
- Single layer per SDK
- Same generic API on multiple platforms

PD - Peripheral Drivers
- IP dedicated low-level drivers
- Designed for efficiency and IP features set coverage

When to use the Peripheral Abstraction Layer (PAL)?
- Whenever an application needs a simplified, generic interface that abstracts as much as possible the underlying silicon features.
- Whenever developing portable higher level generic code that is meant to run on different NXP platforms. This may include anything from low level console utility libraries to communication stacks like TCP/IP.

When to use Peripheral Drivers?
- Whenever developing for high efficiency (code size, execution speed, etc.) or planning to use specific peripheral features.

Best regards,

Rares

Re: S32K144 Driver vs PAL?

alwin_lutz — Thu, 21 Nov 2019 21:57:13 GMT

Hi,

thank you very much for the clarification, that makes sense. I can see now the difference. I noticed, that the PALs are enabling/using other resources (e.g. Timer Interrupts,...) that one has to be aware of in the design.