Welcome to CW12 V3.1! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT NOTES: Without a license, the software runs in 1K-limited demo mode. If you would like to evaluate CodeWarrior Standard Edition or CodeWarrior Professional Edition, run the 'Register CodeWarrior' shortcut created by the installation script to get a 30-day free evaluation license. Send the file created to license@metrowerks.com (Americas, Asia), license_europe@metrowerks.com (Europe, Africa) or j-license@metrowerks.com (Japan). If you have any questions or comments/improvements, please contact us. We appreciate your input and are always looking for ways to improve the product. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It contains: - CodeWarrior for Motorola HC(S)12 (Special, Standard and Professional Edition) Browse the 'Release Notes' folder installed for more details. Ordering printed documentation: You can order paper copies of the user manuals through the Motorola Literature Distribution Center. For this, go to http://www.vervante.com/metrowerks Here is short list from what has been done from V3.0: - support for assembly include files for some (but not all) hc12 derivatives. The new wizard is using them if they are available. - revert changed bitfield behaviour for 16-bit bitfields. Please read the compiler release notes for details. - fix for browse information generation which was partially broken in V3.0. - includes more manuals in chm format. Especially the HC12 compiler and HC12 assembler are now in this searchable format too. - The ICD12 Target Interface for P&E Microcomputer Systems BDM cables supports now the CYCLONE PRO, "Automated Programmer And Debug Interface". Also flash programming download speed has been improved for this interface. - The SofTec support has been updated to support the PK-HCS12 Series Starter kits. This support is available through SofTec Microsystems Hardware Debugging connection in the Wizard. By default inDART-HCS12 Hardware Model is selected. The user must select the correct Hardware Model when using the PK-HCS12 Series through the MCU Configuration dialog. - updated prm and library files for existing derivatives. - Added Full Chip Simulation (FCS) for MC9S12A128B and MC9S12A256B derivatives. Here is short list from what has been done from V2.0: - all tools updated to latest version - IDE 5.5 with Processor Expert running in its own project tab - IDE 5.5 with docking windows - Full-Chip Simulation for most HCS12 devices - New Project Wizard to create new projects - postlinker and prelinker plugins - Stationery wizard: menu File > New and then 'HC(S)12 New Project Wizard. It asks you a few questions and creates a tailored project according to the answers. Try it! - new standard monitor for HCS12 (debugging S12 devices using serial cable) - SofTec inDART support for HCS12 devices - P&E BDM Multilink USB support for HCS12 devices - on-chip DBG module including trace for new HCS12 devices (e.g. E128) - The HC12 parts (compiler, assembler, debugger) has an increased license version number. The license file for HC12 V2.0 will not work in all parts for this V3.0 release. You need a HC12 V3.0 license or an updated license file. - updated prm and library files for existing and new derivatives - updated debugger/simulator files - new visualization tool in the debugger supporting additional instruments/properties - updated online documentation with extended search capabilities (IDE menu Help > CodeWarrior Help) - new Burner utility to support path suppression in the S0 record - updated ClearCase version control plugin - added COM/Scripting interface to the simulator/debugger Known Issues: - Devices with the DBG module on-chip feature (Trigger Module Settings): With a BDM host target interface, "Memory access inside Address A - Address B range" will not cover the $FF00-$FFFF range. - When converting a Processor Expert project from HC12 V2.0 to HC12 V3.1, the PE panels (Environment options and Project options) do not show up. In order to correct this, open the "Target Settings" panel and set the "Pre-Linker" to "PE Options", this results in the missing two PE panels appearing. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Compatibility with CW12 V2.0 projects (derivative library files) Derivative library files have been consistently improved and are available in CW12 V3.1. They also use a new naming convention based on the derivative name: mc9s12.h/.c/.prm When porting your CW12 V2.0 project to CW12 V3.1, you may choose between the two following options: 1- Upgrade to the new derivative files (recommended) Select the "Files" tab in your project and remove the derivative files (usually in the "Libs" group) currently in use. Add the new derivative files into the same group of files (mc9s12.h and mc9s12.c). You may also remove and replace the prm file (linker.prm) in the "Prm" group with the one matching your derivative. These files are located in "\HC12c\lib\include", "\HC12c\lib\src" and "\HC12c\lib\prm" folders respectively. Note: References to the old file names will need to be changed in any source files in which the appear. 2- keep using the CW12 V2.0 derivative files For compatibility, the derivative header files provided with CW12 V2.0 and CW12 V3.0 are still provided with this new release.However they are no longer in the default access path as they were moved into a new directory "\lib\HC12c\old\v2.0". In order to successfully build your project within CW12 V3.1, this path must be added to your project. Open the project settings (ALT + F7) and select the "Access Paths" panel. Click the "System Paths" radio button and click the "Add..." button. Browse to the "lib\HC12c\old\v2.0" folder of your installation using "Compiler Relative" path type and validate with the "OK" button. You should see the new path displayed: "{Compiler}lib\HC12c\old\v2.0". Click the "OK" button of the project settings to validate and close the project settings window. Make your project, it is now using the same CW12 V2.0 derivative files. Hint: In order to adapt multiple projects, you can use the keyboard shortcuts for copy (CTRL-C) and paste (CTRL-V) to copy paths in the "Access Paths" panel. Drag and drop across multiple open "Access Paths" panels is also supported by the ide. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Docked vs MDI Child window modes for project windows By Default, the project windows are in Docked window mode. If you want to switch to MDI Child window mode, go to the bin\Plugins\Support\DefaultLocations directory of your installation and rename the file IDEDefaultLocation.mdi to IDEDefaultLocation.xml. The next time the CodeWarrior IDE is started all new projects will use the MDI Child window mode. For existing projects, you have to make sure to delete the Data folder before opening them, otherwise they will still use the Docked window mode. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! List of fixed bugs: - MTWX10118, MTWX10435, MTWX10702, MTWX11032, MTWX4120, MTWX4423, MTWX6939, MTWX7470, MTWX8628, - MTWX9228, MTWX9634, MTWX9688, MTWX9718. Contacting us: We welcome and encourage comments. You can contact us directly by sending e-mail to support@metrowerks.com or support_europe@metrowerks.com. Drop us a line to let us know how we're doing. We'll listen and we'll act. Visit our product page at: Metrowerks