time facility and runtime dependencies for code in the "components" dirs about ada_drivers_library HOT 4 OPEN

I agree that the current scheme is not great and we will also need the same kind of timing features for the services and even MCU layers.

My suggestion: make HAL.Time have concrete delay routines, with the selection of the body of the package controlled by the runtime selection, something like what we do now for the last chance handlers

How would this work for ZFP? Time handling will be different from a MCU to the other, maybe from one project to the other?

from ada_drivers_library.

from ada_drivers_library.

Perhaps the work I have done can help in how to provide delays on ZFP, including interrupt services. I have made facilities like clock configuration, interrupt service and real-time for a ZFP run-time for the STM32F334 CPU. Take a look at https://github.com/JCGobbi/Nucleo-STM32F334R8_ZFP.
I understand that each CPU family have a common NVIC and Sys-Tick hardware (like STM32 CortexM4 MCU), so each family would have a common time and interrupt interface for ZFP run-time. And in the project, that time and interrupt facilities would be selected by choosing the run-time, as has been suggested.

from ada_drivers_library.

Even if NVIC and Sys-Tick are available on most ARM micro-controllers (but not all), we want to support more than just ARM in this project. For instance this would not be applicable to RISC-V.

from ada_drivers_library.