| Installation Known Issues |
| ID | Known Issue |
| — | You must install VisualDSP++ 5.0 before you can install the Embedded Module for Blackfin Processors. To install VisualDSP++ 5.0, double-click VisualDSP++5.0.exe on the top-level of the Embedded Module for Blackfin Processors Installation DVD. After you install VisualDSP++ 5.0, you can install the Embedded Module for Blackfin Processors by double-clicking setup.exe on the top-level of the installation DVD and following the instructions. |
| General Known Issues |
| ID | Known Issue |
| 125085 | Values on the Output tab of the Processor Status window update slowly when running an application with a user interface on the target.
Workaround—Use an indicator on the user interface to see the output from the application or select Serial port in the Console Output section of the Communication Options page of the Build Specification Properties dialog box. |
| 125084 | Disabling cache in applications with a user interface sometimes causes application to run incorrectly.
Workaround—Make sure there is a checkmark in the Enable cache checkbox of the Advanced Options page of the Build Specification Properties dialog box when building an application with a user interface. |
| 122246 | Column titles in the Profile Results window sometimes display incorrectly even though the data is correct. The column titles should be VI Name, Node Index, Node Type, Count, and Last Execution Time (us). |
| 43865 | In the NI Example Finder, the Duplicate .lvproj file and contents option in the Save As dialog box does not always copy.
Workaround—Manually copy the example and all of its dependencies to a different folder. |
| — | Target syntax checking might not happen until you edit an embedded VI. |
| — | Target syntax checking does not work on data types inside of clusters. |
| — | Because reading and writing of strings, clusters, and arrays is not synchronized in Blackfin applications, sometimes front panel controls and indicators do not update properly when you use the JTAG/non-instrumented debugging mode.
Workaround—Set breakpoints on the wires to the controls or indicators you are debugging. |
| 41265 | Probes on time stamps do not work with non-instrumented (JTAG) debugging. |
| — | The Embedded Module for Blackfin Processors does not support creating a source distribution. If you right-click Build Specifications in the Project Explorer window and select New»Source Distribution from the shortcut menu, LabVIEW displays an error message in the Source Distribution Properties dialog box. |
| — | You can use integer values as inputs to expressions. However, functions that operate on the input use C rounding rules when the input is integer. This means that each function rounds down when returning its value to the rest of the expression. On Windows desktop targets, the functions round to nearest integer instead. |
| 4DA9QP30 | When you use time stamp constants or controls to enter time stamps on the host PC, the time zone of the host machine is used, but time stamps print out in GMT. This is because Blackfin targets do not support time zones, so time stamps are always considered GMT, regardless of the time stamp on the host PC. |
| — | MathScript is unsupported on embedded targets. |
| — | The Timed Loop introduces threads to the generated C code. However, the following parts of LabVIEW are not thread-safe: - Local and global variables
- Data types that use reference numbers (refnums)
- VI Server
- Queues and notifiers—Use the RT FIFO VIs to pass data between Timed Loops instead
- Serial I/O
|
| — | Indicators represented as double data types do not update for integer values. Change the representation of the indicator by right-clicking the indicator, selecting Representation from the shortcut menu, and selecting a different data type. |
| — | When debugging using JTAG/EZ-KIT USB mode, front panel controls briefly revert to the previous value before updating the Blackfin processor with data. |
| — | The Embedded Module for Blackfin Processors does not include a CAN driver. |
| — | A linker error occurs if you include an external C file in a project and the external C file has the same name as a VI in the same project. |
| — | The Embedded Module for Blackfin Processors does not support downloading and running Blackfin applications on a compiled simulator. |
| — | If you have multiple versions of VisualDSP++ on the host computer, you can experience unpredictable behavior in LabVIEW if you run a version of VisualDSP++ other than VisualDSP++ 5.0 and then launch LabVIEW. To resolve this issue if you launched a different version of VisualDSP++ since you last launched LabVIEW, launch VisualDSP++ 5.0 before relaunching LabVIEW. |
| — | If you flatten data that contains an extended precision or complex precision floating-point data type, the flattened data is incompatible with any other LabVIEW version or add-on except the Embedded Module for Blackfin Processors. |
| — | Any binary operation involving a dynamic data type and a non-scalar non-dynamic data type, such as a 1D array, does not work correctly. |
| — | When you create a VI that uses multiple global variables, do not copy controls from one global variable to another global variable. If you copy and paste global variables, you receive an error when you try to build the VI into an application. |
| — | Blackfin VIs do not support the values of Z, X, or T in digital data controls and digital waveform controls. You can use values of 0, 1, L, and H. |
| Windows Vista Known Issues |
| ID | Known Issue |
| 91435 | On the multi-byte versions of Windows, such as the Japanese version of Windows Vista, VisualDSP++ cannot compile the C files that LabVIEW generates. |
| — | The Embedded Module for Blackfin Processors does not run on the Windows Vista x64 Edition, the 64-bit version of the operating system. |
| User Interface Known Issues |
| ID | Known Issue |
| 121087 | If the user interface you want to generate contains a graphic file, such as a bitmap, JPEG, or GIF, the compiler generates errors when you try to build the VI into an application. |
| VIs, Functions, and Structures Known Issues |
| ID | Known Issue |
| 111408 | When you use the Display Message to User Express VI to display a message to a user, execution of other loops is halted.
Workaround—Use a subVI instead of a dialog box. |
| 124598 | You cannot open and update the front panel of a subVI within a Timed Loop. Updating the front panel of a subVI within a Timed Loop can cause LabVIEW to crash.
Workaround—Place the subVI in a While Loop. |
| — | If a VI contains a Timed Loop without at least one While Loop running in parallel, the VI uses 100% of the processor.
Workaround—Place a While Loop containing a Wait (ms) function, or something similar, in the VI outside of the Timed Loop. |
| 4H7C2000 | The Escape XML and Unescape XML VIs are unsupported. |
| — | If you receive empty dynamic data from functions with two inputs and one output, check to see if you have a dynamic data type wired to one input and an array of scalars wired to the other input.
Workaround—Use the Convert to Dynamic Data Express VI to convert the scalar array to a dynamic data type before you wire the input to the function. |
| 44L9FO30 | The abs() function might return incorrect results when the input value is -2147483648. |
| 481G1I30 | Placing more than one BF FIR Filter VI on a block diagram might cause the BF FIR Filter to return incorrect results. |
| — | Changing the voltage or clock frequency using VIs from the Power palette while the Processor Status window is open can cause a Blackfin application to hang. |
| — | If you set the allow empty tokens? input to TRUE in the Scan String for Tokens function and the string starts with a delimiter, the offset past token output and the token string output contains incorrect values. |
| — | If you are using instrumented debugging, the Wait Until Next ms Multiple function does not change the timing if the function updates inside of a loop.
Workaround—Turn off debugging or use a Timed Loop and update the Period terminal from within the Timed Loop. |
| — | When you use a #include in an Inline C Node to add a header file, the #include is inserted in the middle of the C file, which can cause problems with scoping.
Workaround—Use the Add/Remove Header Files dialog box to add header files. Adding header files using the Add/Remove Header Files dialog box inserts the code at the top of the generated C file. |
| — | Reserved words are used in the generated C code. Using these words as inputs or outputs in an Inline C Node can cause unexpected behavior or the embedded application to crash.
Workaround—Change the name of the variables to something else. |
| 38853 | The Call Chain function cannot be used with Timed Loops, including any VIs called from within the Timed Loop. |
| 4DBDFL00 | Elemental I/O is not implemented for the BF54x targets. |
| 4DCH4CSG | The BF Real Fast Fourier Transform VI crashes if N is not a power of two. |
| — | The Draw Text at Point and the Get Text Rect VIs are unsupported in Blackfin VIs. |
| — | Dynamic Add/Remove Signals is unsupported. |
| — | You must use strict C code in Formula Nodes you use in Blackfin VIs. However, LabVIEW does not check the C syntax in the Formula Node syntax while in edit mode. If you build a VI into a Blackfin application that contains a Formula Node with non-strict C code, LabVIEW returns a general error. |
| — | The Delay Values Express VI and the Trigger and Gate Express VI do not function correctly in Blackfin VIs because maintaining state in local variables between calls to a subVI is not supported. |
| Building VIs into Applications Known Issues |
| ID | Known Issue |
| — | If you try to build an embedded VI that is password-protected into an embedded application, the build fails with syntax errors if you enter the wrong password. |
| — | Enabling cache by placing a checkmark in the Enable cache checkbox on the Advanced Options page in the Build Specification Properties dialog box and enabling TCP by placing a checkmark in the Enable lwIP TCP/IP support checkbox on the Communication Options page, can cause the Blackfin application to become unstable and hang when running on a BF537 target. |
| Debugging Known Issues |
| ID | Known Issue |
| — | Debugging reentrant VIs is not supported. |
| Additions to the Help |
| ID | Known Issue |
| — | The behavior of the Run button changed since the LabVIEW Help released. If you click the Run button in Blackfin VIs, LabVIEW runs the application in run or debug mode depending on the default build specification. |
| Documentation Known Issues |
| ID | Known Issue |
| 42862 | The context help for an Elemental I/O Node is incorrect if you place an Elemental I/O Node on a block diagram without first adding the node to the project. The correct context help is: Performs specific Elemental I/O operations on Blackfin targets. You can configure the Elemental I/O Node with one or more Elemental I/O items. To add additional Elemental I/O items to an Elemental I/O Node, right-click the I/O Item section and select Add Element from the shortcut menu. You also can expand or contract the Elemental I/O Node by clicking the upper or lower edge of the node with the Positioning tool and dragging the edge up or down. |
| 4BPCFOWD | The Detailed Help link in the Context Help window does not open the correct topic for the Inline C Node.
Workaround—Open the LabVIEW Help by selecting HelpпSearch the LabVIEW Help. Click the Index tab and select Inline C Node. |
| 4BHDSTWD | The Help button in the Add/Remove Headers dialog box does not open the correct help topic.
Workaround—Open the LabVIEW Help by selecting Help»Search the LabVIEW Help. Click the Index tab and select Add/Remove Headers dialog box (Embedded Targets, PDA, TPC). |
| 4AIEH2WD | The Blackfin VIs reference topics in the LabVIEW Help do not contain the Place on the block diagram or the Find on the Functions palette buttons. |
| — | Blackfin-specific VIs do not contain the Open example buttons. Blackfin-specific examples are available in the LabVIEW\examples\lvemb\Blackfin directory. Open the .lvproj file to open the project and the example Blackfin VI. |