Driver vs HAL

RE: Driver vs HAL

haakonsh — Sat, 03 Oct 2020 09:27:13 GMT

Yes, you're correct.

I suggest you study the RTC driver and RTC HAL API documentation and their code implementation, and compare the two abstraction layers. You should also study the RTC — Real-time counter chapter of the Product specification, and take particular note of the Registers description, it will tell you exactly what each bit in a given register does. If you know what each register does, you will understand how the HAL interfaces with the underlying hardware. As many driver functions results in calls to the HAL api, you'll be able to understand what the driver is actually doing.
Once you've understood the connection between the driver, HAL, product specification, and register description of the RTC you will be able to debug any HW peripheral in the SDK much more effectively.

I believe this abstraction model extends to a great number of embedded systems.

RE: Driver vs HAL

ashokraj — Fri, 02 Oct 2020 04:50:33 GMT

so you mean to say the following hierarchy

1.Driver

2.HAL

3.Hardware ?

Is this how it is existing in nrf52 ?

RE: Driver vs HAL

haakonsh — Thu, 01 Oct 2020 15:15:13 GMT

The Hardware Abstraction Layer ensures safe register access to a peripheral, but is often limited in features. A driver sits atop the HAL and expand on its feature set.

Whether you want to use the HAL or driver depends on your specific use-case, many drivers ensures reliable operation of the peripherals that might otherwise by tricky to do by writing a driver from scratch.

My suggestion is to re-design an existing driver to fit your needs, if it does not do so already.