Archived: LabVIEW 2009 Embedded Module for ARM Microcontrollers Known Issues

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.

Überblick

This document has been archived and is no longer updated by National Instruments.

This document contains the LabVIEW 2009 Embedded Module for ARM Microcontrollers known issues that were discovered before and since the release of LabVIEW 2009. 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 2009 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. However, NI has become aware of a number of issues of potential significance regarding Microsoft Windows 7. To learn how Windows 7 affects your use of NI products, visit ni.com/info and enter the Info Code windows7.

Document Organization

The following section displays the issues by issue category.

Known Issues by 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.

 

Contacting NI

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.

Known Issues by Category

The following items are known issues in LabVIEW 2009 Embedded Module for ARM Microcontrollers Known Issues sorted by Category.

Building and Distributing LabVIEW Applications
177087 In the Project Build Specifications, if "Use stack variables" and "Disable parallel execution" are not enabled together, LabVIEW ignores both options
177405 Using timestamp functions with Serial or TCP debugging causes the build to break
121512 User specified compiler Optimization level is ignored if JTAG debugging is enabled
Functions, VIs, and Express VIs
181189 I2C VIs do not support interface selection or multiple slave addresses
Installation and Activation
154697 Installation of the LabVIEW ARM Module fails if %TEMP% contains Japanese characters



ID Known Issue
Building and Distributing LabVIEW Applications
177087

Return
In the Project Build Specifications, if "Use stack variables" and "Disable parallel execution" are not enabled together, LabVIEW ignores both options
The "Disable parallel execution" option is necessary to enable the "Use stack variables" optimization. The Build Specification does not explicitly mention this dependency. If the "Disable parallel execution" option is unchecked, the "Use stack variables" optimization is ignored.

Workaround: Always use "Disable parallel execution" with the "Use stack variables" optimization.

Reported Version: 2009    Resolved Version: 2010    Added: 07/27/2009
177405

Return
Using timestamp functions with Serial or TCP debugging causes the build to break
While using debugging over TCP Port or Serial Port, the Application will fail to build if one or more VIs in the project contains timestamp functions. This issue can be seen with the timestamp datatype and all associated functions.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2010    Added: 07/28/2009
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

Reported Version: 1.0    Resolved Version: N/A    Added: 06/02/2010
Functions, VIs, and Express VIs
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

Reported Version: 2009    Resolved Version: N/A    Added: 06/02/2010
Installation and Activation
154697

Return
Installation of the LabVIEW ARM Module fails if %TEMP% contains Japanese characters
The installation of the LabVIEW 2009 Embedded Module for ARM Microcontrollers will fail on the Japanese language version of Windows XP if the %TEMP% path contains Japanese characters.

Workaround: Change the %TEMP% environment variable to all english characters.

Reported Version: 2009    Resolved Version: 2010    Added: 07/27/2009

Document last updated on 7/16/2012

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).