Archived: LabVIEW 2010 Embedded Module for ARM Microcontrollers Known Issues

Publish Date: Dec 21, 2017 | 0 Ratings | 0.00 out of 5 | Print

Overview

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

This document contains the LLabVIEW 2010 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.

Table of Contents

Document Organization

The Known Issues Document is divided into two separate tables. 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.

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.

Known Issues by Date

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.

Analysis and Math
225248 Analysis Library functions that resize arrays might generate unexpected results when used with Microlib
Building and Distributing LabVIEW Applications
121512 User specified compiler Optimization level is ignored if JTAG debugging is enabled
225248 Analysis Library functions that resize arrays might generate unexpected results when used with Microlib
236274 Build error when string indicators are used in non-threaded interrupt handler VIs
242453 Pressing Pause while debugging an ARM application over JTAG does not highlight the place where execution stops
Documentation
241162 Build Specification does not expose the "Generate Integer Only" option but the Help still lists it
240886 "Additional LabVIEW Documentation" link in the online Help points to a blank page
Functions, VIs, and Express VIs
181189 I2C VIs do not support interface selection or multiple slave addresses
200372 Profile data might be incorrect if your Application has Timed Loops in it
216128 Timed Loops run with a default priority of 100 if the Configure Timed Loop dialog box is not opened
225248 Analysis Library functions that resize arrays might generate unexpected results when used with Microlib
304683 PWM Elemental IO node on the TI LM3S8962 ARM target ignores the pre-divider setting
276403 Serial ports 2 and 3 on the MCB2300 evaluation board can not be used in LabVIEW
286504 Elemental IO resource name does not match with peripheral on the Luminary LM3S8962 Evaluation Board
Miscellaneous
196444 While Profiling an Application, a data abort error occurs if debugging is disabled on any VI in the Application



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

Reported Version: 2010    Resolved Version: N/A    Added: 07/22/2010
Building and Distributing LabVIEW Applications
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
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

Reported Version: 2010    Resolved Version: N/A    Added: 07/22/2010
236274

Return
Build error when string indicators are used in non-threaded interrupt handler VIs
Using string indicators in non-threaded interrupt handler VIs causes build errors.

Workaround: Do not use indicators in interrupt handler VIs.

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

Reported Version: 2010    Resolved Version: N/A    Added: 07/30/2010
Documentation
241162

Return
Build Specification does not expose the "Generate Integer Only" option but the Help still lists it
The "Generate Integer Only" option has been removed from the Build Specification for ARM targets in LabVIEW 2010. However, the ARM module Help still lists it.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2011    Added: 07/21/2010
240886

Return
"Additional LabVIEW Documentation" link in the online Help points to a blank page
The "Additional LabVIEW Documentation" link in the online Help for the LabVIEW 2010 Embedded Module for ARM Microcontrollers might point to a blank page.

Workaround: Additional LabVIEW Documentation can be found here: http://zone-test.ni.com/reference/en-XX/help/371361G-01/lvconcepts/LabVIEW_documentation_resources/

Reported Version: 2010    Resolved Version: 2011    Added: 07/22/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
200372

Return
Profile data might be incorrect if your Application has Timed Loops in it
While profiling an Application, the data returned by the profiler might be incorrect or unclear if the application contains Timed Loops.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2011    Added: 06/02/2010
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.

Reported Version: 2010    Resolved Version: N/A    Added: 06/02/2010
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

Reported Version: 2010    Resolved Version: N/A    Added: 07/22/2010
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

Reported Version: 2010    Resolved Version: 2012    Added: 07/28/2011
276403

Return
Serial ports 2 and 3 on the MCB2300 evaluation board can not be used in LabVIEW
The MCB2300 evaluation board has 4 serial ports but only COM0 and COM1 are populated using DB9 connectors. Using the Serial Connectivity VIs to access port 2 and 3 fails in LabVIEW.

Workaround: N/A

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

Reported Version: 2010    Resolved Version: N/A    Added: 07/29/2011
Miscellaneous
196444

Return
While Profiling an Application, a data abort error occurs if debugging is disabled on any VI in the Application
While profiling an Application, if debugging is disabled for any VI in the application, the profiler fails to generate proper information for it. This causes a Data Abort error and the application terminates prematurely.

Workaround: Debugging must be enabled in the VI Properties for every VI in the application: Right-click the VI icon on the front panel or block diagram and select VI Properties from the shortcut menu or select File»VI Properties to display the dialog box. Select the Execution category and place a checkmark in the Allow debugging checkbox

Reported Version: 2009    Resolved Version: 2011    Added: 06/02/2010

Known Issues by Date

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

121512 User specified compiler Optimization level is ignored if JTAG debugging is enabled
181189 I2C VIs do not support interface selection or multiple slave addresses
196444 While Profiling an Application, a data abort error occurs if debugging is disabled on any VI in the Application
200372 Profile data might be incorrect if your Application has Timed Loops in it
216128 Timed Loops run with a default priority of 100 if the Configure Timed Loop dialog box is not opened
241162 Build Specification does not expose the "Generate Integer Only" option but the Help still lists it
225248 Analysis Library functions that resize arrays might generate unexpected results when used with Microlib
240886 "Additional LabVIEW Documentation" link in the online Help points to a blank page
236274 Build error when string indicators are used in non-threaded interrupt handler VIs
242453 Pressing Pause while debugging an ARM application over JTAG does not highlight the place where execution stops
304683 PWM Elemental IO node on the TI LM3S8962 ARM target ignores the pre-divider setting
276403 Serial ports 2 and 3 on the MCB2300 evaluation board can not be used in LabVIEW
286504 Elemental IO resource name does not match with peripheral on the Luminary LM3S8962 Evaluation Board



ID Known Issue
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
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
196444

Return
While Profiling an Application, a data abort error occurs if debugging is disabled on any VI in the Application
While profiling an Application, if debugging is disabled for any VI in the application, the profiler fails to generate proper information for it. This causes a Data Abort error and the application terminates prematurely.

Workaround: Debugging must be enabled in the VI Properties for every VI in the application: Right-click the VI icon on the front panel or block diagram and select VI Properties from the shortcut menu or select File»VI Properties to display the dialog box. Select the Execution category and place a checkmark in the Allow debugging checkbox

Reported Version: 2009    Resolved Version: 2011    Added: 06/02/2010
200372

Return
Profile data might be incorrect if your Application has Timed Loops in it
While profiling an Application, the data returned by the profiler might be incorrect or unclear if the application contains Timed Loops.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2011    Added: 06/02/2010
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.

Reported Version: 2010    Resolved Version: N/A    Added: 06/02/2010
241162

Return
Build Specification does not expose the "Generate Integer Only" option but the Help still lists it
The "Generate Integer Only" option has been removed from the Build Specification for ARM targets in LabVIEW 2010. However, the ARM module Help still lists it.

Workaround: N/A

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

Reported Version: 2010    Resolved Version: N/A    Added: 07/22/2010
240886

Return
"Additional LabVIEW Documentation" link in the online Help points to a blank page
The "Additional LabVIEW Documentation" link in the online Help for the LabVIEW 2010 Embedded Module for ARM Microcontrollers might point to a blank page.

Workaround: Additional LabVIEW Documentation can be found here: http://zone-test.ni.com/reference/en-XX/help/371361G-01/lvconcepts/LabVIEW_documentation_resources/

Reported Version: 2010    Resolved Version: 2011    Added: 07/22/2010
236274

Return
Build error when string indicators are used in non-threaded interrupt handler VIs
Using string indicators in non-threaded interrupt handler VIs causes build errors.

Workaround: Do not use indicators in interrupt handler VIs.

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

Reported Version: 2010    Resolved Version: N/A    Added: 07/30/2010
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

Reported Version: 2010    Resolved Version: 2012    Added: 07/28/2011
276403

Return
Serial ports 2 and 3 on the MCB2300 evaluation board can not be used in LabVIEW
The MCB2300 evaluation board has 4 serial ports but only COM0 and COM1 are populated using DB9 connectors. Using the Serial Connectivity VIs to access port 2 and 3 fails in LabVIEW.

Workaround: N/A

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

Reported Version: 2010    Resolved Version: N/A    Added: 07/29/2011

Document last updated on 7/16/2012

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit