|
The release notes give users instructions on dealing with many issues not covered in other documentation. The solutions to many common problems are found in the release notes.
1 New Features
Solaris 5.8/VxWorks 5.4 BSP
A new GedaeTM Board Support Package (BSP), Solaris/VxWorks has been develop for Solaris 5.8 running Tornado 2.1 and the MVME5101 board running VxWorks 5.4.
Solaris 5.8/Mercury Altivec BSP
A new Gedae BSP, Solaris/McosAltivec, is now being delivered to run with a Solaris 5.8 host and the Mercury MCOS 5.6 operating system.
VxWorks 5.4/Mercury Altivec BSP
A new Gedae BSP, VxWorks/McosAltivec, is now being delivered to run with a VxWorks 5.4 host and the Mercury MCOS 5.6 operating system
Solaris/VxWorks/Mercury Multihop BSP
A multihop BSP has been developed that allows the Solaris/VxWorks BSP and the VxWorks/Mercury BSP to be combined into one BSP in which a Solaris 5.8 workstation controls a VxWorks 5.4 host of Mercury Altivec boards running MCOS 5.6
Windows NT 4.0/Mercury PCI BSP Upgraded to MCOS 5.6
The Gedae Board Support Package (BSP), NT/McosAltivec, has been upgraded from MCOS 5.5 to MCOS 5.6.
GSIM_Gedae Performance Simulator DSA Communication
The GSIM Performance Simulator has been enhanced to provide a simulation of the DSA (Direct Schedule Access) communication mechanism of Gedae.
Specifying the Non-Blocking size of Transfer Mechanisms
The Transfer Table dialog now allows non-blocking sizes to be specified as nb instead of the number of bytes to use for the buffer. If nb is used then the buffer size is made large enough so that the communication between processors is non-blocking. After scheduling the entry in the transfer table dialog looks like
nb:32768
Indicating that the nonblocking buffer size was determined to be 32768 bytes.
Atomic Parameter Updates from Command Program
When parameters are updated using appUpdateParams the parameter updates on a particular processor are now done atomically. Previously, when appUpdateParams was called if a box had multiple parameters being updated there was no guarantee that all of the parameters would change simultaneously.
Popup Menus
New Flow Graph Editor popup menus have been added. Clicking Button 3 on boxes or the canvas will bring up the popup menu item.
Command Line options -print, -land, and -all
New command line options have been added to support printing gedae flowgraphs from the gedae command line. The options are
-print: prints the flow graph specified in the -file option
-land: prints the file in landscape mode
-all: prints the flowgraph and all of its subgraphs
Examples:
gedae -file demo/comm/comm -print
gedae -file demo/bench1/bench1 -print -land -all
Version Control
Configuration management tools allow users to store versions of documents in a repository so that changes to a document or project can be monitored and managed. Gedae includes an interface to the CVS configuration management tool (see http://www.cvshome.org for more information) so that users may more easily monitor changes in their Gedae applications by storing in a repository four types of FGlibraries files: graphs, primitives, parameters, and group settings. CVS is a widely available and easy-to-use tool for controlling project files and documents. However, some users may need to use another configuration management tool, of which there are many to choose from. Because it is impossible to directly support all such tools, this CVS interface is built upon an Application Program Interface (API) so that the user may overwrite the inclusion of the CVS tool with menu items and commands better suited to their desired tool.
2 Bugs Fixed
The following bugs and problems have been fixed.
SCR1180: GSIM Executes Slowly on NT
The problem was that GSIM executed very slowly on NT processors. This was due to there being no implementation of Posix pthread_cond_wait and pthread_cond_signal functions. The solution was to replace our home-grown implementation of Posix threads with the pthreadVC.lib supplied by Redhat. This includes all of the mutex and cond_signal functions required to avoid busy waiting in the threads.
SCR1184: Printing of Flow Graphs Fails
When attempting to print flowgraphs an error would occur. This problem has been fixed.
3 Known Bugs
The following known bugs are listed by their Software Change Request (SCR) number. Please include the SCR number if you wish to report additional information about this bug.
SCR1016
Unterminated comment causes Gedae parser to segfault.
SCR1021
Arrays declared in a trigger box Local section aren’t allocated correctly.
SCR1022
Trigger boxes cannot have type long for inputs or outputs.
SCR1038
On NT Gedae uses 100% of the CPU even if idle.
SCR1097
The Gedae parser doesn’t handle an odd number of quotes (") well.
SCR1105
Changing launch package default file has no effect on default parameter values.
SCR1168
If a dynamic variable vector input is preceded by a vv_delay, then the graph segfaults during scheduling.
SCR1175
The File->Dump Trace Events to File menu option currently doesn’t work correctly. A segfault occurs when a filename is entered that begins with a “/”.
SCR1181
Users have reported that some graphs deadlock. It is unknown at this time if the problem is a Gedae problem or a problem with the graphs.
SCR1182
Some graphs that used to work with primitive boxes having dynamic inputs no longer work. The recommended work around is to use nondet inputs in the way described in the document “Migrating to Gedae 3.2”. Examples of boxes that use nondet inputs the correct way are the:
- embeddable/var_vector/s_vv
- embeddable/stream/logic/merge
SCR1183
Firing Granularity Table does not handle large graphs well when Show All Boxes is selected.
|
