|
|
|
| R2012a Documentation → xPC Target | |
Learn more about xPC Target |
|
| Contents | Index |
This table summarizes what's new in Version 5.1 (R2011b):
New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
Yes | Yes | Bug
Reports |
.
In Simulink External Mode, xPC Target supports uploading non-bus signal information from models referenced inside a top model. Uploading information from buses and virtual signals inside a reference model generates a warning.
You can create an xPC Target "bootdisk" using CompactFlash and removable hard drives as well as floppy disk and CD-ROM. This disk boots the xPC Target kernel without requiring DOS, as with DOSLoader.
In addition to supporting preemptive rate monotonic scheduling for single-core processors, the xPC Target software supports distributing a target application built from a Simulink model as concurrent tasks across processors in a multicore machine.
The xPC Target kernel supports distributing a target execution in multicore mode using the Intel® Core™ i5 and Intel Core i7 processors.
As part of its support for multiple processors, the xPC Target software uses the Advanced Configuration and Power Interface (ACPI) to discover ACPI-compliant hardware in the target computer and creates a MultiProcessor Floating Pointer Structure (MPFPS) representing it. If the hardware is not all ACPI compliant, you can use the following xPC Target environment property to access the legacy MPFPS in the computer BIOS:
setxpcenv('LegacyMultiCoreConfig', 'on')Note To display the allowed values of xPC Target environment properties, type setxpcenv with no arguments. To display their current values, type getxpcenv with no arguments. |
The xPC Target kernel supports data storage and transfer using 1 LUN (logical unit) USB drives, 2 LUN USB drives, and 4–LUN card readers.
The xPC Target kernel allow the host and target computers to communicate using USB Ethernet adapters. In xPC Target Explorer, do the following:
Set TCP/IP target bus to USB.
Set TCP/IP target driver to USBAX772, USBAX172, or Auto.
From the MATLAB command line, do the following:
setxpcenv('TcpIpTargetBusType','USB')
setxpcenv(‘TcpIpTargetDriver','USBAX772'), or
setxpcenv(‘TcpIpTargetDriver','USBAX172'), or
setxpcenv(‘TcpIpTargetDriver','Auto')
If you set the target driver to Auto, the software defaults the target driver to USBAX772, the driver most commonly used.
Note To display the allowed values of xPC Target environment properties, type setxpcenv with no arguments. To display their current values, type getxpcenv with no arguments. |
The xPC Target software supports multiple triggering modes and extracting a region of interest using the NEON BitFlow Image Input block. See Acquiring Images from Camera Link Cameras.
The From File IsValid port outputs 1 if the file read succeeds and 0 if it fails. Select the Show IsValid port check box on the From File Source Block Parameters dialog to make it visible in the model.
The xPC Target kernel supports the CAN protocol with remote frame transmission.
xPC Target supports the default I/O pin map for the 37–pin variant of the NI 6221 M-Series board, as shown in the M-Series User Manual from National Instruments®.
The xPC Target driver supports direct frequency measurement (pulse counting) using the capabilities of the NI PCI-6601 and PCI-6602 boards.
The software supports the following additional Speedgoat boards and functionality:
Speedgoat IO302 board
A/D input port on Speedgoat IO325 board. HDL Workflow Advisor will automatically add the A/D input port calibration block to the model.
Differential ports on Speedgoat IO303/IO325 board.
Digital Clock Manager (DCM) configuration on Speedgoat FPGA boards.
The xPC Target computer can synchronize target application execution to interrupts produced by all supported FPGA boards.
Compatibility Considerations. The Watcom 1.8 compiler cannot compile an IO325 model. Use a Microsoft® compiler instead.
You can change the stack size of the real-time threads by setting a TLC option in the Configuration Parameters dialog, Code Generation node, section Build Process. For example, to set the stack size to 256 kBytes, type the following in the TLC option box:
-axPCModelStackSizeKB=256
The xPC Target compiler support has changed as follows:
Added Intel Visual Fortran Composer XE 2011 on win32 and win64.
Added Windows SDK 7.1 on win32 and win64.
Removed Microsoft Visual Studio 2005 SP1 (8.0) on win32 and win64.
See Supported and Compatible Compilers for a complete list of supported compilers.
This release contains the following new demos:
Concurrent Execution on xPC Target — This demo demonstrates how to realize concurrent execution of a model on xPC Target, illustrating the execution of each model thread using the xPC Target profiling tool.
 | Version 5.2 (R2012a) xPC Target | Version 5.0 (R2011a) xPC Target |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
