NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
This document contains the LabVIEW 2011 Embedded Module for ARM Microcontrollers known issues that were discovered before and since the release of LabVIEW 2011 Embedded Module for ARM Microcontrollers. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The LabVIEW 2011 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The Known Issues Document is divided into two separate tables. The following section displays the issues by issue category.
Please refer to Developer Zone Article LabVIEW Known Issues Categories Defined for an explanation of the categories and what types of issues are in each category.
For those who wish to locate the newly reported issues, we have also have published a section of the known issues table sorted by the date the issue was added to the document.
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The following items are known issues in LabVIEW 2011 Embedded Module for ARM Microcontrollers sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Analysis and Math | ||||||
| 225248 Return | Analysis Library functions that resize arrays might generate unexpected results when used with Microlib When building ARM applications with MicroLib (not a default selection), advanced analysis library functions that resize arrays can generate unexpected results. Advanced analysis library functions can be found on the Signal Generation and Mathematics palettes. By default, ARM applications are built with the Standard Library and not MicroLib. However, this option can be set through the uVision project. Workaround: N/A
| |||||
| Building and Distributing LabVIEW Applications | ||||||
| 307209 Return | First time builds using the Compile Farm Server might fail with an error First time builds of ARM applications using the Compile Farm might fail with an error such as "missing file at the following location: Untitled Project 1\MCB2300\Application\4.01\Project\LabVIEW.uvopt.tmp". This error is due to synchronization issues when copying files to the Compile Server. Workaround: Rebuild the application.
| |||||
| 121512 Return | User specified compiler Optimization level is ignored if JTAG debugging is enabled The user specified value of compiler optimization level (-Ox), set in the Advanced Compilation Options in the Build Specification is ignored if JTAG debugging is enabled. A default of -O0 is used in this case. Workaround: N/A
| |||||
| 225248 Return | Analysis Library functions that resize arrays might generate unexpected results when used with Microlib When building ARM applications with MicroLib (not a default selection), advanced analysis library functions that resize arrays can generate unexpected results. Advanced analysis library functions can be found on the Signal Generation and Mathematics palettes. By default, ARM applications are built with the Standard Library and not MicroLib. However, this option can be set through the uVision project. Workaround: N/A
| |||||
| 242453 Return | Pressing Pause while debugging an ARM application over JTAG does not highlight the place where execution stops While debugging an application using JTAG on an ARM target, pressing pause does stop the VI but you cannot single step after this and LabVIEW does not indicate where the VI stopped execution. This is because pressing pause simply sends a stop command to the target and LabVIEW does not know where the application stopped in relation to the VI. Workaround: Set breakpoints in your VI to stop execution
| |||||
| 284430 Return | Indicators of Extended Precision data type do not display proper values when debugging on ARM targets Workaround: N/A
| |||||
| Functions, VIs, and Express VIs | ||||||
| 304683 Return | PWM Elemental IO node on the TI LM3S8962 ARM target ignores the pre-divider setting The PWM elemental IO nodes on the TI LM3S8962 ARM target, expose a pre-divider settings in the properties. However, this setting is ignored in the elemental IO node in your block diagram. Workaround: N/A
| |||||
| 181189 Return | I2C VIs do not support interface selection or multiple slave addresses The ARM I2C VIs do not give you the ability to use all available I2C interfaces (ports) on your Microcontroller. They also do not have the ability to address multiple slaves. Workaround: N/A
| |||||
| 216128 Return | Timed Loops run with a default priority of 100 if the Configure Timed Loop dialog box is not opened The default priority of a Timed Loop should be 25 when targeting an ARM Microcontroller. However if a Timed Loop is added to the Block Diagram of an ARM VI and saved without opening the Configure Timed Loop dialog box, the default priority is configured at 100. This can cause significant difference in the timing behavior of your application, if multiple timed loops are present. Workaround: Whenever you add a Timed Loop to the Block Diagram, double-click its Input node or right-click the node and select Configure Input Node from the shortcut menu to display the Configure Timed Loop dialog box. This should automatically set its priority to 25. Now click OK to save the correct priority.
| |||||
| 225248 Return | Analysis Library functions that resize arrays might generate unexpected results when used with Microlib When building ARM applications with MicroLib (not a default selection), advanced analysis library functions that resize arrays can generate unexpected results. Advanced analysis library functions can be found on the Signal Generation and Mathematics palettes. By default, ARM applications are built with the Standard Library and not MicroLib. However, this option can be set through the uVision project. Workaround: N/A
| |||||
| 286504 Return | Elemental IO resource name does not match with peripheral on the Luminary LM3S8962 Evaluation Board On the TI LM3S8962 evaluation board, the user LED is designated LED1. However, the elemental IO node to access this LED is displayed as LED0 in LabVIEW. Workaround: N/A
| |||||
| 306720 Return | Merge Errors function is not available in functions palette on ARM targets Workaround: Open functions palette in a VI under the My Computer target, drop the Merge Errors function and copy to your ARM VI
| |||||
| Installation and Activation | ||||||
| 331211 Return | EK-LM3S8962 USB drivers fail to install on 64-bit operating system. When performing a custom installation of LabVIEW Embedded for ARM 2011 the EK-LM3S8962 USB drivers fail to install on 64-bit operating systems. Workaround: Install the drivers in the order described in the documentation.
| |||||
| 331208 Return | EK-LM3S8962 USB drivers do not install by default. When installing LabVIEW Embedded for ARM 2011 the EK-LM3S8962 USB drivers do not install by default. Workaround: N/A
| |||||