Easy development software from the company that knows MCU
Contents
1. MCUez Installation and Configuration User s Manual MCUEZINS D Rev 2 My MOTOROLA MCUEZINS D MCUez Installation and Configuration User s Manual Mj MOTOROLA Users Manual Important Notice to Users While every effort has been made to ensure the accuracy of all information in this document Motorola assumes no liability to any party for any loss or damage caused by errors or omissions or by statements of any kind in this document its updates supplements or special editions whether such errors are omissions or statements resulting from negligence accident or any other cause Motorola further assumes no liability arising out of the application or use of any information product or system described herein nor any liability for incidental or consequential damages arising from the use of this document Motorola disclaims all warranties regarding the information contained herein whether expressed implied or statutory including implied warranties of merchantability or fitness for a particular purpose Motorola makes no representation that the interconnection of products in the manner described herein will not infringe on existing or future patent rights nor do the descriptions contained herein imply the granting or license to make use or sell equipment constructed in accordance with this description The computer program contains material copyrighted by Motorola Inc first published in 1997 and may be used only under2. 1 Contents Fe DD OHIO 424 ior Ee ERC RUP S debe eire beds 15 23 A ee Re PRA RR cM x 16 2 2 CD Installation 1 Insert the CD into the CD drive Select Run from the Windows 95 Windows NT Start menu 2 3 Enter CD drive letter and setup program for example D SETUP 4 Follow the instructions displayed on the monitor During installation the system prompts the user to select one MCU target Select one target per installation NOTE MCUez software and manuals can be downloaded from Motorola s website at http www mcu motsps com mcuez MCUez Installation and Configuration User s Manual MOTOROLA MCUez Installation 15 MCUez Installation 2 3 MCUez Directory User s Manual After installation these subdirectories are created in the directory where the MCUez is installed MCUez MCUez Demo HCXX MCUez Docs MCUez PROG MCUez PROG FPP MCUez PROG MEM MCUezNPROGNREG Root directory for default installation Subdirectory for specific MCU Family XX defines the MCU release level HC05 HC08 or HC12 The DEMO subdirectories contain sample programs that can be used to explore most of the features of the MCUez system Each debugger or emulator creates its own subdirectory within this directory with programs configured for the selected target Contains the user manuals in pdf format Subdirectory that contains the MCUez programs shell assembler linker and debugger Contains MCU
3. 4 8 Editor Configuration Tor Wotd 4 26 2 400s0 80s 00464 oon 42 MCUez Installation and Configuration User s Manual MOTOROLA List of Figures 9 List of Figures User s Manual MCUez Installation and Configuration 10 List of Figures MOTOROLA User s Manual MCUez Installation and Configuration 1 1 Contents 1 2 Introduction Section 1 General Information L2 In rodUcllO0 6 sa 69 69 a R RRPXGU RS RR AR RA R RA A A AR RR A 11 L3 Document Conventions 0000s eee ce ah 12 LXI Typographic Styles in This Manual lesse 12 1 3 2 Extended Backus Naur Form 13 1 3 3 Precis Foiano aa ee 13 A Sye Rails esso enaren E pisa s 13 Motorola s MCUez is an integrated development environment which includes these tools MCUez Shell A 32 bit application that serves as a configuration tool to manage MCUez projects The MCUez Shell uses a graphical interface to create new projects or modify the environment for existing projects MCUez assembler A 32 bit application that translates an assembly file into native code for the target processor The assembler supports absolute and relocatable assembly code and generates a Motorola S file for absolute assembly The MCUez assembler uses a graphical interface to select the assembly file set up options and provide on line help The input syntax for the assembler conforms to the Motorola assembly language input standard The output object code form
4. a license such as the License For Computer Programs Article 14 contained in Motorola s Terms and Conditions of Sale Rev 1 79 Trademarks This document includes these trademarks MCUez is a trademark of Motorola Inc Windows Windows 95 Windows NT and Microsoft Word are registered trademarks of Microsoft Corporation in the U S and other countries WinEdit is a trademark of Wilson WindowWare Motorola Inc and HIWARE AG 1999 All Rights Reserved User s Manual MCUez HC12 Debugger 4 MOTOROLA User s Manual MCUez Installation and Configuration List of Sections Section 1 General Information ethene rom 11 Section 2 MCUez Installation 15 Section 3 MCUez Shell 17 Section 4 MCUez Environment 31 MCUez Installation and Configuration User s Manual MOTOROLA List of Sections 5 List of Sections User s Manual MCUez Installation and Configuration 6 List of Sections MOTOROLA User s Manual MCUez Installation and Configuration Table of Contents Section 1 General Information li DE l PLC EMT 11 1 2 esea Te uiu ouo Lodo ases So apatia 11 1 3 Document Conventos ie iui LE UT 12 1 3 1 Typographic Styles in This Manual 00 12 1 3 2 Extended Backus Naur Form 0 eee 13 1 3 3 Executable Files s iso rela tx eE ANN GAE 13 14 Syse Rogultetuslls 2ocsocuaceasdashs tad ipanen As aS CES 13 Section 2 MC
5. the Editor drop down box 4 In the Executable edit box enter the Motpad executable file including path Use the Browse button to search for the executable file if necessary 5 The Options edit box contains options used for error feedback in the MCUez assembler and linker After Motpad is selected the shell automatically enters the appropriate options Figure 4 5 shows a typical Motpad configuration Current Configuration x Project Editor Tools Paths Additional Editor Mpa 1l Project File D S Executable C MCUEZ Prog Motpad EXE n x x Options The options set in the above Edit box are passed to MCUez tools to set parameters when calling the editor Figure 4 5 Editor Configuration for Motpad MCUez Installation and Configuration User s Manual MOTOROLA MCUez Environment 39 MCUez Environment 6 Click OK to close the dialog 7 Motpad is set as the default project editor and the associated icon is displayed in the MCUez toolbar 4 7 Configuring Notepad To define Notepad as the project editor 1 Start the MCUez Shell 2 Click the ezMCU icon in the toolbar to open the Configuration dialog box 3 Select the Change button in the Configuration dialog box to open the Current Configuration dialog box 4 Selectthe Editor tab and select Notepad from the Editor drop down box 5 In the Executable edit box enter the Notepad executable file including pat
6. the appropriate options Figure 4 8 shows a typical Word configuration Project Editor Tools Paths Additional E ditor Word Executable c MSOFFICE 32 Winword Winword exe Browse Options f Figure 4 8 Editor Configuration for Word 7 Click OK to close the dialog 8 Word is set as the default project editor and the associated icon is displayed in the MCUez toolbar User s Manual MCUez Installation and Configuration 42 MCUez Environment MOTOROLA Technical support for MCUez development tools is available through your regional Motorola office or by contacting Motorola Inc 6501 William Cannon Drive West MD 0E17 Austin Texas 78735 Phone 800 521 6274 Fax 602 437 1858 CRC CRC email sps mot com Motorola reserves the right to make changes without further notice to any products herein Motorola makes no warranty representation or guarantee regarding the suitability of its products for any particular purpose nor does Motorola assume any liability arising out of the application or use of any prod uct or circuit and specifically disclaims any and all liability including without limitation consequential or incidental damages Typical parameters which may be provided in Motorola data sheets and or specifications can and do vary in different applications and actual performance may vary over time All operating parameters including Typicals must be validated for each customer applic
7. STEM MENU MCUTOOLS INI WPJ OR PJT PROJECT INI WORKINGDIRECTORY mr INFORMATION WORKDIR cec TORY Winko ORA FOR MCUEZ CODEWRIGHT PROGRAMS OPTIONS CONFIGURATION EXECUTABLE DEFAULTDIR FILE PATHS LAYOUTS SHELL PROJECT PARAMETERS Figure 3 1 MCUez Shell 3 3 Executing the Shell Double click on the MCUez Shell icon in the MCUez program group or select Start Programs MCUez MCUez Shell from the Windows task bar The toolbar contains icons for related applications delivered with the MCUez package It also contains icons for tools specified during project configuration which is described in 3 6 Defining or Redefining a Project User s Manual MCUez Installation and Configuration 18 MCUez Shell MOTOROLA MCUez Shell Project Selection 3 4 Project Selection Click on the MCUez Shell system menu to display the list of available projects Figure 3 2 illustrates that projects for all MCU targets were loaded during installation User defined projects also will be listed in this menu SYSTEM MENU gt STROSS ET em Eem em em mcu ASM DEBUG LINK MCUez Shell ie xi Restore Move Size Minimize Mezze Close Alt F4 About Application General Help C MCUEZ DEMO4HCO5 C AMCUE2 DEMO HCO8 C MCUEZ DEMOSHC12 PROJECTS Figure 3 2 List of Projects The user should select a project from the list associated with the MCU for the development enviro
8. Uez Installation 2 1 ID ROT T EEEE S E A EES EEE ARR E A EE T EEE A S T 15 2 2 LL Install ure oe eq rer AN Sob eae Rta eee weds e 13 23 II PPP 16 Section 3 MCUez Shell 3 1 GU as ca died ax Lina badedas agri 17 3 4 osse i PRETI 18 3 3 Execute ihe Sell ua cies bake d h FED HE CER ERRR Y dE A RA acd dd 18 3 4 Mets ee a 4 Ea Kb PRX AER P 19 3 9 Propet Connan ce kad hahaa sew baie ia ai 20 dos We duo Dc T rrm 21 i Bee Opine A oa eua um E b Ite o 9 E o3 ex da 23 3 9 3 Changing Project Environment snaran nnne 24 MCUez Installation and Configuration User s Manual MOTOROLA Table of Contents 7 Table of Contents User s Manual 3 6 3 6 1 35 2 4 5 3 3 6 4 3 53 4 1 4 2 4 3 4 3 1 4 4 4 4 1 4 4 2 4 4 3 4 4 4 4 5 4 5 1 4 5 2 4 5 3 4 6 4 7 4 8 4 9 Defining or Redetuus a Project i e 24 linea A LEN ELIA 24 DIL siii cetacei 25 jo Wo mec T TTC Kr ETE ZT E tear EIE ERU ES QUA VES canes dq doi e E Sc ea 28 MIE 29 Section 4 MCUez Environment CON NM 31 Da E DOO era GERE ET 32 sane Path Parameters sods cos etsnei soe d titiri E HORE ened 32 o 33 Conheunne WinEdit scesi A aaa 33 Configuring WINEDIT INL 26cic6cceucaeernessacenavunsss da Storing and Restoring Configuration Files 23 WinEdit Menu Selection gt 00 b RE RR T R diari KR T ES 35 Wea N iiber rsRORRRASERCAR ERA RES ERRARE E 36 Configuring COREROABDE ci
9. at conforms to the ELF DWARF 2 0 object code format MCUez Installation and Configuration User s Manual MOTOROLA General Information 11 General Information MCUez linker Merges all objects of an application into one absolute abs file The absolute file contains absolute unrelocatable code that can be loaded to a target using the MCUez debugger The linker also generates a Motorola S file that can be burned into an EPROM MCUez debugger Used for emulation or cross debugging of an embedded application for a specific hardware design The MCUez debugger incorporates a powerful graphical interface and command line that enable the user to debug assembly files correlate them with the data manipulate register content and read and manipulate memory content Additional features include Unlimited memory data etc windows selection for debug Drag and drop from one window to another for a different view Displays procedure chain and function parameters Displays function local variables and parameters in varying formats Performs stepping at source and assembly levels 1 3 Document Conventions This section describes styles and terms used throughout this manual 1 3 1 Typographic Styles in This Manual This list identifies typographic styles used in this manual to define notational conventions Bold face type is used for literal strings that must be used exactly as shown in the example and for
10. ation by customer s technical experts Motorola does not convey any license under its patent rights nor the rights of others Motorola products are not designed intended or authorized for use as components in systems intended for surgical implant into the body or other applications intended to support or sustain life or for any other application in which the failure of the Motorola product could create a situation where personal injury or death may occur Should Buyer purchase or use Motorola products for any such unin tended or unauthorized application Buyer shall indemnify and hold Motorola and its officers employees subsidiaries affiliates and distributors harmless against all claims costs damages and expenses and reasonable attorney fees arising out of directly or indirectly any claim of personal injury or death as sociated with such unintended or unauthorized use even if such claim alleges that Motorola was negligent regarding the design or manufacture of the part Motorola and amp are registered trademarks of Motorola Inc Motorola Inc is an Equal Opportunity Affirmative Action Employer How to reach us USA EUROPE Locations Not Listed Motorola Literature Distribution P O Box 5405 Denver Colorado 80217 1 800 441 2447 or 1 303 675 2140 Customer Focus Center 1 800 521 6274 JAPAN Motorola Japan Ltd SPD Strategic Planning Office 141 4 32 1 Nishi Gotanda Shinagawa ku Tokyo Japan 03 5487 8488 ASIA PACIFIC Mot
11. bug command line The shell automatically links the MCUez debugger program to this entry Select Project Execute to start the tool specified in the Execute command line The shell automatically links the program associated with the Decoder tool to this entry 4 4 4 WinEdit Toolbar Figure 4 2 shows the association between the command lines in the Project Configuration dialog and buttons in the toolbar pii E x FEN Sm COMPILE MAKE REBUILD DEBUG EXECUTE COMMAND COMMAND COMMAND COMMAND COMMAND Figure 4 2 WinEdit Toolbar 4 5 Configuring Codewright Follow these steps to configure Codewright The MCUez Shell automatically creates the project file required by Codewright Click the ezMCU icon on the toolbar to start the MCUez Shell 2 Click the Change button in the Configuration dialog box to open the Current Configuration dialog box 3 Select the Editor tab and select Codewright from the Editor drop down box 4 Inthe Project File edit box enter a name for the Codewright project file Usually Codewright project files have a pjt extension Do not specify a path in front of the filename 5 Inthe Executable edit box enter the Codewright executable file including path Use the Browse button to search for the executable file if necessary User s Manual MCUez Installation and Configuration 36 MCUez Environment MOTOROLA MCUez Environment Configuring Codewright 6 The Options edit box contains option
12. c DirectoryName Example Q ENPATH C PROJECTS TESTS D PROJECTS TESTS GENPATH C PROJECTS TESTS If a directory name is preceded by an asterisk the MCUez program recursively searches the directory tree for a file not just the given directory Directories are searched in the order they appear in the path list When using WinEdit or Codewright if the system environment variable DEFAULTDIR is set ensure that this variable is assigned the project directory specified in the WinEdit or Codewright project configuration If the specified directories differ files may be placed in the wrong directory This could affect proper execution of the MCUez application 4 4 Configuring WinEdit Follow these steps to configure WinEdit The MCUez Shell automatically creates the editor project file required by WinEdit Click the ezMCU icon on the toolbar to start the MCUez Shell 2 Click the Change button in the Configuration dialog box to open the Current Configuration dialog box 3 Selectthe Editor tab and select WinEdit from the Editor drop down box 4 Inthe Project File edit box enter a name for the WinEdit project file WinEdit project files have a wpj extension Do not specify a path in front of the filename 5 Inthe Executable edit box enter the WinEdit executable file including path Use the Browse button to search for the executable file if necessary MCUez Installation and C
13. dependent FLASH parameter files that handle internal FLASH modules The MEM subdirectory contains memory files used to allocate memory maps for the HC05 HC08 and HC12 The REG subdirectory contains register files for various devices that are emulated through the MCUez debugger command line and used to view input output I O devices and memory register information MCUez Installation and Configuration 16 MCUez Installation MOTOROLA User s Manual MCUez Installation and Configuration 3 1 Contents Section 3 MCUez Shell 3 2 st iii a A e E E E E EE A E EN 18 da EE Pe OR EE ET 18 3 4 I a o pl AG ee eR EUR ole EO OR OE ORE RU HUN 19 a Project Conii IA zed ee RR E ERE reer NR ere oer 20 33 1 Hu od CCP T 21 EE M RIE a gt PPP PE 23 VR Changing Project Environment oo a GoCERGPCAOI ACER RERCER OR OK 24 3 6 Deining or Redefining B Piedi gt 4 0 6 esses ebd dde d deca 24 3 6 1 luc o Wl 24 3 6 2 Ss Xp TC ec 25 3 6 3 Tools K T TTE 27 3 6 4 FAI ETE dE s ETE ER T bi EIER Edd 4d i EE RARE SEA 28 3 0 5 PN VA PARRA E 29 MCUez Installation and Configuration User s Manual MOTOROLA MCUez Shell 17 MCUez Shell 3 2 Introduction The MCUez Shell delivered with the MCUez package configures the project environment and provides a toolbar to launch related applications Figure 3 1 lists the different configuration files handled by the shell TOOLBAR MCUez Shell MCUEZ SHELL SY
14. ect environment are explained in 3 6 Defining or Redefining a Project 3 6 Defining or Redefining a Project 3 6 1 Project Tab User s Manual Each project can have its own parameters Define all tools and parameters associated with a project in the New Configuration or Current Configuration dialog box From the main Configuration dialog box click New to create a new configuration or Change to edit the current project Refer to Figure 3 5 for an example of the project tab in the Configuration dialog box Define the name of the project in the Project Name edit box This name will be displayed in the main Configuration dialog box Check Enforce Project Directory to define the project directory as the default directory Leave this option unchecked to define the project directory as the temporary working directory Enforcing the project directory also enables MCUez tools to be started from the desktop or Windows Explorer MCUez Installation and Configuration 24 MCUez Shell MOTOROLA MCUez Shell Defining or Redefining a Project 3 6 2 Editor Tab Set the project editor to be used with the application source files in the Editor tab as shown in Figure 3 7 Current Configuration x Project Editor Tools Paths Additional Editor Motpad Y Project Files Executable CAM CUEZR2 Prog Motpad EXE Options The options set in the above Edit box are passed to MCUez tools to set parameters when calling the edit
15. ewright The Make command is used only when the C compiler has been installed If the C compiler has not been installed the assembler will be invoked and the Make command will be inactive 4 3 Setting Path Parameters User s Manual Various parameters of the MCUez environment are set by environment variables No blanks are allowed in an environment variable definition The syntax is KeyName ParameterDefinition Example GENPATH D PROJECTS TESTS Methods of defining parameters e Use system environment variables supported by the operating system e Put definitions in a file called default env in the default directory Put definitions in the file specified in the system environment variable named ENVIRONMENT The default directory can be set with the DEFAULTDIR system environment variable When searching for an environment variable all MCUez programs search the system environment then the default env file and finally the global environment file given by ENVIRONMENT If no definition is found a default value is assigned MCUez Installation and Configuration 32 MCUez Environment MOTOROLA 4 3 1 Paths NOTE MCUez Environment Configuring WinEdit Most environment variables contain path lists that indicate where to look for files A path list is a list of directory names separated by semicolons or a directory name preceeded by an asterick and follows this syntax DirSpec DirSpe
16. h Use the Browse button to search for the executable file if necessary 6 The Options edit box contains options used for error feedback in the MCUez assembler and linker After selecting Notepad the shell automatically enters the appropriate options Figure 4 6 shows a typical Notepad configuration Project Editor Toots Paths Additional Editor Notepad E ile Executable C SWINDOWS Notepad exe Browse Options g Figure 4 6 Editor Configuration for Notepad 7 Click OK to close the dialog 8 Notepad is set as the default project editor and the associated icon is displayed in the MCUez toolbar User s Manual MCUez Installation and Configuration 40 MCUez Environment MOTOROLA MCUez Environment Configuring Wordpad 4 8 Configuring Wordpad The MCUez assembler and linker cannot process input files containing Wordpad format information Save all source files as ASCII text files To define Wordpad as the project editor 1 Start the MCUez Shell 2 Click on the ezMCU icon in the toolbar to open the Configuration dialog box 3 Selectthe Change button in the Configuration dialog box to open the Current Configuration dialog box 4 Select the Editor tab and select Wordpad from the Editor drop down box 5 Inthe Executable edit box enter the Wordpad executable file including path Use the Browse button to search for the executable file if necessary 6 The Options edit box contains opti
17. itor Editor Project File Editor configuration file for instance project wpj MCUez Installation and Configuration 20 MCUez Shell MOTOROLA MCUez Shell Project Configuration 3 5 1 New Project To start a new project follow these steps 1 Click New in the Configuration dialog box to define a new project directory 2 Create a new project by selecting the Empty radio button 3 Select From Current Project to use configuration settings from the previously opened project for the new project 4 Enter the directory path or browse to the directory as shown in Figure 3 4 5 Click OK and the New Configuration dialog box will appear 6 Set project parameters starting with the Project Name as shown in Figure 3 5 Directory DM CUez MYPROJECTSHC14 Browse Create From Current Project C Empty Cancel Help Figure 3 4 Defining a New Project MCUez Installation and Configuration User s Manual MOTOROLA MCUez Shell 21 MCUez Shell New Configuration xi Project Editor Tools Paths Additional Project Name Enforce Project Directory Info when you check the Enforce Project Directory other existing projects on your computer will be set with the current project directory defined in the Configuration dialog Cancel Help Figure 3 5 New Configuration Dialog Box Refer to 3 6 Defining or Redefining a Project for information abo
18. le is created in the project directory and the associated icon is displayed in the MCUez toolbar 4 4 1 Configuring WINEDIT INI WinEdit looks for a file named EDOUT to retrieve information about errors or warnings detected during assembly linking or debugging To ensure that the appropriate file is used initialize the OUTPUT variable in the WinEdit section of the winedit ini file WinEdit OUTPUT NEDOUT 4 4 2 Storing and Restoring Configuration Files After starting WinEdit select Configure from the Project menu to open the Project Management dialog box e Select Save to save the current configuration e Select Open to load a previously saved configuration NOTE Each time the working directory is changed WinEdit must be closed and restarted 4 4 3 WinEdit Menu Selection Select Project Compile to execute the tool specified in the Compile command line The MCUez Shell automatically links the MCUez assembler program to this entry Select Project Make to execute the tool specified in the Make command line The MCUez Shell automatically links the maker program to this entry Select Project Rebuild to execute the tool specified in the Rebuild command line The MCUez Shell automatically links the MCUez linker program to this entry MCUez Installation and Configuration User s Manual MOTOROLA MCUez Environment 35 MCUez Environment Select Project Debug to start the tool specified in the De
19. nment The current project directory will change to the directory containing the selected project The project ini and default env files residing in the selected project directory are maintained by the project Configuration dialog box and used to reconfigure the environment MCUez Installation and Configuration User s Manual MOTOROLA MCUez Shell 19 MCUez Shell 3 5 Project Configuration Click on the first icon in the toolbar to create a new project open an mcu existing project or change environment settings for a project The Configuration dialog will appear as shown in Figure 3 3 Configuration r Current Configuration Project Name MCUez for HC08 Project Directory D motorolaprojecthmcuez amp DE MD hc 8 Enforce Project Directory No Environment File DEFALILT ENV E ditor Motpad Editor Project File New Open Change Cancel Help Figure 3 3 Current Configuration Window The project configuration displays this information User s Manual Project Name User defined project name usually denotes target Project Directory User defined working directory where source files are located Enforce Project Directory Indicates whether the current project directory will be the working directory for all projects or not Environment File Contains environment variables defined by using the Configuration dialog boxes Editor User assigned project ed
20. on but the executable does not contain an f icon the default icon shown to the left is set in the toolbar 3 6 4 Paths Tab Working paths for defined tools are set in the Paths tab as shown in Figure 3 11 Current Configuration x Project Editor Tools Paths Additional Configure SETZE lela Browse Figure 3 11 Setting Paths for Tools Click on the Configure combo box to view the list of paths as in Figure 3 12 User s Manual MCUez Installation and Configuration 28 MCUez Shell MOTOROLA MCUez Shell Defining or Redefining a Project Object General Path Library Object Text Figure 3 12 List of Paths During installation MCUez automatically sets up these paths If the project requires specific paths select an option from the combo box and enter the path or paths in the edit box Click the browse button to help find the path Paths defined here are valid only for MCUez tools or other user assigned tools 3 6 5 Additional Tab Use the Additional tab to set additional parameters for tools These parameters are saved in the default env file Figure 3 13 is an example of setting additional parameters Current Configuration Ea Figure 3 13 Setting Additional Tool Parameters NOTE Lines stored in a default file default env project wpj or pjt file are limited to 1024 characters MCUez Installation and Configuration User s Manual MOTOROLA MCUez Shell 29 MCUe
21. onfiguration User s Manual MOTOROLA MCUez Environment 33 MCUez Environment 6 The Options edit box contains options used for error feedback in the MCUez assembler and linker After selecting WinEdit the shell automatically enters the appropriate options NOTE WinEdit version 3 1 or lower cannot be started with a line number l as a parameter For older versions of WinEdit options should be changed to f only Current Configuration x Project Editor Tools Paths Additional Editor Win dit Project File demo wpi Executable C Program Files winE dit exe Browse Options a Mil The options set in the above Edit box are passed to MCUez tools to set parameters when calling the editor Figure 4 1 Editor Configuration for WinEdit 7 Select the Tools tab 8 Some tools specified here are automatically associated with WinEdit commands menu entries and buttons ASSEMBLER is automatically associated with the WinEdit Compile command MAKER is associated with the WinEdit Make command LINKER is associated with the WinEdit Rebuild command DEBUGGER is associated with the WinEdit Debug command DECODER is associated with the WinEdit Execute command User s Manual MCUez Installation and Configuration 34 MCUez Environment MOTOROLA MCUez Environment Configuring WinEdit 9 Click OK to close the Current Configuration dialog 10 The specified editor project fi
22. ons used for error feedback in the MCUez assembler and linker After selecting Wordpad the shell automatically enters the appropriate options Figure 4 7 shows a typical Wordpad configuration Project Editor Tools Paths Additional Editor Wordpad Project lt Executable C Program Files Windows NT Accessories wordpa Options a Figure 4 7 Editor Configuration for Wordpad 7 Click OK to close the dialog 8 Wordpadis set as the default project editor and the associated icon is displayed in the MCUez toolbar MCUez Installation and Configuration User s Manual MOTOROLA MCUez Environment 41 MCUez Environment 4 9 Configuring Word The MCUez assembler and linker cannot process input files containing Word format information Save all source files as ASCII text files To define Microsoft Word as the project editor 1 Start the MCUez Shell 2 Click on the ezMCU icon in the toolbar to open the Configuration dialog box 3 Selectthe Change button in the Configuration dialog box to open the Current Configuration dialog box 4 Select the Editor tab and select Word from the Editor drop down box 5 Inthe Executable edit box enter the Word executable file including path Use the Browse button to search for the executable file if necessary 6 The Options edit box contains options used for error feedback in the MCUez assembler and linker After selecting Word the shell automatically enters
23. or OK Cancel Help Figure 3 7 Setting the Editor Editor In the Editor combo box select an editor such as Motpad WinEdit Codewright Notepad or Wordpad Select Others to specify another editor Figure 3 8 Editor Combo Box MCUez Installation and Configuration User s Manual MOTOROLA MCUez Shell 25 MCUez Shell User s Manual NOTE Project File Enter the name of the associated editor project file if applicable that contains the editor settings The MCUez Shell automatically generates the appropriate project files for WinEdit and Codewright If WinEdit is selected a wpj file must be associated with the editor If Codewright is selected a pjt file must be associated with the editor Executable sx In the Executable field enter the path to the editor executable file An icon associated with the editor will appear in the MCUez Shell toolbar If the editor path is not valid the icon shown to the left appears in the toolbar Options Define editor options in the Options edit box These options are saved in the editor s project file and appended to the editor command line when the editor is executed Consult the appropriate editor manual for available options For most editors the f option identifies the source file containing an error The l option identifies the line number where an error occurred When an error message in the assembler or linker is double clicked the f and l op
24. orola Semiconductors H K Ltd Silicon Harbour Centre 2 Dal King Street Tai Po Industrial Estate Tai Po New Territories Hong Kong 852 26668334 Mfax Motorola Fax Back System RMFAX0 email sps mot com http sps motorola com mfax TOUCHTONE 1 602 244 8609 US amp Canada ONLY 1 800 774 1848 HOME PAGE http motorola com sps Mfax is a trademark of Motorola Inc MOTOROLA Semiconductor Products Sector
25. rogram to this entry Select Utility Compile Debug to start the tool specified in the Debug Compile command line The shell automatically links the assembler program to this entry Select Utility Make to start the tool specified in the Make command line The shell automatically links the maker program to this entry Select Utility Rebuild to start the tool specified in the Rebuild command line The shell automatically links the MCUez linker program to this entry Select Utility Debug to start the tool specified in the Debug command line The shell automatically links the MCUez debugger program to this entry Select Utility Execute to start the tool specified in the Execute command line The shell automatically links the decoder program to this entry 4 5 3 Codewright Toolbar User s Manual Figure 4 4 illustrates the toolbar functions LIN COMPILE MAKE DEBUG EXECUTE COMMAND COMMAND COMMAND COMMAND Figure 4 4 Codewright Toolbar MCUez Installation and Configuration 38 MCUez Environment MOTOROLA MCUez Environment Configuring Motpad 4 6 Configuring Motpad Motpad is the default editor However if another editor has been defined as the default redefine Motpad as follows 1 Click the ezMCU icon on the toolbar to start the MCUez Shell 2 Click the Change button in the Configuration dialog box to open the Current Configuration dialog box 3 Selectthe Editor tab and select Motpad from
26. s c opes ruo qc ERE troit onra 36 Switching Configurations aes siriani rea 37 Co dewrisht Menu siii 38 Codewridht Ke T 1 00 errate 38 Copheuring MIGIPAR sosiodiitoriea T ibi do ERRARE ERA 39 CODES Notepad ae 9 9 56450605 eet e TSP 65560885084 40 Contouring Wordpad 6 0 9689 KR RKR helena AREA 41 Connie Ward 46625405 ses ee eecseneeeeeeee pede nsec ees 42 MCUez Installation and Configuration 8 Table of Contents MOTOROLA User s Manual MCUez Installation and Configuration List of Figures Figure Title Page PL 1 55 Pr 18 LIO rie iL ERECTA qd LA DEAS Ad ES 19 3 3 Current Configuration Window orar rra RTT 20 S4 Denis a NEG Pier oeaeenst kusDERY VE xar 3a b oto bs 21 3 5 Mew Configuration Dialog BOX b RexE ERES 22 3 6 Selecting a Project Directory sciiti 23 3 7 ss Me BONGE avait dard e REOR HER E RCROR HER E oe 25 30 Panarea heap 25 3 9 Denning Application Tools 501501099 27 a4 Toplba TIBET O PRO RE O 21 Slt Seting Pathe Tar Tolto x a 5 0 9 X te 6 9 R da Eine series ha 28 CAVIE di 224b vr ECHOS eran VIROS TP pF LEICA V3d VV KE 20 3 13 Setting Additional Tool Parameters ere mw 29 4 1 Editor Configuration for WinEdit L LL 34 c ROIO 36 4 3 Editor Configuration for Codewrnght 37 52 PRO 38 4 5 Editor Configuration for Motpad e eee eee 39 4 6 Editor Configuration Tor Notepad cosi cese E Rs 40 4 7 Editor Configuration for Wordpad aenean 4
27. s used for error feedback in the MCUez assembler and linker After selecting Codewright the shell automatically enters the appropriate options Figure 4 3 is a typical setup for Codewright Project Editor Tools Paths Additional Editor Codewright v Project File demo pi Executable CACWACw EXE Browse Options f Figure 4 3 Editor Configuration for Codewright 7 Select the Tools tab 8 Some tools specified here are automatically associated with Codewright commands such as menu entries and buttons ASSEMBLER is automatically associated with the Codewright Compile and Debug Compile commands MAKER is associated with the Codewright Make command LINKER is associated with the Codewright Rebuild command DEBUGGER is associated with the Codewright Debug command DECODER is associated with the Codewright Execute command 9 Click OK to close the Current Configuration dialog 10 The specified editor project file is created in the project directory and the associated icon is displayed in the MCUez toolbar 4 5 1 Switching Configurations Select Project Open to load a previously saved project configuration file MCUez Installation and Configuration User s Manual MOTOROLA MCUez Environment 37 MCUez Environment 4 5 2 Codewright Menu Select Utility Compile to execute the tool specified in the Compile command line The MCUez Shell automatically links the MCUez assembler p
28. the names of menus windows dialog boxes icons and buttons User s Manual MCUez Installation and Configuration 12 General Information MOTOROLA General Information System Requirements Courier type face is used for all C code program listings command lines and directories e Italics are used where the string is a place holder that may be substituted for a string of the user s own design e Variable user inputs are in Courier italics e Filenames are in italics with all lower case letters for example proj ext 1 3 2 Extended Backus Naur Form Extended Backus Naur Form EBNF is used frequently in this user s manual to describe file formats and syntax rules See Appendix C in the MCUez HC12 Debugger User s Manual Motorola document order number MCUEZDBGI2 for more information 1 3 3 Executable Files Generic Name Application Name ahcxx exe MCUez assembler elflink exe MCUez linker mcushell exe MCUez shell tool mcuez exe MCUez debugger NOTE xxrepresents the MCU Family HC05 HC08 HC12 depending on which MCU target is installed 1 4 System Requirements MCUez applications require Windows 959 or Windows NT MCUez Installation and Configuration User s Manual MOTOROLA General Information 13 General Information User s Manual MCUez Installation and Configuration 14 General Information MOTOROLA User s Manual MCUez Installation and Configuration Section 2 MCUez Installation 2
29. tions enable the editor to open the source file and highlight the line containing the error MCUez Installation and Configuration 26 MCUez Shell MOTOROLA MCUez Shell Defining or Redefining a Project 3 6 3 Tools Tab In this tab define applications that can be launched from the MCUez Shell toolbar Application paths are set in the Executable edit box as shown in Figure 3 9 Current Configuration x Project Editor Tools Paths Additional Tools New DEBUGGER LINKER Delete Executable CM CUEZ PROG AHC12 EXE j OK Cancel Help Figure 3 9 Defining Application Tools Select New to open the New Tool dialog box Enter the program name in the edit box Some names are reserved for MCUez applications or other tools Reserved names are ASSEMBLER LINKER DEBUGGER COMPILER BURNER MAKER LIBRARIAN and DECODER The program name is listed in the Tools tab and used for the help tip in the toolbar as show in Figure 3 10 Figure 3 10 Toolbar Help Tip MCUez Installation and Configuration User s Manual MOTOROLA MCUez Shell 27 MCUez Shell lt j Browse to or enter the path to the program in the Executable edit box The program icon is loaded automatically from the executable file and displayed on the toolbar If the shell cannot find the application defined in the executable path the icon shown to the left is set in the toolbar If the shell finds the applicati
30. ut configuration settings Editor Tools etc User s Manual MCUez Installation and Configuration 22 MCUez Shell MOTOROLA MCUez Shell Project Configuration 3 5 2 Opening a Project Select Open in the Configuration dialog box Select a project directory to open another project This is equivalent to selecting a project from the list in the MCUez Shell system menu Ensure that a default env file exists in this directory For new projects the default eny and project ini files are automatically created If a default env file is not found Environment File doesn t exist is displayed in the main Configuration dialog box Select Directory x Directory di Cancel Drives c Network Figure 3 6 Selecting a Project Directory After selecting an existing project directory that contains a default env file settings stored in the configuration files project ini and default env are displayed in the various tabs Project Editor Tools Path and Additional of the Configuration dialog box MCUez Installation and Configuration User s Manual MOTOROLA MCUez Shell 23 MCUez Shell 3 5 3 Changing Project Environment Select Change in the Configuration dialog box to display the Current Configuration dialog box and change parameters for the current project This dialog box is the same as the one shown in Figure 3 6 except the title will be Current Configuration Procedures for configuring the proj
31. z Shell User s Manual MCUez Installation and Configuration 30 MCUez Shell MOTOROLA User s Manual MCUez Installation and Configuration 4 1 Contents Section 4 MCUez Environment 4 2 s cr Le MCN 32 4 3 sene Pun rT cde dar CU A do b a ed oe d gn 32 4 3 1 i ee ORO OROSEI ee eee 33 44 Config ring WinBdi x aes x ac 6 Kde R K R KE R RRR KR R RKR K 33 4 4 Contiguring WINEDITINI csc lerici RRR R RR ERE ERES 35 4 4 2 Storing and Restoring Configuration Files 29 4 4 3 WinEdit Menu Selection is v 6 K 4 68 tk A RR AR ARR E 35 4 4 4 WwWinEdit Toolbar 2225995942474 T SS ETC PRAE ESO EX TERA 36 4 5 Configuring CONT BUR Lo Lees EC eens EROR PERRA Ee treor kit 36 4 5 1 Switching Configurations coanlesecessPEAUR ER I ERE REA ies 37 4 5 2 Codewrght Memi aires 38 4 5 3 Log arant TOUIDUE Lo s 6 64 RARA 38 4 6 Conieunnge MOLDE osare REVERSE COE TSERTEE ES 39 4 7 COPS NOISDU x 6 0 96579 4 E PRI tiua EPA SEQ RE P SR ETE 40 4 8 Configuring Wordpad i oed ey cebecevr EE S E E REPLRC PRA 4 4 9 Comrie RR EEE 42 MCUez Installation and Configuration User s Manual MOTOROLA MCUez Environment 31 MCUez Environment 4 2 Introduction NOTE The MCUez Shell is used to define the MCUez project environment Parameters for the environment are stored in the default env and project ini files This section describes how to edit the default env file parameters and manually configure various editors such as WinEdit and Cod
Download Pdf Manuals
Related Search