mke_et --
I mean that I am too lazy to deal with a single file that is over 10,000 lines long. Admittedly, about half of that is mc9s12a32.inc and I am using about 1% of that. But entering it from scratch would mean debugging it, and I really don't have that sort of time.
My HC11 tool was MCUasm, I never used the "!" declarations, all my "magic numbers" are symbolics in the code with a single module devoted to defining them and they are practically all hex anyway.
I do use conditionals, but none of them created any problems.
The biggest "problem" I had was that the HCS12 had so many more resources that I was able to get rid of a bunch of external timers, etc, and move it on board. Of course, then I had to re-think functions that I hadn't thought about since I first wrote that code, many, many years ago.
Hello Gary,
If you are using absolute assembly, you don't really need to create a CW project. Simply run the assembler program as a separate tool, in isolation from the IDE, and it will generate the necessary output files directly (without the linker). Assuming your include files are in the same directory as the main ASM file, you may need to load a "default" project.ini file located in same directory, so the assembler can find your include files.
Regards,
Mac
Hello
First you have to decide whether you want to use absolute or relocatable assembly.
In absolute assembly you have one single assembly unit (i.e. a source file and n include file) assembled as a whole in one step. All section have to be absolute in that mode.
If you decide to go with relocatable assembly (i.e. Several assembly source files assembled separately), you have to use the linker to build the final application.
What do you mean exactly when you say the linker is not happy? What does he report back?
CrasyCat
CrasyCat --
My understanding of absolute assembly is that it all has to be in one source file. The source files for this program take up over 600K (I comment rather more heavily than most), and I am too lazy to scroll past all that stuff to get to what I need.
The linker returns a "L1923: File (filename) has no DWARF debug info". Insert the name of each of the 12 files for (filename). It doesn't have DWARF debug info because it is assembly, according to the help for L1923. The help goes on to say that generating debug info can be skipped, but doesn't say how, and I have been unable to guess where it might be. The messages are annoying, but I can live with annoying.
The linker also returns a "L1115: Function Entry not found" and a "L1106 Object Entry not found". The help for these says they are generated if no "main" function exists. The problem is that it does exist, it is called main, and it is specified in Edit > Softec Settings > Debugger Settings.