Table of Contents
MC-3020 3.2 provides minor bug fixes and visible trace changes for BridgePoint Model Debugger.
This document has been divided into the following sections for easier reference.
Support resources available for DesignPoint™ and BridgePoint™ products and MC-3020 specifically. (BridgePoint™ and DesignPoint™ are registered trademarks of Project Technology, Inc.)
World class support is provided for the BridgePoint and DesignPoint products. Support is available via the web, email, telephone, and fax. Each of the support options is described at our support web address: Project Technology Support.
The Project Technology, Inc. web site is available 24 hours a day, 7 days a week. You can access the following features at the Project Technology Customer Service web site by clicking on the "Customers Only" icon.
Use a pre-defined form to submit a problem report and be assured you are providing enough information for our support technicians to help you. The information that you provide on this form is emailed to our support organization at <[email protected]>.
Submit your enhancement ideas directly from your workstation as you think of them. This information will be immediately entered in our enhancements database for consideration in future releases. Your ideas drive our product development ONLY when we hear them.
Read technical tips that will help you get more out of your Project Technology software products. New tips will be posted on a regular basis and old tips will be archived for your easy reference.
Read technical papers that treat topics of interest in depth. Many are written by Project Technology developers, instructors, and consultants, but we encourage you to submit your own contributions.
We have extended our popular users' mailing list service by adding a list for BridgePoint users. This mailing list allows you to communicate with a community of BridgePoint users, who are solving many of the same problems you encounter each day. You'll have to sign-up for this service.
The "Customers Only" section utilizes authentication technology to limit this service to Project Technology, Inc. customers who have support contracts.
To access this area, you will need your Project Technology Customer ID and your web site password. You'll find your Customer ID on packing lists and/or invoices you have received from us. Your initial password is the first eight characters (or all, if eight or fewer) of the name of the city your product was shipped to, capitalized appropriately, with spaces compressed out.
Project Technology, Inc. is your first stop for customer support. If what you need is not available there, the web site of ROX Software, Inc. has additional support material. Visit ROX Software, Inc. This site contains sample models, generated code and an online version of the MC-3020 Users Guide. All of the most recent and up-to-date material is found at this web site.
The customer support email address is <[email protected]>. This is the preferred method for non-critical questions.
Customers within the US can call our toll-free number, 800-482-3853. The direct line, which can be used by US and International customers is +1-520-544-0808.
MC-3020 translation runs on all platforms supported by BridgePoint. See your BridgePoint release notes for details on versions of the operating systems. The list includes Solaris and Windows XP/2000/NT/98SE/ME. (Windows 98 is no longer recommended.)
Targets for running the translated models include almost any platform with an ANSI compliant C compiler. Compilers known to work include:
gcc (which supports Linux, Windows, Mac, H8 and many, many microprocessors)
Microsoft Visual C/C++ (Visual Studio)
Texas Instruments TI470 C
Sparcworks Workshop
Tasking 8051, C167 and others
Borland C/C++
Yellowsoft for H8
Cosmic
others
MC-3020 3.2 provides bug fixes to allow smoother tracing within BridgePoint Model Debugger.
MC-3020 3.2 is being delivered as a zip file containing the changed files. Follow these steps to upgrade your installation from 3.1 to 3.2.
Open a Cygwin (bash) shell.
Change directory to the root of your MC-3020 installation (as defined in $ROX_MC_ROOT_DIR).
Copy the delivered zip file into the installation directory contained in the environment variable $ROX_MC_ROOT_DIR.
Unzip the file. (unzip 3020320XXXXXXXX.zip)
MC-3020 has been modified to support a greater number of enumerators expressed in the "old style" (pre-BridgePoint 6.0). This support was requested by customers upgrading from older versions of BridgePoint Model Builder and MC-3020. It is recommended that all new enumerations use the new support provided in BridgePoint Model Builder version 6.0 and beyond.
MC-3020 3.2 supports up to 512 elements in an "old style" enumeration.
Event packaging and some routines used for UML debugging did not adhere strictly the C++ specification when defining static and external storage. This caused missing externals during the link process.
This problem is fixed.
For testing within BridgePoint Model Verifier, specification of OAL is supported in outgoing bridge descriptions. This allows "stubbing out" of domains during testing. MC-3020 supports translation of these bridge descriptions as an extension to the Model Verifier testing.
MC-3020 version 3.1 did not scan the OAL defined in these bridge descriptions for class creation and linking statements and then optimized out the CREATE and LINK accessors. This was observed as missing externals during the link process.
This problem is fixed. OAL defined in bridge descriptions is now scanned for create and link actions. Associated accessor code is generated if needed.
Examples for TagInitializationFunction and TagFunctionTranslationOff were not included in the domain.clr delivered with MC-3020 3.1.
This problem is fixed. The required examples are now provided.
The TagPEIsDefinedInData, TagStaticInstancePopulation and TagReadOnly coloring functions did not work correctly when coloring all classes in a specific subsystem.
This problem is fixed. The tagging interface now operates correctly.
In MC-3020 3.1, the debugger stopped at the beginning of state actions rather than at the end. This made it difficult to see which instance events were being generated and dispatched from the event queues.
This problem is fixed. In MC-3020 3.2, the state action stepping pauses at the end of each state action. This allows viewing of events generated within the current state action.
This is an issue very similar to that above and is fixed in the same way.
This problem is fixed. In MC-3020 3.2, the state action stepping pauses at the end of each state action. This allows viewing of events generated within the current state action.
In MC-3020 3.1, assigner state models did not report the starting and ending of state actions correctly. This caused class-based (assigner) events to accumulate on the displayed queues. The events and state actions were being correctly dispatched, but missing synchronization with the debugger caused assigner events to not be cleared from the display.
This problem is fixed. Assigner state models now properly communicate their dispositions.