NXP Semiconductors
AH1721
SJA1105SMBEVM UM
AH1721
All information provided in this document is subject to legal disclaimers.
© NXP Semiconductors N.V. 2018. All rights reserved.
User Manual
Rev. 1.00
— 16 July 2018
25 of 35
addresses, usage of GPIOs, device handles, etc. This data is used by other
application components to call the right device driver instances.
o
SJA1105SMBEVM utilities: sja1105smbevm_console.c contains some very
simple functions for implementing a serial console. This is useful for
debugging, and very simple visualization. It makes use of the UART
configuration via ProcessorExpert (baud rate, etc.), and the UART2USB
interface and the USB connector.
o
Callback functions for ENET and CAN: ProcessorExpert allows for some
drivers to optionally configure callback functions in the application layer in
specific situations, for example when errors occur or when data has been
received or transmitted. Callback functions are called in the context of a
device specific service task or from the interrupt context. Therefore, they
should not perform time or stack consuming operations.
In the example project, the ENET callback functions handle receiving
ethernet packets. The PHY callbacks are for handling link detection changes
and for auto-negotiation result processing.
o
ENET and CAN application. These SW modules contain code to initialize the
proper device drivers, which in turn configure the devices, and to start tasks
to maintain regular communication. The initialization and tasks are only
started for specific rotary dial settings, see Table 7.
o
The general application module main.c does general initialization, and
hardware plausibility tests, and starts the other application modules,
depending on rotary dial settings. Periodic blinking the alive LED is also a
task done in the main application module.
6.2 Code organization
Fig 16 shows the source files of the example project as they are presented in S32DS: