It makes sense to include all the '.def' files in each '.asm' file then, but some labels are cross referenced - for example, 'main.asm' calls for functions from 'io.asm'. Nope, the proper way mandates that I assemble each file independently. It leaves you guessing where in that file the error has occurred, and I'm not masochistic enough for that. A bug in 'io.asm' will come out as a bug in 'semyon.asm' in line 12, which is where the problematic file is included. The practical problem is that ASXXXX is not smart enough to trace bugs into the included files. The conceptual problem is that it's not doing what I intended - I didn't want it to simply copy and paste my code together, but to assemble it in pieces and then assign all the addresses and tie the hex file together. Unsurprisingly, it gets assembled just as good as assembling it all in one file. The 'include' directive just copies the included files into the caller file. Here is 'semyon.asm' where it all goes together:

The cruedest way to get all my files together is to create a capital assembly file which includes all these files. include directive, just like C preprocessor #include. These are used in other assembly files using the. These files are pure assembly files, and as it seems that ASXXXX is agnostic to file extension, I'll go with ASXXXX examples and call these 'f' and 'f'. Akin to header files in C, these are used to define constants - such as SFR locations - and macros - such as SFR assignments. How can it be done?įirst, one must have define files. So I've split it into files which make sense together.

When the code has grown big enough, it made sense to split it into several files.

Assembly 8051 fibonacci