| Table of Contents | ||
|---|---|---|
|
...
| Show advanced configuration | When selected, the user can configure advanced features: | |
|---|---|---|
| Time step factor | Denotes a multiplier for the board's speed in relation to the model's timestep. | |
| Enable FPGA register logger | For advanced debugging purposes, the driver will start a tool that will log all the FPGA register accesses during the initialization and the reset of the model. The logs will be saved in files named with the prefix "register_trace*". Those files are retrieved on the host PC after the reset of the model. | |
| Automatic bitstream reprogramming | If selected, bitstream programming is triggered automatically at the model load. The bitstreams should be placed at the model path and must have the name given in the configuration file used. If the bitstream currently programmed in the board is found to be the same as the one about to be programmed, then the bitstream is reloaded into the FPGA. The field is not available if the bitstream file is not Found. | |
| Bitstream file name | A static field showing the bitstream found based on the selected bitstream configuration file. | |
| Force | This option flashes the board even if it is already programmed with the same bitstream. | |
| Disable strict hardware mismatch validation | If selected, the use of multiple I/O card types based on general compatibility rules is activated instead of exact hardware ID values. | |
| Enable FPGA Scope | If selected, the FPGA Scope will be available when the model is executed. The option is visible only if the feature is available in the selected bitstream configuration file. | |
| Enable virtual mode | In virtual mode, the model can be executed even if this I/O interface is not compatible with the hardware configuration of the system. The connections between the model and the I/O interface will be done during the initialization, but the I/O interface will not do anything. The virtual mode can be used to troubleshoot problems on a system without having the required hardware, or to prepare a model with different I/O interfaces even if the final hardware platform is not available. | |
...
For more information regarding the detailed configuration of the signals, refer to the corresponding I/O type documentation.
...
| Anchor | ||||
|---|---|---|---|---|
|
Remote Board Configuration
Adding remote systems to the configuration is done by clicking the Insert button in the Remote Board Configuration list.
...
| Common elements | Action | Explanation | |
|---|---|---|---|
Slot configuration | Description | reset | The value of the Description field will be reset to the value in the new bitstream configuration file. |
| Functionality | reset | The Functionality field will be reset to the value in the new bitstream configuration file. | |
| IO card type | reset | The IO card type field will be reset to the value in the new bitstream configuration file. | |
| Analog Inputs | keep | The Analog Inputs channel group configuration (refer to Analog In) is applied to the new configuration. | |
| Analog Outputs | keep | The Analog Outputs channel group configuration (refer to Analog Out) is applied to the new configuration. | |
| Digital Inputs | keep | The Digital Inputs channel group configuration (refer to Digital In) is applied to the new configuration. | |
| Digital Output | keep | The Digital Outputs channel group configuration (refer to Digital Out) is applied to the new configuration. | |
Digital In channel group Threshold low value | keep or reset | If a slot contains a card with support for configurable thresholds (refer to section General Compatibility Rules for Multiple I/O Card Types), the Threshold low value from the old configuration is kept or reset according to the user preferences. | |
Digital In channel group Threshold high value | keep or reset | If a slot contains a card with support for configurable thresholds (refer to section General Compatibility Rules for Multiple I/O Card Types), the Threshold high value from the old configuration is kept or reset according to the user preferences. | |
Bidirectional channel group Direction | keep or reset | If a slot contains a card supporting configurable direction (refer to section General Compatibility Rules for Multiple I/O Card Types), the Direction is kept or reset according to the user preferences. | |
Raw data configuration | If both the old and the new bitstream configuration files define the same raw data from board ports, the configuration done (refer to section Data from Board on these ports is kept. For all common ports, the maximum DWORD count is the lower value among the maximums defined in the two files. | ||
| Raw data to board ports | keep | If both the old and the new bitstream configuration files define the same raw data to board ports, the configuration done (refer to section Data to Board) on these ports is kept. For all common ports, the maximum DWORD count is the lower value among the maximums defined in the two files. | |
| Raw load from board ports | keep | If both the old and the new bitstream configuration files define the same raw load from board ports, the configuration done (refer to section Load from Board) on these ports is kept. For all common ports, the maximum DWORD count is the lower value among the maximums defined in the two files. | |
| Raw load to board ports | keep | If both the old and the new bitstream configuration files define the same raw load to board ports, the configuration done (refer to section Load to Board) on these ports is kept. For all common ports, the maximum DWORD count is the lower value among the maximums defined in the two files. | |
| Remote boards configuration | keep | If the MuSE feature is available in both old and new bitstreams, the remote boards configuration (refer to section Remote Board Configuration) will be kept when loading the new bitstream configuration file. | |
...