1 //------------------------------------------------------------------------
3 //------------------------------------------------------------------------
4 This project stationery is designed to get you up and running
5 quickly with CodeWarrior for MC9S12DP256B.
6 It is set up for the selected CPU and target connection,
7 but can be easily modified.
9 Sample code for the following language(s) is at your disposal:
12 The wizard has prepared CodeWarrior target(s) with the connection methods of
15 This interface/target is prepared to use the FCS (Full Chip Simulation).
18 This enables to debug with the P&E ICD12 target interface.
19 The P&E ICD12 target interface allows to debug using the
20 BDM connector with P&E BDM Multilink or Cable12 hardware.
21 The BDM Multilink and Cable12 connect to the host parallel port.
22 Please consult your hardware documentation for additional details.
25 Additional connections can be chosen in the simulator/debugger,
26 use the menu Component > Set Target.
28 //------------------------------------------------------------------------
30 //------------------------------------------------------------------------
31 This project is prepared to be designed with Processor Expert.
32 The project has an additional 'tab' named 'Processor Expert' where you
33 can configure the CPU and its beans.
34 The CPU selected is inserted into the Processor Expert project panel, in
35 the Debug and Release configurations.
36 Change of the configuration is possible by the mouse double-click on it.
37 All the installed Embedded Beans are accessible in the Bean Selector
38 window, grouped into folders according to their function. The mouse
39 double-click on selected Embedded Bean in the Bean Selector window adds
40 the Bean to the project. The mouse double-click on the Bean icon in the
41 Project panel opens the Bean Inspector window, which is used to set the
42 Bean properties. Source code is generated after selecting the
43 (Code Design 'Project_name.mcp') menu command from the CodeWarrior main
44 window (Processor Expert > Code design 'Project_name.mcp').
45 Use the bean methods and events to write your code in the main module
46 'Project_name'.c and the event module Events.c.
48 For more help please read Processor Expert help:
49 (Processor Expert > Help > 'Topic').
51 The following folders are used in CodeWarrior project window for
53 - User modules: contains your sources. The main module 'Project_name'.c
54 and event module Events.c are located here after the Processor Expert
56 - Prm: Linker parameter file used for linking. Note that the file used
57 for the linker is specified in the Linker Preference Panel. To open
58 the Preference Panel, please press <ALT-F7> or open the
59 (Edit > 'Current Build Target Name' Settings...) menu item in the
60 CodeWarrior main window menu, while the project window is opened).
61 After Processor Expert code generation 'Project_name'.prm file
62 will be placed here. You can switch off the .prm file generation in
63 Processor Expert if you want (in the CPU bean, Build Options)
64 - Generated code: this folder appears after the Processor Expert code
65 generation and contains generated code from Processor Expert.
66 - Doc: other files generated from the Processor Expert (documentation)
68 //------------------------------------------------------------------------
70 //------------------------------------------------------------------------
71 To build/debug your project, use the menu Project > Debug or press F5.
72 This will open the simulator/debugger.
73 Press again F5 in the debugger (or menu Run > Start/Continue) to start
74 the application. The menu Run > Halt or F6 stops the application.
75 In the debugger menu Component > Open you can load additional components.
77 //------------------------------------------------------------------------
79 //------------------------------------------------------------------------
80 The project generated contains various files/folders:
81 - readme.txt: this file
82 - Sources: folder with the application source code
83 - Startup Code: C/C++ startup code
85 - burner.bbl file to generate S-Records
86 - Linker Map: the .map file generated by the linker
87 - Libraries: needed library files (ANSI, derivative header/implementation files)
88 - Debugger Project File: contains a .ini file for the debugger for each
90 - Debugger Cmd Files: contains sub-folders for each connection with command
93 //------------------------------------------------------------------------
94 // Adding your own code
95 //------------------------------------------------------------------------
96 Once everything is working as expected, you can begin adding your own code
97 to the project. Keep in mind that we provide this as an example of how to
98 get up and running quickly with CodeWarrior. There are certainly other
99 ways to handle interrupts and set up your linker command file. Feel free
100 to modify any of the source files provided.
102 //------------------------------------------------------------------------
103 // Simulator/Debugger: Additional components
104 //------------------------------------------------------------------------
105 In the simulator/debugger, you can load additional components. Try the menu
108 //------------------------------------------------------------------------
109 // Additional documentation
110 //------------------------------------------------------------------------
111 Check out the online documentation provided. Use in CodeWarrior IDE the
112 menu Help > Online Manuals.
114 //------------------------------------------------------------------------
115 // Contacting Metrowerks
116 //------------------------------------------------------------------------
117 For bug reports, technical questions, and suggestions, please use the
118 forms installed in the Release_Notes folder and send them to:
119 USA: support@metrowerks.com
120 EUROPE: support_europe@metrowerks.com
121 ASIA/PACIFIC: j-emb-sup@metrowerks.com
begriffs.com / projects / cmsis-freertos / blob