Table of Contents
Advertisement
•
freemaster.h - The main driver header file. This is the only file which needs to be included by the
application code.
•
freemaster_cfg.h - The minimal driver configuration file which further includes the appconfig.h
file and enables the driver to be configured in Graphical Configuration Tool.
•
freemaster_cfg.h.template - An example of the full driver configuration file. Such a file needs to
be used (and renamed to freemaster_cfg.h) in case the FreeMASTER driver is extracted and used
outside the DSP56F800E_Quick_Start environment.
•
freemaster_private.h - Internal header file used by all driver source code. The compile-time
verification of the configuration macros is done in this file. Also the default values of undefined
configuration values are defined here.
•
freemaster_56F8xxx.c - 56F8xxx hardware-specific functions are implemented in this file.
•
freemaster_56F8xxx.h - 56F8xxx hardware-specific macros and inline functions are in this file.
•
freemaster_protocol.c - Implements the FreeMASTER protocol decoder, which is independent on
the communication interface used.
•
freemaster_protocol.h - Internal header file which contains the FreeMASTER protocol constants.
•
freemaster_serial.c - Physical SCI and JTAG interface is handled in this file. The protocol decoder
is invoked from this file when a valid FreeMASTER message is received. This file also handles the
response transmission back to the PC.
•
freemaster_appcmd.c - Implementation of the FreeMASTER Application Commands.
•
freemaster_rec.c - FreeMASTER Recorder implementation.
•
freemaster_scope.c - FreeMASTER Oscilloscope implementation.
•
freemaster_tsa.c - Target-side Addressing (TSA) implementation.
•
freemaster_tsa.h - TSA header file which is indirectly included in the user application code too.
This file defines the macros which are used to build the TSA tables in the user code.
6.3
Interrupt Handling
The FreeMASTER driver must be configured for one of the three modes of operation, differing in
the way how the peripheral interrupts are used by the driver.
Mode
Long Interrupt Mode
Short Interrupt Mode
FREESCALE SEMICONDUCTOR
Table 6-1. FreeMASTER Driver Interrupt Mode
Both the communication interface and the protocol decoder are processed in the
SCI or JTAG interrupt. The time spent in the interrupt routine depends on the what
protocol command is being handled. Such a non-deterministic behavior may require
the application interrupt levels to be balanced with care.
The communication is handled in the interrupt while the protocol is decoded and
handled only when the "poll" function is called. The time spent in the interrupt ser-
vice routine is rather short as the characters are just fetched to or from the buffer.
One additional communication buffer (receiver queue) is required to store received
characters before they are handled by the protocol state machine.
Targeting 56F8xxx Platform
Description
Interrupt Handling
6-3
Advertisement
Chapters
Table of Contents
