Low level driver configuration

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

Low level driver configuration

804件の閲覧回数
SivaB
Contributor III

Different between CLOCK_DRV_Init  vs  Clock_Ip_InitClock

which one is bettter for non autosar applications.

0 件の賞賛
返信
3 返答(返信)

791件の閲覧回数
VaneB
NXP TechSupport
NXP TechSupport

Hi @SivaB 

Both functions set clock configurations according to a pre-defined structure.

The difference between the functions is that are from different software. CLOCK_DRV_Init is a function of the S32K1 SDK, which is development kit that provides a cost-effective, complete, and easy-to-use solution matched with stacks for connectivity, motor control, and safety libraries for the entire range of S32K1 microcontrollers. The S32SDK for S32K1 is well suited for all applications in the automotive space.

On the other side, Clock_Ip_InitClock is a function of the RTDs, which are a new and innovative drivers set supporting real-time software on AUTOSAR® and non-AUTOSAR applications targeting Arm® Cortex®-M cores and ISO 26262 compliance for all software layers.

 

B.R.

VaneB

0 件の賞賛
返信

785件の閲覧回数
SivaB
Contributor III

Hi VaneB

How to include the AMMCLIB & Freemaster  SDK on tool chain 9.2 when using RTD SW32K1_RTD_4_4_1_0_1_D2202 for non-AUTOSAR application

 

0 件の賞賛
返信

770件の閲覧回数
VaneB
NXP TechSupport
NXP TechSupport

@SivaB 

Here is a HOWTO: Working with AMMCLib SDKs.

Also if you are planning to use the S32K1 family for motor control I suggest you take a look at the S32K144 BLDC/PMSM Development Kit and the available software for it.

0 件の賞賛
返信