Microsemi SmartFusion2 MSS Manuel utilisateur
SmartFusion2 MSS
CAN Configuration
SmartFusion2 MSS CAN Configuration
2
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1 Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Peripheral Signals Assignment Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Connectivity Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4 Resource Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Error Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Warning Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Information Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 Port Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
A Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Customer Technical Support Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Contacting the Customer Technical Support Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ITAR Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3
Introduction
The SmartFusion2 Microcontroller Subsystem (MSS) provides one CAN hard peripheral (APB_1 sub
bus).
On the MSS Canvas, you must enable (default) or disable the CAN instance based on whether it is being
used in your current application. When disabled, the CAN instance is held in reset (lowest power state).
By default, when enabled, the CAN ports are configured to connect to the device Multi Standard I/Os
(MSIOs). Note that MSIOs allocated to the CAN instance are shared with other MSS peripherals. These
shared I/Os are available to connect to MSS GPIOs and other peripherals when the CAN instance is
disabled or if the CAN instance ports are connected to the FPGA fabric.
The functional behavior of the CAN instance must be defined at the application level using the
SmartFusion2 MSS CAN Driver provided by Microsemi.
In this document, we describe how you can configure the MSS CAN instance and define how the
peripheral signals are connected.
For more details about the MSS CAN hard peripheral, please refer to the SmartFusion2 User Guide.
4
1 – Configuration Options
There are no hardware configuration options for the CAN peripheral.
Note: If the CAN instance is enabled, M3_CLK must be a multiple of 8MHz. This restriction will be
enforced in the MSS CCC Configurator.
5
2 – Peripheral Signals Assignment Table
The SmartFusion2 architecture provides a very flexible schema for connecting peripherals signals to
either MSIOs or the FPGA fabric. Use the signal assignment configuration table to define what your
peripheral is connected to in your application. This assignment table has the following columns
(Figure 2-1):
MSIO - Identifies the peripheral signal name configured in a given row.
Main Connection - Use the drop-down list to select whether the signal is connected to an MSIO or the
FPGA fabric.
Direction - Indicates if the signal direction is IN, OUT or INOUT.
Package Pin - Shows the package pin associated with the MSIO when the signal is connected to an
MSIO.
Extra Connections - Use the Advanced Options check-box to view the extra connection options:
• Check the Fabric option to observe into the FPGA fabric a signal that is connected to an MSIO.
• Check the GPIO option to observe an input direction signal - from either the FPGA fabric or an
MSIO - using an MSS GPIO.
Figure 2-1 • CAN Peripheral Signals Assignment Table
6
3 – Connectivity Preview
The Connectivity Preview panel in the MSS CAN Configurator dialog shows a graphical view of the
current connections for the highlighted signal row (Figure 3-1).
Figure 3-1 • CAN Connectivity Preview
7
4 – Resource Conflicts
Because MSS peripherals (MMUART, I2C, SPI, CAN, GPIO, USB, Ethernet MAC) share MSIO and
FPGA fabric access resources, the configuration of any of these peripherals may result in a resource
conflict when you configure an instance of the current peripheral. Peripheral configurators provide clear
indicators when such a conflict arises.
Resources used by a previously configured peripheral result in three types of feedback in the current
peripheral configurator:
•Information - If a resource used by another peripheral does not conflict with the current
configuration, an information icon appears in the connectivity preview panel, on that resource. A
tooltip on the icon provides details about which peripheral uses that resource.
•Warning/Error - If a resource used by another peripheral conflicts with the current configuration,
a warning or error icon appears in the connectivity preview panel, on that resource. A tooltip on
the icon provides details about which peripheral uses that resource.
When errors are displayed you will not be able to commit the current configuration. You can either
resolve the conflict by using a different configuration or cancel the current configuration using the Cancel
button.
When warnings are displayed (and there are no errors), you can commit the current configuration.
However, you cannot generate the overall MSS; you will see generation errors in the Libero SoC log
window. You must resolve the conflict that you created when you committed the configuration by re-
configuring either of the peripherals causing the conflict.
The peripheral configurators implement the following rules to determine if a conflict should be reported as
an error or a warning.
1. If the peripheral being configured is the GPIO peripheral then all conflicts are errors.
2. If the peripheral being configured is not the GPIO peripheral then all conflicts are errors unless the
conflict is with a GPIO resource in which case conflicts will be treated as warnings.
8
Error Example
The USB peripheral is used and uses the device PAD bounded to package pin V24. Configuring the CAN
peripheral such that the RXBUS port is connected to an MSIO results in an error.
Figure 4-1 shows the error icon displayed in the Connectivity Assignment table for the RXBUS port.
Figure 4-2 shows the error icon displayed in the Preview panel on the PAD resource for the RXBUS port.
Figure 4-1 • Error Displayed in the Connectivity Assignment Table
Figure 4-2 • Error in the Preview Panel
9
Warning Example
The GPIO peripheral is used and uses the device PAD bounded to package pin V24 (GPIO_3).
Configuring the CAN peripheral such that the RXBUS port is connected to an MSIO results in a warning.
Figure 4-3 shows the warning icon displayed in the Connectivity Assignment table for the RXBUS port.
Figure 4-4 shows the warning icon displayed in the preview panel on the PAD resource for the RXBUS
port. Note that in this example, there is a second conflict with a GPIO because of the extra connection to
GPIO_3.
Figure 4-3 • Warning Displayed in the Connectivity Assignment Table
Figure 4-4 • Warning in the Preview Panel
10
Information Example
The USB peripheral is used and uses the device PAD bounded to package pin V24. Configuring the CAN
peripheral such that the RXBUS port is connected to the FPGA fabric does not result in a conflict.
However, to indicate that he PAD associated with the RXBUS port (but not used in this case), the
Information icon is displayed in the Preview panel (Figure 4-5). A tooltip associated with the icon
provides a description of how the resource is used (USB in this case).
Figure 4-5 • Information Displayed in the Preview Panel
Autres manuels pour SmartFusion2 MSS
18
Table des matières
Autres manuels Microsemi Outils électriques
Microsemi
Microsemi SA.22c Manuel utilisateur
Microsemi
Microsemi SmartFusion2 MSS Instructions d'installation et d'utilisation
Microsemi
Microsemi IGLOO2 FPGA DSP FIR Filter Instructions d'installation et d'utilisation
Microsemi
Microsemi SmartFusion2 MSS Manuel utilisateur
Microsemi
Microsemi SmartFusion2 MSS Manuel utilisateur
Microsemi
Microsemi SmartFusion2 MSS Manuel utilisateur
