Re: Hardware Abstraction



Rene Tschaggelar wrote:

I am looking for a concept for abstracting of a hardware. It is desired that the concept should be convenient, clear, consistent, logical and pretty universal.

[...]

Also, it would be good to minimize the amount of cryptic system functions, initializations and dependencies.


The initialization usually is only a few register
access each.

And it can take weeks of digging through the manuals, trials and errors to do the initialization properly.

There is another aspect: when a new guy gets involved into the project, it takes him a month of hard work just to understand the dependencies and know what is already available.


Depending on the families, there are
limitations that cannot be overcome. Especially
since some families were partially made to have
a certain feature enhanced.
Eg the dsPIC2023, with a PWM that operates on a
PLLed 480MHz clock, but only on 5V, at 3.3V, the
PLL is lower, 320MHz. You want to cover this with
a standard PWM ?

Why not. For example, I can describe this feature as a class derived from the basic PWM class.


I came across such libraries. As soom as you need
a trivial addition, such as power save, part of them
becomes useless.

That's why the concept should allow for the flexible expansion.


IMO, a HAL is a bad idea in many cases, especially
on embedded hardware. How to dump performance on
zero advantage.


Reinventing a wheel each and every time when starting a new project is not a good idea either.


Read the manual once, understand how it works and
then copy/paste from project to project.

This is how it is done now, and I can feel more and more that this is not the right way.


Vladimir Vassilevsky

DSP and Mixed Signal Design Consultant

http://www.abvolt.com

.

Quantcast