| R12 Release Notes | |
Known Software and Documentation Problems
This section updates the Motorola DSP Developer's Kit 1.0 documentation set, reflecting known software and documentation problems.
Interactive Mode Not Currently Supported on Solaris
Interactive mode has been temporarily disabled on Solaris.
Limited Support on Microsoft Windows Platforms
The following interactive mode functions have been disabled for Microsoft Windows platforms:
Multiple Users On the Same Machine
Two users cannot run interactive mode on the same machine at the same time.
However, if two users are working on the same machine simultaneously, one user can use interactive mode and the other can use all the functionality except interactive mode. The second user can use interactive mode after the first user is finished.
Exiting Interactive Mode
The proper way to exit interactive mode is to exit the Simulator itself. This causes the MATLAB engine to be terminated automatically.
Suite56 Simulator Abnormal Termination (Solaris)
On Solaris, if the interactive mode Suite56 Simulator GUI terminates abnormally, you may need to clean up the interprocess communications pipes. You can do this by using the following commands.
ipcs <hit return> ipcrm -q <ID><hit return>
Stand-Alone GUI Simulator May Hang
(Windows NT)
Calling the simulator Run() method immediately after instantiating the simulator object causes the Stand-alone GUI Simulator to hang.
To avoid this problem, call WriteToMem/Reg() between instantiating the simulator object and calling Run().
Other Solaris-Specific Limitations
Limited Compiler Support
MEX-file builds currently only support Version 5.0 of Sun's native CC compiler.
Use Full Pathnames
Using partial (relative) pathnames on Solaris machines may cause problems. Use full (absolute) pathnames for files where appropriate, or use ./ to indicate the current working directory.
Documentation Updates
The following information supplements the information found in the online Motorola DSP Developer's Kit User's Guide.
Setting the System Path
If you experience problems related to the system path, make sure that the following system global variables are set for your platform.
For Microsoft Windows 95 and Windows 98 . Make sure your autoexec.bat file includes the <MATLAB_INSTALL_DIR>\bin directory in the path variable.
Use the following command if this path is not already set, and then reboot for the changes to take effect.
SET PATH=%PATH%;<MATLAB_INSTALL_DIR>\bin
For Solaris. To enable Motorola MEX-files to run from any working directory, add the following directory to your LD_LIBRARY_PATH environment variable, if it does not already exist.
<MATLAB_INSTALL_DIR>/bin/
Rebuilding the Motorola DSP Developer's Kit
You can conveniently rebuild the entire Motorola DSP Developer's Kit by using the supplied build_all_xxx.m scripts to build from the <matlab>/toolbox/motdsp/motdspmex directory. These scripts take between 20 and 90 minutes to run, depending on the platform and hardware specifications.
Building MEX-Files
Use motdsp_mexopts3xx.sh or motdsp_mexopts6xx.sh to build MEX-files. Specify the MEX options by using the -f flag. On Solaris, these files are supplied in the motdspmex directory. On Windows, you must execute the motdsp_build_mexopts.m script to generate the motdsp_mexopts*.sh files.
Length Function and Block are Obsolete
The toolbox functions mot563_length and mot566_length, mentioned in the documentation, have been removed. The corresponding blocks have also been removed from the blockset. Use the MATLAB built-in length function to calculate lengths.
| | New Features | Neural Network Toolbox 4.0 Release Notes | |