S32K144 Driver vs PAL?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

S32K144 Driver vs PAL?

4,908件の閲覧回数
alwin_lutz
Contributor II

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,

Al

タグ(3)
0 件の賞賛
返信
2 返答(返信)

4,564件の閲覧回数
raresvasile
NXP Employee
NXP Employee

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

0 件の賞賛
返信

4,564件の閲覧回数
alwin_lutz
Contributor II

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. 

Al

0 件の賞賛
返信