LabVIEW Microprocessor SDK Release Notes Version 2009

Transcription

1 LabVIEW Microprocessor SDK Release tes Version 2009 Contents Use the LabVIEW Microprocessor SDK to port LabVIEW to any 32-bit microprocessor. By using a single development tool from concept to finished product, you can ease the development process and increase end quality while reducing time to market. System Requirements and Target Recommendations...1 Host Computer Requirements...1 Target Recommendations...1 System Requirements for Example Targets...2 Installation...3 Selecting an Appropriate Example Target...3 Upgrading from Version Changes in the LabVIEW Development System...4 Upgrading Target Support...4 Instrumented Debugging Diagnostic Filename Change...5 What's New...5 VIs and Functions Support and Enhancements...5 Front Panel Controls Support and Enhancements...6 Properties and Methods Support and Enhancements...6 Application Status Window...7 Funclist Wizard...7 Interrupt Configuration Wizard...7 LabVIEW Class Support...8 Timed Loop Enhancements...8 Microprocessor SDK Documentation...8 System Requirements and Target Recommendations Host Computer Requirements The Microprocessor SDK has the following requirements: A computer with Windows Vista (32-bit version)/xp/2000 LabVIEW 2009 Full or Professional Development System NI-VISA Run-Time Engine version or later (available on the NI Device Drivers DVD) Refer to the LabVIEW Release tes, available by selecting Start»All Programs»National Instruments»LabVIEW 2009»LabVIEW Manuals and opening LV_Release_tes.pdf, for standard LabVIEW development system requirements. Target Recommendations National Instruments recommends that your target has the following: 32-bit processor architecture.

2 256 KB of application memory (in addition to the embedded operating system memory requirements). An embedded operating system so you can take advantage of parallelism and multithreading in LabVIEW. A hardware floating-point unit or floating-point emulation library to perform the math calculations in the LabVIEW Analysis Library, which is floating-point. You can improve performance by performing the math calculations in hardware instead of using software emulation. System Requirements for Example Targets The Microprocessor SDK example targets have the following requirements: Target Name Hardware Requirements Software Requirements Code Generation Only Axiom CMD565, VxWorks Module Axiom CMD565, VxWorks RAM Image Axiom CMD565, VxWorks ROM Image VxWorks Simulation Freescale ColdFire M5329EVB, uclinux PHYTEC LPC229 x, ecos Spectrum Digital DSK6713, DSP/BIOS Unix Console Unix UI Unicon UCN2410-CWIFI, Linux Windows Console Application ne Axiom CMD-565 Development Board Axiom CMD-565 Development Board, isystem ic3000activeemulator Axiom CMD-565 Development Board ne ColdFire M5329EVB Development Kit phycore-arm7/lpc229x Rapid Development Kit, GPIO Expansion Board DSP Starter Kit (DSK) for the TMS320C6713 ne ne Mobile Development Kit MKit UCN2410-CWIFI ne ne Wind River Tornado 2.2.1, VxWorks BSP for CMD565 Wind River Tornado 2.2.1, VxWorks BSP for CMD565, isystem winidea Wind River Tornado 2.2.1, VxWorks BSP for CMD565 Wind River Tornado 2.2.1, VxWorks 5.5.1, (Optional) ULIP Ethernet driver CodeSourcery ColdFire uclinux toolchain release m68k, CF Flasher 3.1, P&E Device Drivers Cygwin 1.5.x ecos 2.0 ARM toolchain TI's Code Composer Studio 3.1 Cygwin 1.5.x with gcc package Cygwin 1.5.x with gcc package Cygwin 1.5.x, FLTK toolchain Microsoft Visual Studio 2003 or Visual C Contact the respective vendors for more information about their hardware and software products. Refer to ecos.sourceware.org/getstart.html for information about downloading and installing ecos. Refer to gcc.gnu.org for information about downloading and installing gcc. The VxWorks for LabVIEW Embedded Development Module Evaluation Kit includes the Tornado integrated development environment and evaluation run-times for VxWorks for the purpose of demonstrating the features, performance, and capabilities of these Wind River products in association with the LabVIEW Microprocessor SDK. Refer to windriver.com/alliances/eval-cd, click National Instruments Evaluation CD Program, and follow the instructions to receive the VxWorks for LabVIEW Embedded Development Module Evaluation Kit. Refer to windriver.com for more information about Wind River s Device Software Optimization products, including VxWorks real-time operating systems and Tornado, an integrated development environment. LabVIEW Microprocessor SDK Release tes 2 ni.com

3 Installation This section includes information about installing the Microprocessor SDK on a development computer. te Refer to the LabVIEW Release tes for information about installing the LabVIEW development system. Complete the following steps to install the Microprocessor SDK. 1. Log in to the development computer as an administrator or as a user with administrative privileges. 2. Insert the LabVIEW Platform DVD. Tip You also can double-click setup.exe from the media to launch the installer. 3. Follow the instructions on the screen for installing software. a. Select the following software from the product list tree: LabVIEW Microprocessor SDK in the Embedded (Real-Time, FPGA, and Microprocessor) folder b. Continue to follow the instructions on the screen to complete installation of the software. The installer might prompt you to insert another DVD to continue installation. 4. Activate the Microprocessor SDK. You must activate the Microprocessor SDK to access the example targets. You have the option of activating the Microprocessor SDK at the end of installation. You also can use the NI License Manager, available by selecting Start»All Programs»National Instruments»NI License Manager, to activate National Instruments products. Refer to the National Instruments License Manager Help, available by selecting Help»Contents in the National Instruments License Manager, for more information about activating NI products. Tip If you have beta versions, previous versions, and/or multiple versions of the Embedded Development Module and/or Microprocessor SDK and the activation is not successful at the end of installation, use the NI License Manager to activate the software. Selecting an Appropriate Example Target Selecting an appropriate example target is a good place to start when you port LabVIEW to a new embedded target. Use the target that is closest to your target and toolchain. For example, if you are using a GNU C/C++-based (gcc) toolchain, consider using an ecos target. If you are using a VxWorks-based toolchain with different hardware, you might want to use a VxWorks subtarget. Subtargets are targets that reuse existing functionality from another target that uses the same operating system. The Microprocessor SDK also includes a blank template target. This target is not intended to be an implementation example, but the target can serve as a good starting point when none of the example targets are appropriate. National Instruments recommends you use the blank target when porting LabVIEW to a new operating system. ne of the example targets are meant to be fully featured, ready-to-use targets. The different example targets have different implementations. When you are implementing a feature for a new embedded target, look for an existing implementation in an existing example target that is similar to your target. Depending on the feature, you also might look for an existing implementation that uses the same operating system as your target. National Instruments Corporation 3 LabVIEW Microprocessor SDK Release tes

4 The following table lists which example targets contain example implementations of different features. Use this table to find an example of a feature you are implementing for your target. Target Name Instrumented Debugging On Chip Debugging Pre-Built Run-Time Library Static Memory Model Memory Mapping Elemental I/O IDE Integration UI Code Generation Only Axiom CMD565, VxWorks Module Serial Wind River WTX Axiom CMD565, VxWorks RAM Image isystem ic3000 Axiom CMD565, VxWorks ROM Image VxWorks Simulation Freescale ColdFire M5329EVB, uclinux PHYTEC LPC229x, ecos Serial Spectrum Digital DSK6713, DSP/BIOS RTDX Unicon UCN2410-CWIFI, Linux Unix Console Eclipse Simulated Eclipse Unix UI Windows Console Application Simulated Upgrading from Version 8.6 Changes in the LabVIEW Development System Refer to the LabVIEW Release tes and LabVIEW Upgrade tes, available by selecting Start»All Programs»National Instruments»LabVIEW 2009»LabVIEW Manuals, for information about new features and changes in the LabVIEW development system. Upgrading Target Support Because each target implementation is different, upgrading target support is different for every target. In general, you must complete the following steps to upgrade your target support. 1. Create a folder in LabVIEW 2009\Targets. National Instruments recommends using some version of your company name. LabVIEW Microprocessor SDK Release tes 4 ni.com

5 2. Create an Embedded folder under the LabVIEW 2009\Targets\company name directory. te LabVIEW does not recognize any targets outside of this directory. 3. Copy your target directory from LabVIEW 8.6, which is located in LabVIEW 8.6\Targets\company name\embedded, to the new LabVIEW 2009 directory you created in steps 1 and Select Tools»Microprocessor SDK»Target Editor in LabVIEW 2009 to launch the Target Editor and modify the TgtSupp.xml file. LabVIEW uses the TgtSupp.xml file to incorporate your target into LabVIEW. 5. Open all of your existing plug-in VIs in LabVIEW 2009 and verify none of the VIs are broken. 6. Move any target-specific VIs and palettes from the LabVIEW 8.6 directory to the LabVIEW 2009 directory. Instrumented Debugging Diagnostic Filename Change What's New You can configure LabVIEW to create an embedded debugging diagnostic file by adding a token to the LabVIEW.ini file, which is located in the labview directory. The token has changed from LogPDAMessages=True to LogCGenMessages=True. The resulting filename has changed from pdamsglog.txt to cgenlog.txt. This text file contains various debugging diagnostic and error messages that occur as a result of instrumented debugging connections. Use this file to help you implement and troubleshoot your instrumented debugging implementation. The Microprocessor SDK includes the following new features and changes: VIs and Functions Support and Enhancements The Microprocessor SDK includes the following support and enhancements: Application Status Window VIs Use the Application Status Window VIs to customize how the Application Status window interacts with your target. Current VI's Path Support The Current VI's Path function is now supported. The Current VI's Path function returns the path to the file of the current VI. The function returns <t A Path> for embedded targets that do not support file systems. Additional Fixed-Point Support The following functions now support the fixed-point data type: Divide Reciprocal Square Root In Range and Coerce Unflatten From XML Flatten To XML Thread-Safe Functions The Queue Operations functions are now thread safe. Synchronize Timed Structure Starts Support The Synchronize Timed Structure Starts VI is now supported. The Synchronize Timed Structure Starts VI synchronizes the start of Timed Loops or Timed Sequence structures. The clear and replace inputs are not supported. Stop Timed Structure Support The Stop Timed Structure VI is now supported. The Stop Timed Structure VI stops a Timed Loop or Timed Sequence structure. Execution Highlighting Support The Microprocessor SDK now supports execution highlighting, which you can use to view an animation of the execution of the block diagram. Execution highlighting is supported only for instrumented debugging. National Instruments Corporation 5 LabVIEW Microprocessor SDK Release tes

6 VI Call Configuration Support Use the VI Call Configuration dialog box to configure when to load a subvi. Right-click a subvi and select Call Setup from the shortcut menu to display this dialog box. Deprecated VIs The Microprocessor SDK no longer supports the Status Processor Window Utilities VIs. Use the Application Status Window VIs instead. Front Panel Controls Support and Enhancements The Microprocessor SDK includes the following support and enhancements: Scroll Bar Control Support Scroll bar controls are now supported. Use the scroll bar control to add custom scroll bars to a control with scrollable data. The scroll bar control includes vertical and horizontal scroll bars. Table Control Support Table controls are now supported. Use the table control to create a table on the front panel. Tree Control Support Single-column tree controls are now supported. Use the tree control to give users a hierarchical list of items from which to select. Tree controls in embedded VIs do not support column headers, row headers, or drag and drop. Graph and Chart Control Enhancements The graph and chart controls include the following enhancements: Improved Appearance Graphs and charts in embedded applications now have a high-color, three-dimensional appearance. Graphs and charts also include improved placement and appearance of scale labels and the plot area. Plot Legend Support Graphs and charts now support the plot legend, which you can use to customize how the plot appears in the plot area of a graph or chart. Cursor Legend Improvements Graphs and charts in embedded VIs now use the same cursor legend as graphs and charts in VIs running on Windows. Scale Legend Improvements Graphs and charts in embedded VIs now use the same scale legend as graphs and charts in VIs running on Windows. Graph Palette Support Graphs and charts now support the graph palette, which you can use to move cursors, zoom, and pan the display. Z-Order Support The LabVIEW C Code Generator now generates controls and indicators in the correct z-order. Properties and Methods Support and Enhancements The Microprocessor SDK includes the following support and enhancements: You can now use the following properties with tree controls: Active Item:Child-Only?, Active Item:Disabled?, Active Item:Indent Level, Active Item:Open?, Active Item:Row Number, Active Item:Symbol Index, and Active Item:Tag All Tags (read only) Displayed Items (read only) Number of Rows Size, Size:Height, and Size:Width Visible Items:Hierarchy Lines Visible and Visible Items:Symbols Visible You can use the following methods with tree controls: Custom Item Symbols:Get Symbol Array, Custom Item Symbols:Get Symbol, Custom Item Symbols:Revert All To Built In Symbols, Custom Item Symbols:Revert To Built In Symbol, Custom Item Symbols:Set To Custom Symbol Array, and Custom Item Symbols:Set To Custom Symbol LabVIEW Microprocessor SDK Release tes 6 ni.com

7 Edit Tree Items:Add Item to End, Edit Tree Items:Add Item, Edit Tree Items:Add Multiple Items to End, Edit Tree Items:Delete Item, Edit Tree Items:Move Item, Edit Tree Items:Set Tag, and Edit Tree Items:Sort Children Navigate Tree:Get Child, Navigate Tree:Get Next Item, Navigate Tree:Get Parent Item, Navigate Tree:Get Path, and Navigate Tree:Get Previous Item Open/Close:All, Open/Close:Ensure Visible, and Open/Close:Item Point to Row Column Application Status Window Funclist Wizard The Microprocessor SDK now includes the Application Status window, which you can use to determine the download, connection, and execution progress of embedded applications. The Application Status window is supported only on targets that support /IP. The Application Status window is implemented on the Windows Console and PHYTEC example targets. If you implement the Application Status window for your target, users display it by right-clicking a build specification under your target in the Project Explorer window. You can configure the Application Status window in the Build Specification Type Properties dialog box in the Target Editor. Use the Application Status Window tab in the Build Specification Type Properties dialog box to enable or disable the Application Status window for your target. By default, the Application Status window includes a General page and an Output page. Use the Application Status Window VIs and the Progress Bar Utilities VIs with your plug-in VIs to customize the Application Status window. If you implement the Application Status window for your target, you can allow processes to run concurrently. The Windows Console and PHYTEC example targets implement the Application Status window. The Windows Console example target is located in the labview\targets\ni\embedded\win32con directory. The PHYTEC example target is located in the labview\targets\ni\embedded\ecos\phytec_lpc229x directory. The Microprocessor SDK now includes the Funclist Wizard, which you can use to override subvi calls with C function calls. Instead of editing Funclist entries by hand, use the Funclist Wizard to generate Funclist entries. You can use the Funclist Wizard to override Funclist entries in the common Funclist files included with the Microprocessor SDK or to create your own target-specific Funclist files. The Funclist Wizard also includes error checking for formatting of Funclist entries and simplifies passing parameters directly into Funclist entries. Select Tools»Microprocessor SDK»Funclist Wizard to display the Funclist Wizard. Interrupt Configuration Wizard The Microprocessor SDK now includes the Interrupt Configuration Wizard, which you can use to create and configure interrupts for embedded targets and edit the function calls for interrupts. When you use the Interrupt Configuration Wizard to create an interrupt for a target, the wizard generates an interrupt.xml file and places it in the Targets\NI\Embedded\target\interrupt directory for that target. Select Tools»Microprocessor SDK»Interrupt Configuration Wizard to display the Interrupt Configuration Wizard. The Build Specification Properties dialog box now includes the Manage Interrupts page, which users of your target can use to configure VIs as ISR VIs. The Interrupt VIs page of the Build Specification Properties dialog box is obsolete. Use the Manage Interrupts page instead. National Instruments Corporation 7 LabVIEW Microprocessor SDK Release tes

8 LabVIEW Class Support You can now use LabVIEW classes in embedded VIs in the same way you use LabVIEW classes in VIs running on Windows. The Microprocessor SDK now supports using the following node and functions with LabVIEW classes: Call Parent Method Preserve Run-Time Class To More Generic Class To More Specific Class The Microprocessor SDK does not support using LabVIEW classes in the following VIs and functions: Get LV Class Default Value Get LV Class Path Flatten To String Unflatten From String Flatten To XML Unflatten From XML Variant To Flattened String Flattened String To Variant File I/O VIs and functions You cannot probe a LabVIEW class data type. You can debug and probe values on any static, dynamic, and accessor VIs of a LabVIEW class. Timed Loop Enhancements The Microprocessor SDK includes the following changes to Timed Loop support: The Microprocessor SDK now supports all input and output terminals for the nodes of Timed Loops except the Processor terminal. The Configure Timed Loop dialog box now includes the following options: Discard missed periods Specifies that the Timed Loop discards any data generated during missed iterations and executes on the next scheduled iteration the Offset / Phase and Period values establish. Maintain original phase Specifies that the Timed Loop returns to the original configured phase. Deadline Specifies a time boundary for the completion of an iteration of the Timed Loop. If the iteration does not complete before the specified Deadline, the Finished Late? [i-1] output on the Left Data node returns TRUE in the next iteration. Loop name Uniquely identifies the Timed Loop. The Offset / Phase option of the Configure Timed Loop dialog box is now supported for all timing sources. Microprocessor SDK Documentation The Microprocessor SDK includes the following documentation in addition to this document: The LabVIEW Microprocessor SDK Porting Guide, available by selecting Start»All Programs»National Instruments»LabVIEW 2009»LabVIEW Manuals and opening MicroprocessorSDK_Porting_Guide.pdf, contains the information you need to port LabVIEW to a new target. LabVIEW Microprocessor SDK Release tes 8 ni.com

9 The readme file, available by selecting Start»All Programs»National Instruments»LabVIEW 2009»Readme and opening readme_microprocessorsdk.html, contains known issues. The LabVIEW Help, available by selecting Help»Search the LabVIEW Help, contains reference information about LabVIEW palettes, menus, tools, VIs, and functions. The LabVIEW Help also contains step-by-step instructions for using LabVIEW. The LabVIEW Help uses (Microprocessor SDK) in the index to indicate topics specific to the Microprocessor SDK and embedded targets. National Instruments Corporation 9 LabVIEW Microprocessor SDK Release tes

10 National Instruments, NI, ni.com, and LabVIEW are trademarks of National Instruments Corporation. Refer to the Terms of Use section on ni.com/legal for more information about National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies. For patents covering National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent tice at ni.com/patents National Instruments Corporation. All rights reserved E-01 Jun09