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.
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.
The following items are known issues in LabVIEW 2009 SP1 Embedded Module for Blackfin Processors sorted by Category.
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
Document last updated on 11/10/2010