Explain the Hardware Abstraction Layer followed by MCUXpresso IDE

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Explain the Hardware Abstraction Layer followed by MCUXpresso IDE

1,028 Views
GanesanGuru
Contributor IV

Hi fellas,

I'm currently working on Energy meter application based on KM3x series and the findings are listed as follows:

  1. MKM34Z256VLx7 MCU has a Bare Metal Software Drivers v R4.1.6 - Refer this
  2. SDK_2_14_0_MKM34Z256xxx7 has funcitons like BOARD_InitPins - Refer this
  3. Metering Algorithms - AN4555/65 has funtions like METERLIB1PH_ProcSamples - Refer this

SDK uses Baremetal drivers & Metering algo/any middleware. IDE uses SDK for easier app. development.

So, whether my understanding is correct? How to double verify those. What about CMSIS part then?

From my previous experiences on STM32F4 series --- ARM Registers HAL --> CMSIS HAL --> STM32F4 HAL. Similarly, can somewhone point out for NXP too?!

Labels (1)
0 Kudos
Reply
1 Reply

986 Views
RaRo
NXP TechSupport
NXP TechSupport

Hello @GanesanGuru,

Just for double check, are you asking for a driver recommendation for metering applications? If so, we recommend you check out our examples and application notes like the one you mentioned.

In the SDK that you have downloaded, inside docs -> metering there are three application notes that could be useful for metering applications. In addition, you could check the Arm® Cortex®-M0+|Kinetis® KM3x 50-75 MHz 32-bit MCUs | NXP Semiconductors Documentation -> Application Note, which includes their SW as you mentioned in the first point. Usually, the ANs are made with the standard drivers of the SDK.

The CMSIS drivers for the KMx series are for managing SPI, I2C and UART. You could check more about them in the cmsis_ examples and docs -> MCUXpresso SDK API Reference Manual_MKM3x in the SDK.

Best regards, Raul.

0 Kudos
Reply