Technical Note (8 & 16-bits) TN 98

Transcription

1 Using Development Tools Kit with WinIDEA Configuring WinIDEA for the Metrowerks Development Tools Some configurations are required in order to make an efficient use from the development Tools within WinIDEA. General working and executable path have to be indicated. Extension for file types can be set. An additional configuration must be performed for the environment path settings to be sure that the build tools find the library and the header files. Executable files can be associated with the compile/assemble, Make, rebuild buttons New entries in the menu Tools with associated command can be create. Configuration of WinIDEA paths Open WinIdea and create a new Workspace directory File New Workspace. Enter a working directory and a project name. Choose following menu: Projet Project Settings. The "Project Setting" dialog is opened. Select the General tab. Compiler toolset path: Enter prog directory of your development tool installation Output directory: Enter the whole path to your project directory Output file name: Enter the name of the executable file, which will be, generate (For example Fibo.abs) Root directory: Specifies a root directory for project files location. Using a root directory, WinIDEA can store paths to project files in relative from, thus assuring workspace moveability. Page 1 of 6

2 Configuring the file extension By clicking on the File Extension tab you will be able to add and change the extension of Basic File Types. For an efficient usage of the build tools, following file extensions types can be defined: File type Input Extensions Header Extensions Output Extensions ASM Files asm - o C Files c h o C++ Files cpp h o Linker File O;lib - - Note that default value obj have to be replaced with o to work with CodeWarrior for 8 & 16 bit. Page 2 of 6

3 Configuring the environment settings By clicking on the Customize tab you will be able to specify new paths or environment variable settings for the development tools. Refer to the tools user manual for a list of the available environment variables. Environment Settings: Enter the path for libraries and header files. Any environment variable can be defined here. Configuring the compile/assemble, Make, rebuild buttons By clicking on the Compiler you are able to define the compiler, which will be launch, by clicking on one of compile/assemble, Make, rebuild buttons: Page 3 of 6

4 Compiler Path: Option: Enter first the path to the piper.exe tools followed by the path of compiler executable. The CHC12.EXE must be replaced with the corresponding compiler name if you use another CPU. Enter $(EDNAME) to specify the Full file name and append all the compiler options you want to use in the project. For more information about additional modifier supported by WinIdea, please refer to your WinIdea user manual. For more information about compiler options refer to Metrowerks compiler manual. By clicking on the Assembler you are able to define the assembler, which will be launch, by clicking on one of compile/assemble, Make, rebuild buttons: Assembler Path: Option: Enter first the path to the piper.exe tools followed by the path of assembler executable. The AHC12.EXE must be replaced with the corresponding assembler name if you use another CPU. Enter $(EDNAME) to specify the Full file and append all the assembler options you want to use in the project. For more information about additional modifier supported by WinIdea, please refer to your WinIdea user manual. For more information about assembler options refer to Metrowerks assembler manual. Page 4 of 6

5 By clicking on the Linker you are able to define the linker file which will be launch by clicking on one of compile/assemble, Make, rebuild buttons: Linker Path: Enter first the path to the piper.exe tools followed by the path of linker executable. Options: Enter the name of the *.prm file (sample.prm). Enter after this all your linker option. For more information about linker options refer to Metrowerks linker manual. Indirection File: Enter the path and file name of your *.prm file. Translate Character: Enter the character in the *.prm file that will be replaced with the Source files list from your Workspace Note that the string & & in sample.prm will be replaced with Source files list separate with a blank LINK fibo.abs NAMES & & END SECTIONS MY_RAM = READ_WRITE 0x800 TO 0x80F; MY_ROM = READ_ONLY 0x810 TO 0xAFF; MY_STK = READ_WRITE 0xB00 TO 0xBFF; PLACEMENT DEFAULT_ROM DEFAULT_RAM SSTACK END INTO MY_ROM; INTO MY_RAM; INTO MY_STK; /* set reset vector to function _Startup defined in startup code start12.c */ VECTOR ADDRESS 0xFFFE _Startup Page 5 of 6

6 & & is replace with ansis.lib fibo.o start12.o in the sample.prm file before the linker is started. Using WinIDEA to start the Debugger Choose following menu: Tools Customize. The "Customize" dialog is opened. Select the Tools tab. Click on the browse button and select a *.exe file or *.bat file to be started. Click on the add button to add a menu entry in the Tools menu. Field "Menu Text", "Command", "Argument" and "Initial Directory" must be initialized before the "Add" button is pressed. After clicking on OK, you will have a new entry in the tool menu that start the corresponding executable: Menu text: Enter first name of the menu entry. Command: Enter the path of the *.exe file or *.bat file which will be started. Initial directory: Enter the directory where the tool will be started or select the arrow ( ) on the right to brings a list of predefined macros to specify the path. Page 6 of 6