This is a cache of https://www.96boards.org/blog/neonkey-aosp/. It is a snapshot of the page at 2024-10-31T03:46:05.895+0000.
Implementing Neonkey Sensor Mezzanine on AOSP - 96Boards

Implementing Neonkey Sensor Mezzanine on AOSP

Sahaj Sarup
|

Introduction

The Neonkey packs a Cortex-M4 chip, 512 Kb flash, 128 Kb SRAM, and a hub of the following sensors: Temperature, Humidity, Pressure, Ambient Light Sensor, Proximity, Geomagnetic, Accelerator and Gyroscope.

Kernel source and ContextHub board support is available in AOSP to help developers create and debug new sensors, make new HAL and kernel changes, etc. with fewer OEM encumbrances.

The Nanaohub, Cantexthub and Sensor HAL

What is a HAL?

A HAL(Hardware Abstraction Layer) defines a standard interface for hardware vendors to implement, which enables Android to be agnostic about lower-level driver implementations. Using a HAL allows you to implement functionality without affecting or modifying the higher level system. HAL implementations are packaged into modules and loaded by the Android system at the appropriate time.

HALs Required by the Neonkey Mezzanine:

  • Contexthub HAL which also impliments the Nanohub HAL: This includes the hardware specific code for devices like Neonkey.

  • Sensor HAL: Android sensors give applications access to a mobile device’s underlying physical sensors. They are data-providing virtual devices defined by sensors.h, the sensor Hardware Abstraction Layer (HAL).

HAL Implementation: You can take a look at the implementation following this commit on AOSP.

… and finally

Guide to build AOSP with support for Neonkey

comments powered by Disqus