MtDt Release Notes (New Features and Fixed Bugs) for all builds of V4.61

V4.61A New Features and Fixed Bugs (2011-Dec-09)

- Directing output to a log file (-q -lf5 options)  with the command line simulator was not working in most cases; it was going to stdout/stderr instead.  This has been corrected.

- When running an eTPU module (rather than an eTPU2 module), the scheduler could sometimes run in eTPU2 priority-passing disabled mode.  This seemed to happen more frequently under the command line version of the simulator, but could potentially happen with either tool.  This has been fixed and priority passing cannout be disabled when simulating the eTPU, only the eTPU2.

- During the generation of .EBV files (enhanced behavior verification) there was a chance that on internal buffer wrap a set of pin transition data would not be written out, thus causing a large gap in the saved out enhanced behavior verification data.  This has been corrected.  The workaround had been to resize the pin buffer using resize_pin_buffer() to a large enough size to avoid buffer wrap.

- Upon verification error, the simulator reports the script file name and line number of the verification script command that failed, however, it would not properly display this information if the error occurred in an included file.  This has been corrected.

- Certain DLL's that were required for the just-release command line version of the simulator were not being installed and for some customers this was preventing the (new and faster) command line version of the simulator from running.  This has been fixed.  (Note that many customers were not experiencing this issue because the DLL's get installed by many other commercial programs.)

- Added the ability to break on any thread in a channel using the new 'Complex Breakpoints' 'Active Channel' breakpoint feature.

- In certain cases use of the 'Mem Tool' was generating a spurious error that was crashing the simulator.

- When a script verification error is encountered, the correct script file name and line number are now being reported even when the verification error occurs in an included file to the main script.  Previously, only the top file and line fo the #include were reported.