From 8ec724200a5d30dc55a7f30a363255c228e2e75d Mon Sep 17 00:00:00 2001 From: Michal Horn Date: Mon, 17 Aug 2015 17:43:50 +0200 Subject: [PATCH 1/1] doc: remove section about HAL --- doc/rpp_simulink.tex | 22 ---------------------- 1 file changed, 22 deletions(-) diff --git a/doc/rpp_simulink.tex b/doc/rpp_simulink.tex index 22bc0bf..565f6e7 100644 --- a/doc/rpp_simulink.tex +++ b/doc/rpp_simulink.tex @@ -358,28 +358,6 @@ folder. Large part of this layer was generated by the HalCoGen tool (see Section~\ref{sec-halcogen}). -\subsection{HAL abstraction layer} -\label{sec-hal-abstraction-layer} -Hardware Abstraction Layer (HAL) provides an abstraction over the real -hardware. For example imagine an IO port with 8 pins. First four pins -are connected directly to the GPIO pins on the MCU, another four pins -are connected to an external integrated circuit, communicating with -the MCU via SPI. This layer allows to control the IO pins -independently of how that are connected to the MCU, providing a single -unified API. - -Note that this functionality is not needed in the current version for -\tgtBoardName, because all IOs are controlled directly by GPIO pins. - -As a result, the higher layers do not have to know anything about the -wiring of the peripherals, they can just call read, write or configure -function with a pin name as a parameter and the HAL handles all the -details. - -The source files can be found in -\texttt{$\langle$rpp\_lib$\rangle$/rpp/src/hal} and the header files can -be found in \texttt{$\langle$rpp\_lib$\rangle$/rpp/include/hal} folder. - \subsection{Drivers layer} \label{sec-drivers-layer} The Drivers layer contains code for controlling the RPP peripherals. -- 2.39.2