OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [freertos-6.1.1/] [Demo/] [HCS12_CodeWarrior_small/] [readme.txt] - Blame information for rev 609

Go to most recent revision | Details | Compare with Previous | View Log

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

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.