Image Processing Reference
In-Depth Information
handed to the
Det
allow for tracing source and kind of error, namely, the module and the function
in which error has been detected and the type of the error. he functionality behind the API of the
Det
is not specified in AUTOSAR. Possible functionalities could be the setting of debugger break-
points within the error reporting API, the counting of the number of reported errors, the logging of
Det
calls together with the passed parameters to a RAM buffer for later analysis, and the sending of
reported errors via some communication interface (e.g.,
CanIf
) to external logger devices.
General purpose timer
(
Gpt
)
driver
: The general purpose timer (GPT) driver module provides ser-
vices for starting and stopping a functional timer instance within the hardware general-purpose timer
module and thus “provides exact and short-term timings” for use in the
Os
or within other system
software modules where an
Os
alarm service causes too much overhead. Individual timeout periods
(single shot mode) as well as repeating timeout periods (continuous mode) can be generated via the
Gpt
module.heusercanconigurewhetheranotiicationshallbeinvokedwhentherequestedtime-
out period has expired. hese notifications can be enabled and disabled at runtime. Both the relative
time elapsed since the last notification occurred and the time remaining until the next notification
will occur can be queried via API functions of the
Gpt
module.
Microcontroller unit
(
Mcu
)
driver
: he MCU Driver module provides services for “basic microcon-
troller initialization, power-down functionality, microcontroller reset” and microcontroller-specific
functions required from other system software modules. The initialization services of the MCU
Driver module allow a flexible and application-related MCU initialization in addition to the start-up
code.
∗
The services of the MCU Driver include the initialization of the MCU's clock, initializa-
tion of the MCU's phase-locked loop, the initialization of clock prescalers, and the configuration
of the MCU's clock distribution. Furthermore, the MCU Driver takes care of the initialization of
the MCU's RAM sections, facilitates the activation of the MCU's reduced power modes (i.e., putting
the MCU into a low-power mode), and provides a service for enforcing a reset of the MCU and a
service for obtaining the reset reason from the MCU hardware.
18.8 JasPar
Founded September by Toyota, Nissan, Honda, and Toyotsu Electronics, the nonprofit organi-
zation JasPar [] was created to develop a unified architecture for vehicle networking and software
development tailored to the requirements of Japanese customers.
JasPar's goals are focused on the evaluation, the exploitation, and the implementation of exist-
ing standards in actual projects. The organization seeks to serve as the Japanese point of contact
for automotive-standards organizations in other regions. Based on the results of the AUTOSAR and
FlexRay consortium, JasPar was constructed as complementary organization to unite standardiza-
tion and product attempts in Japan (see Figure .) to maintain the possibility of tailored product
generation for the Japanese OEM and finally the end customer.
Within JasPar, working groups are focusing on developing design tools and prototypes for auto-
motive networks, creating standards for in-vehicle cable routing, writing guidelines for wire-harness
design, developing recommended circuits for controllers/transceivers, and planning communica-
tion software. Moreover, JasPar is feeding suggestions back to related consortia for new standard
requirements.
An example given in the evaluation of existing standards is the standardization of the business
process in using FlexRay parameter settings. This standardization shall reduce the risk of failures
∗
∗The start-up code itself is not within the scope of AUTOSAR.
