>1. How C fits into Code Warrior and can be
>used with my micro.
>For example, I have
>seen examples using a function
>EnableInterrupts() which is self explanatory.
Well, its not a function at all. It is a macro as Lundin already mentioned.
After building the project once, you can jump to the definition of it.
>Where do you find a list of all
>these functions?
All the macros defined in hidef.h are defined in hidef.h :smileyhappy:
Well, I know, not really helpful. Most of the functions defined in the ANSI library are for ANSI-C compliance, so any good book on the language should explain them. The compiler manual also contain a chapter about the ANSI functions (contained as pdf in the help/pdf directory). But knowing C a bit helps.
>Where is a reference list of variables that
>define the register locations?
The IO peripherial registers are described in pdf's you can download from the freescale web site. The header file contained for the C32 is using the same names. When you create a project with the wizard, the right header is already included and you can start using them.
>How do I create multiple C source code files
>and link them together?
Just add all the C files to your project, or is the question how to do this in C?
Anyway, start with one file. Once this works, start splitting it up.
>What C features are not supported?
All the basics are there. The only things not supported are are things like file IO, just as there is no file system. Also printf needs some SCI inteface code, otherwise linking fails.
>2. Mixing C and assembly code.
>What problems should I look out for?
>Is it possible to reserve space for a
>variable with assembly code and reference
>that variable in C?
Sure.
You did read about the wizard and how it creates projects. If you select both C and asm during the wizard, the generated project contains both a C file and an assembly file. So you see the basics in there. In the end it depends on how deeply you want to interact between C and assembly, as starter I would start with C or assembly, and once you control one of the two languages, start interacting with the other.
>3. Monitoring the registers and memory space
>on my micro with the debugger.
>Is this even possible?
Of course! But (there has to be a but), there are different ways to connect from the debugger to the target system, and I'm not sure what you have available.
>4. Compiling project code and transferring
>to my micro.
>If someone can point me to tutorials on
>those questions, I believe a lot of my
>frustration will be relieved.
>Bonus points for a tutorial that
>starts with a new project and ends with
>a completed project loaded onto the micro.
>Thanks in advance!
Jon
Did you check the HCS12X_Quick_Start.pdf on the root of the installation? Well, it ends up running the code on the simulator, but that's a start. And if you do have a board properly configured in front of you connected with one of the supported ways to connect, then all it needs for hardware is to pick another connection in the last step in the wizard. Which connection and how to set it up really depends on what you have in front of you :smileywink:.