Archived: LabVIEW 2009 and 2009 SP1 Embedded Module for Blackfin Processors 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 known issues that were discovered before and since the release of LabVIEW 2009 SP1 Embedded Module for Blackfin Processors. 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.

Each Issue appears as a row in the table and includes these fields:
  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of LabVIEW the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)

Document Organization

The Known Issues Document 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

You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in this document. If you have feedback on this specific document, please contact NI on this NI Developer Zone post.

Known Issues by Category

The following items are known issues in LabVIEW 2009 SP1 Embedded Module for Blackfin Processors sorted by Category.

 

Building and Distributing LabVIEW Applications
169994 LabVIEW generated C Code might not compile on multi-byte versions of Microsoft Windows
Controls and Indicators
253778 Controls and Indicators of Complex_float type do not exchange data with the Block Diagram
Example Programs
193593 BF533 Web LED.lvproj is listed in the Example Finder but is not installed with the module
Functions, VIs, and Express VIs
250097 Timed loops do not run with specified timing in certain conditions
190016 Using Event Structures inside Timed Loops might cause unexpected behavior on a BF548 EZKit
LabVIEW Project
163553 Closing the project during a debugging session does not stop the session



ID Known Issue
Building and Distributing LabVIEW Applications
169994

Return
LabVIEW generated C Code might not compile on multi-byte versions of Microsoft Windows
On multi-byte versions of Microsoft Windows such as the Japanese version of Windows XP/Vista/7, VisualDSP++ cannot compile the C files that LabVIEW generates.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 11/10/2010
Controls and Indicators
253778

Return
Controls and Indicators of Complex_float type do not exchange data with the Block Diagram
Controls and Indicators of Complex_float type do not exchange data with the Block Diagram. Wires connected to controls will always carry default values. Wires connected to Indicators will show results when probed but these results will not update the corresponding Indicators on the Front Panel.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 11/10/2010
Example Programs
193593

Return
BF533 Web LED.lvproj is listed in the Example Finder but is not installed with the module
BF533 Web LED.lvproj is listed in the Example Finder (Toolkits and Modules>>Blackfin>>Fundamentals). However, double-clicking on the example brings up an error dialog. This example is not installed by the LabVIEW Embedded Module for Blackfin Processors.

Workaround: A similar example does exist for the BF536 target, you can find it at \examples\lvemb\Blackfin\BF536\Web LED. You can change the target in the Project Explorer from BF536 to BF533 to target your BF533 EZKit.

Reported Version: 2009    Resolved Version: N/A    Added: 11/09/2010
Functions, VIs, and Express VIs
250097

Return
Timed loops do not run with specified timing in certain conditions
When Timed Loops are configured with the 1 MHz time source and the "Discard missed periods" and "Maintain original phase" checkboxes are checked, your timed loop may run with rate that is different from the specified rate.

Workaround: Do not have both the "Discard missed periods" and "Maintain original phase" checkboxes checked at the same time if you are using the 1 MHz time source.

Reported Version: 2009    Resolved Version: N/A    Added: 11/01/2010
190016

Return
Using Event Structures inside Timed Loops might cause unexpected behavior on a BF548 EZKit
If you have an Event Structure inside a Timed Loop, the loop might not always wait for the event structure to execute. A While Loop with an Event Structure inside it also shows similar behavior when there is another running While loop in parallel with it on the Block Diagram.

Workaround: Avoid using Block Diagram constructs as mentioned above.

Reported Version: 2009    Resolved Version: N/A    Added: 11/10/2010
LabVIEW Project
163553

Return
Closing the project during a debugging session does not stop the session
When debugging using the JTAG/USB EZ-KIT, closing the project does not stop the debugging session. Closing the VI manually crashes LabVIEW

Workaround: Terminate the debugging session before closing the VI or the project

Reported Version: 2009    Resolved Version: N/A    Added: 07/28/2009

Document last updated on 11/10/2010

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).