ASM11

A two-pass absolute DOS cross-assembler for the 68HC11

Quick Reference Guide

ASM11 - Copyright © 1999 by Tony Papadimitriou <[email protected]>

Last Update: 15-November-99 for ASM11 v1.84

Command-Line Syntax and Options

ASM11 [-option [...]] [[@]filespec [...]] [>errfile]

option(s) may appear before, in between or after filespec(s).

option(s) specified apply to all files assembled, regardless of command line placement.

Text file(s) containing list(s) of files to be processed may be specified by naming the text file on the command line, prefixed with a «@» character. These text files may not contain command line options.

filespec(s) may include wildcard characters (?,*). Wildcards are not allowed in filespec(s) that are prefixed with a «@» but are allowed in filespecs inside @files.

If the file extension for a source filespec is omitted, the extension «.ASM» is assumed (see description of the -R.ext option below).

Assembler errors may be redirected to errfile using standard DOS output redirection syntax. This capability may be used in conjunction with, or as an alternative to the -E+ option.

The assembler will set the DOS ERRORLEVEL variable when it terminates as indicated:
0 No error, assembly of last file was successful
1 System error (hardware I/O failure, out of disk space, etc.), or -W 24224b113y option failure
2 Error(s) generated (or Escape pressed) during assembly of last file
3 Warning(s) generated during assembly of last file
4 Assembler was not started (help screen displayed, -W 24224b113y option used with success)

Source File Pseudo-Ops

Source File Processing Directives

All processing directives must be prefixed with a or character. ASM11 will recognize either character as the start of a processing directive.

If a directive has a corresponding command-line option, the directive in the source file will override the command line directive at the point in which the source file directive is encountered.

[text] will be trimmed of spaces. To have spaces display, use the Alt-255 character.

Expression Operators and Other Special Characters

Recognized by ASM11

Expressions are evaluated in the order they are written (left to right).
All operators have equal precedence.

Avoid inserting spaces between values and operators (unless using -SP+ switch and ; comments).

ASM11 Extended Instruction Set

The instructions listed below are not actually new instructions, rather, internal macros which generate one or more 68HC11 CPU instructions. These instructions are only recognized if the extended instruction set option is enabled (-X+ command line option or $EXTRAON processing directive).

ASM11-generated Error and Warning Messages

Here's a list of error and warning messages.

Errors inform the user about problems that prevent the assembler from producing 'correct' code. If there is even a single error during assembly, no files will be created (except for the ERR file, if one was requested).

Warnings inform the user about problems that do not prevent the assembler from producing 'correct' code but the code produced may not be what was intended, or it may be inefficient. A program that has warnings may be totally correct and run as expected.

Errors and warnings that begin with 'USER:' are generated by #ERROR and #WARNING directives, respectively. Their meaning and importance is decided by the source code author.

In the lists below, what's enclosed in angle brackets (< and >) is a 'variable' part of the message. That is, it is different depending on the source line to which the error or warning refers.

The order the messages appear below is random. Some messages have similar meanings, they simply result from different checks of the assembler.

Errors

Invalid binary number

The string following the % sign is not made up of zeros and/or ones.

Binary number is longer than 16 bits

A binary number may have no more than sixteen digits. Leading zeros are ignored.

"<SYMBOL>" not yet defined, forward refs not allowed

RMB and DS directives may not refer to forward defined symbols. You must define the symbol(s) used in advance.

Bad <MODE> instruction/operand "<OPCODE> <OPERAND>

The instruction and operand addressing mode combination is not a valid one, or you have turned the -X option (EXTRAx directive) off. For example, TST #4 will show «Bad IMMEDIATE instruction/operand "TST 4"» because although TST is a valid instruction, it does not have an immediate addressing mode option.

Could not close MAP file

For some reason, the MAP file could not be closed. Possibly some disk problems (check available space, etc.) If you can't figure out what's wrong and still must assemble, turn off the MAP with the -M- option.

Could not close SYM file

For some reason, the SYM file could not be closed. Possibly some disk problems (check available space, etc.) If you can't figure out what's wrong and still must assemble, turn off the SYM with the -S- option.

Could not create MAP file <FILEPATH>

For some reason, the MAP file could not be created. Possibly some disk problems (check available space, etc.) If a MAP file of the same name already exists it probably has a read-only attribute or is somehow locked by the system.

Could not create SYM file <FILEPATH>

For some reason, the SYM file could not be created. Possibly some disk problems (check available space, etc.) If a SYM file of the same name already exists it probably has a read-only attribute or is somehow locked by the system.

Expression error

Something is wrong with the attempted expression, or an expression is altogether missing.

Invalid argument for DB directive

The value or expression supplied is not correct.

Invalid argument for EQU directive

The value or expression supplied is not correct.

Invalid first argument

The first value or expression supplied is not correct.

Invalid second argument

The second value or expression supplied is not correct.

Missing value between commas

Two (or more) commas without a value in between.

Possibly duplicate symbol "<SYMBOL>"

The symbol shown has already been defined. The word 'possibly' suggests that a symbol may have been truncated to 19 characters, and thus not appear duplicate to the user, only to the assembler. It also suggests that the original may have been written for case-sensitive assembly but you turned the option off.

Repeater value is invalid

The repeater value (the :n part of the opcode) is not a positive integer number.

Symbol "<SYMBOL>" contains invalid character(s)

The symbol shown contains characters that are used in special ways and, therefore, cannot be part of a symbol because they will cause ambiguities. For example, a quote within a symbol is not allowed.

Undefined symbol "<SYMBOL>" or bad number

The string shown is either a symbol that hasn't been defined at all, or it is a number that has some error, for example: $ABCH and $FFFFF are not valid hex numbers. The first contains an invalid character while the second is greater than 16 significant bits ($FFFF).

USER: <USER TEXT>

This is a user generated error via the #ERROR directive.

Comma not expected

A comma was found in an unexpected position within the operand. Possibly using more arguments than required.

Syntax error

Some symbol is confusing the assembler. For example, FCB #$FF will give a syntax error because the # indicates immediate addressing mode which makes no sense for an FCB directive (the correct is FCB $FF

Empty string not allowed

An empty string (two quotes next to each other) is not allowed because there is no value that can be generated from it.

Could not open include file <FILEPATH>

The [path and] file shown could not be located or opened. If the file exists, it may be locked by some other program (under Windows, the file could be loaded in an editor).

ELSE without previous Ifxxx

An #ELSE directive was encountered that does not match any unmatched #IF directive.

ENDIF without previous Ifxxx

An #ENDIF directive was encountered that does not match any unmatched #IF directive.

Forward references not allowed

The #MEMORY and other directives do not accept forward references.

Incomplete argument for Bit Instruction (commas?)

BSET BCLR BRSET, and BRCLR require commas between each part of the operand. You have either left the commas out or forgotten to supply all the parts of the operand. Assembling code written for Mot's AS11 will produce a lot of these.

Invalid expression(s) and/or comparator

The expression or comparator used in the #IF directive is incorrect.

Missing branch address

BRSET and BRCLR require a target address for branching to but one was not supplied.  The branch target is the last part of the operand and it can be any valid expression.

Missing INCLUDE filename

An #INCLUDE directive was supplied without any [path and] filename.

Missing required first address

A #MEMORY directive was encountered without any value or expression.

Repeater value out of range (1-32767)

The repeater value (the :n part of the opcode) must be from 1 to 32767.

Required string delimiter not found

You have supplied only one quote to a string, or the string is inappropriately separated from the previous or next operand. For example: 'ABC'CR lacks a comma between the quote and the CR symbol. So, the found string ACB'CR is invalid.

Symbol "<SYMBOL>" does not start with A..Z, . or _

All symbols must start with one of the above characters. (Local symbols start with a ?)

Symbol "<SYMBOL>" is reserved for indexing modes

You have used a symbol named X or Y. These names are not allowed because they cause ambiguities with the X and Y registers in the various indexed mode instructions.

Too many include files. Maximum allowed is 99

The maximum number of INCLUDE files is 99 (regardless of nesting level). You have gone over this number. Possible solution: Combine related files together as required. Keep in mind that although the assembler allows this many files to be included, a lot of programs cannot handle these many files in the MAP files.

Division by zero

The expression used contains a division by zero after the / operator.

MOD division by zero

The expression used contains a division by zero after the \ operator.

"<SYMBOL>" is too far back [<VALUE>], use jumps

The target of a branch instruction is too far back by as many bytes as shown. Either get it closer to the target, or use a jump instead. Some instructions, like BRCLR or BRSET do not have an equivalent jump so you must use an intermediate 'jump hook' instead.

"<SYMBOL>" is too far forward [<VALUE>], use jumps

The target of a branch instruction is too far forward by as many bytes as shown. Either get it closer to the target, or use a jump instead. Some instructions, like BRCLR or BRSET do not have an equivalent jump so you must use an intermediate 'jump hook' instead.

Invalid argument for DW or FDB directive

The value or expression supplied is not correct.

Invalid argument for ORG directive

The value or expression supplied is not correct.

Invalid argument for RMB or DS directive

The value or expression supplied is not correct.

Invalid argument for END directive

The value or expression supplied is not correct.

Warnings

Direct mode wasn't used (forward reference?)

Automatic Direct Mode detection requires that symbol(s) used be defined in advance. You should either define the referenced symbol(s) earlier in your code, or use the Direct Mode Override (<) to force the assembler to use Direct Addressing Mode.

Label on left side of END line ignored

The END directive does not take a label. If one is used it will be ignored (it will not be defined).

Label on left side of ORG line ignored

The ORG directive does not take a label. If one is used it will be ignored (it will not be defined).

Trailing comma ignored

A multiple-parameter pseudo-instruction was used (such as FCB and DW) and a comma was found at the end of the parameter list. This may indicate the list is separated by both commas and spaces. You must either remove the spaces or assemble with #SPACESON (or the -SP+ option).

Violation of MEMORY directive at address $<VALUE>

ASM11 has produced code and/or data that falls outside any address ranges defined via the #MEMORY directive. You must either add more #MEMORY directives to cover the offending range or move your code/data elsewhere (using appropriate segment and/or ORG statements).

EQUs require a label, ignoring line

A EQU by definition is meant to assign a value to a symbol but no symbol name was supplied. Using a repeater value in an EQU will also produce this warning for each repetition of the statement except the first one. You should NOT use repeaters with EQU

Forward references are always FALSE

Conditional directives other than #IFDEF and #IFNDEF produce this warning if the symbol(s) referenced have not yet been defined. In this case, the conditional evaluates to false, and if there is an #ELSE part, it is taken.

String is too long, only first 8 or 16 bits used

8-bit and 16-bit instructions (such as LDA and LDD) cannot accept a constant string value of more than 8 or 16 bits, accordingly. The longer string encountered is truncated to the first two characters before being used. If an 8-bit operand is expected, you will also get a warning about using a 16-bit value with an 8-bit operand.

S19 overlap at address $<VALUE>

The code/data of the shown line overlaps an already occupied memory location at the address shown. The warning appears at code/data that causes the first and consequent overlaps but the problem could be with the original code/data that occupied this address. The assembler has no way of knowing your intentions!

Instruction TEST is only valid in SPECIAL TEST MODE

The instruction TEST is only defined when running the 68HC11 in special test mode. This warning is generated just in case you meant to say TST and typed TEST by mistake.

Extra operand found ignored

In a BCLR BSET you have supplied a branch address. Depending on what you intended to do, either change the instruction to BRCLR BRSET or remove the last operand.

No ending string delimiter found

The last string quote is missing. ASM11 did its best to produce a value for you but it may not be the one you wanted. For example: «LDA #'a» will produce this warning but the value used will be correct, while «LDA #'a ;comment» will produce a wrong value (the space after the a because the string 'a ' is a 16-bit value downsize to an 8-bit value, you will get a warning about this also).

Operand is larger than 16 bits, using low 16-bits

The operand is greater than 16 bits but the instruction can only accept a 16-bit operand. The lower word was used.

Operand is larger than 8 bits, using low 8-bits

The operand is greater than 8 bits but the instruction can only accept a 8-bit operand. The lower byte was used.

Possible memory wraparound at address $<VALUE> (<DEC VALUE>)

It seems like you have reached the end of memory ($FFFF) and caused the Program Counter to wrap around to zero. In some situations this may be intentional. Using RMB 2 (rather than FDB or DW) in the vector for RESET will also give this warning but it should be ignored. The address shown is the beginning address of the [pseudo-] instruction that caused the wraparound.

A JUMP was used when a BRANCH would also work

You could have used a Branch instead of a Jump. This will make your code one byte shorter for each warning. Controlled by the -REL (OPTRELxx) option.

Attempting operation with missing first operand

An operation was attempted without an operand before the operator. For example /3 (divide by 3) is missing the dividend.

JSR/BSR followed by unlabeled RTS => JMP/BRA

You could safely replace the sequence JSR/RTS or BSR/RTS to a single JMP or BRA, accordingly. The code will remain equivalent but you will gain a byte of memory, two bytes of stack space, and also make it a little faster. It will, however, make your source-code less user-friendly and a bit harder to follow. It should probably be done only when speed if very important or if you're running out of space and must save every byte you can. WARNING: In certain situations, the code is dependent on the return address pushed on the stack by a JSR or BSR instruction. In those cases, do NOT replace with JMP/BRA because the code will not run correctly. It is assumed you know the code you're working on. Controlled by the -RTS (OPTRTSxx) option.

No ORG (RAM:$0000 ROM:$D000 DATA:$B600 VECTORS:$FFD6)

ASM11 started producing code/data without having been told explicitly where to put it. A segment directive may have been used, however, with its default value. NOTE: You will only get this warning once no matter how many segments you are using. This means that you may be required to add ORGs for each segment or else the default values will be used.

Phasing on <SYMBOL> (PASS1: $<VALUE>, PASS2: $<VALUE>')

The symbol shown was defined two or more times using different values. The values given may help you determine the type of the problem more quickly. If it's a duplicate label with the same purpose or a completely random use of the same symbol name. The assembler will attempt to use the last (most current) value for this symbol.

TABSIZE must be a positive integer number, not changed

The TABSIZE directive requires a positive integer, and one wasn't supplied. The current tab size was not altered.

Unrecognized directive "<DIRECTIVE>" ignored

Something that looks like a directive (i.e., begins with # or $ and appears first in a line after the white-space) was encountered but it wasn't a valid one. Check spelling. If spelling seems correct, you may be assembling someone else's code written for a later version of ASM11 that supports additional directives your version doesn't understand.

USER: <USER TEXT>

This is a user generated warning via the #WARNING directive

Branching to next instruction is needless

You are using a branch instruction (other than BSR) to send control to the immediately following instruction. This is the default action of the CPU, so this instruction is not required. Controlled by the -REL (OPTRELxx) option.

Jumping to next instruction is needless

You are using a Jxx instruction (other than JSR) to send control to the immediately following instruction. This is the default action of the CPU, so this instruction is not required. Controlled by the -REL (OPTRELxx) option.

ASM11's Miscellaneous Features

Repeaters

Each opcode or pseudo-opcode can be suffixed by a colon [:] and a positive integer between 1 and 32767. This is referred to as the <repeater value>. The repeater value must be provided explicitly, no expressions or symbols are allowed, just a plain number. Some examples:

LSRA:4 ;Move high nibble to low

FCB:256 0 ;Create a table of 256 zeros

INS:4 ;De-allocate two words from stack

Segments

Five special directives allow you to use segments in your programs. Segments are useful mostly in conjunction with the use of INCLUDE files. Since often it is not possible to know the current memory allocation for variables and code when inside a general-purpose INCLUDE file, segments help overcome this (and other problems) with ease.

Also, we often want to have our code and data (strings, tables, etc.) grouped in a different way in our source-code than the resulting S19 (object). Segments again give us the ability to have related code, variables, and data together in the source but separated into distinct memory areas in the object file. When using segments, it is common to have a single ORG statement for each of the segments, near the beginning of the program. Thereafter, each time we need to «jump» to a different memory segment/area, we use the relevant segment directive.

Although the five segments are named $RAM $ROM $DATA $SEGn, and $VECTORS their use is identical (except for the initial default values) and they are interchangeable. Use of segments is optional. If segments aren't used, you are always in the default $ROM segment (which explains why code assembles beginning at $D000).

Local Symbols

All symbols that begin with a question mark [?] are considered to be local. Local symbols are local on a per-file basis. Each INCLUDE file (as well as the main file) can have its own locals that will not interfere with similarly named symbols of the remaining participating files. This has two advantages: First, symbols can be re-used in another INCLUDE file in a completely different way. Second, local symbols are not visible outside the file that contains them. This last benefit makes it possible to write quite complex INCLUDE files while making only the global variables and subroutine entry labels visible to the outside.

Marking big blocks as comments

$IFDEF without any expression following will always evaluate to False. This can be used to mark out a large portion of defunct code or comments. Simply «wrap» those lines within $IFDEF and $ENDIF directives. This saves you the trouble to individually mark each line as comment, eg.,:

$IFDEF

This is a block of comments explaining all the little

details of this great assembly language program..

Blah, blah, blah...

$ENDIF

The only drawback is that the listing file will not include this section. In some cases this is desirable, in others it isn't.

Creating 'menus' of possible -D option values

ASM11 -Dxxx [[-Dxxx]...] is used to pass up to ten symbols to the program for conditional assembly. Here's a tip for creating 'menus' of possible symbols to use with the -D option, so you don't have to remember them. An example follows:

#ifdef ?

$message ** ** ** ** ** **

$message * Choice of run-time conditional symbols

$message ** ** ** ** ** **

$message * DEBUG: Turns on debugging code

$message * E2: Target is MC68HC811E2

$message * E9: Target is MC68HC711E9

$message ** ** ** ** ** **

$fatal Run ASM11 -Dx (where x is any of the above)

#endif

The command ASM11 -D? PROGNAME.ASM will display the above 'menu' of possible -D values and terminate assembly. If you make it a habit of doing this in all your programs, then at any time you're not sure which conditional(s) to use, simply try assembling with the -D? option and you will get help. (A question mark is the smallest possible local symbol you can define. It is a perfect candidate for this job as it is easy to remember because it's like asking for help, and also because it is only visible in the main file. You could, of course, use any other symbol name you like.)

Using -Dx with specific values

You may also assign a specific value to a symbol defined at the command-line. This makes it possible, among other things, to assemble a program at different locations on the fly. For example, the following program:

;SAMPLE.ASM

#ifndef ROM ;needed to avoid «Duplicate symbol..» errors

ROM equ $F800 ;Default ROM location

#endif

ORG ROM

Start  lds #$FF ;the program begins here

... ;rest of program is left to imagination

bra * ;the program ends here

will be assembled at $F800 with the command ASM11 SAMPLE but you could also assemble with a command similar to this: ASM11 SAMPLE -DROM:$D000 to move ROM to a different location at assembly time.

As another example, you could declare an array where you define the dimension during assembly. No need to edit the source.

;SAMPLE.ASM

#ifndef ARRAYSIZE ;needed to avoid «Duplicate symbol..» errors

ARRAYSIZE equ 10 ;Default size for array

#endif

#if ARRAYSIZE < 2 ;check for minimum size allowed

#error ARRAYSIZE must be at least 2

#endif

ORG RAM

Status RMB ARRAYSIZE

Pointer  RMB ARRAYSIZE*2

...

ORG ROM

Start  lds #$FF ;the program begins here

... ;rest of program is left to imagination

bra * ;the program ends here

Getting rid of the «No ORG...» warning

If you are annoyed by the «No ORG...» warning that shows up whenever the assembler attempts to produce code or data without first having encountered an ORG statement, here's how to turn it off without actually specifying a fixed origin.

Somewhere before any code or data, and regardless of the current segment, use the pseudo-instruction:

org *

This is a «No Operation» ORG statement because it will simply use the current location counter for the ORG. It effectively does nothing. It will, however, set the appropriate internal flag that tells the assembler an ORG has been used and, thus, no warning!

Tips on using the MEMORY directive

The MEMORY directive is generally very useful for any program. It could help you save precious debugging time by alerting you whenever you accidentally put code and/or data where there is no real memory. The best place to use this directive is the same include file that defines the particulars of a specific MCU. And, assuming you always INCLUDE one such file in every program you write, you can forget about it.

Another use for the memory directive is to help you write a program that does not necessarily reside in specific memory locations but, rather, it occupies no more than so many bytes. For example, you're writing a small program that must be no more than 100 bytes long. Here's how to set the MEMORY directive to warn you should you go over this limit:

Start  lds #$FF ;the program begins here

... ;rest of program is left to imagination

bra * ;the program ends here

#memory Start Start+100-1 ;allowed range = Start to 100 bytes later

If while writing your program you begin getting MEMORY Violation warnings, you'll know you have reached (actually, gone beyond) the allowed limit. You must cut down the size of your code until the warning disappears.
Where to get ASM11

You could try any of the following links:

https://www.aspisys.com/asm11.htm

https://www.geocities.com/SiliconValley/Code/8605/

http://www.simtel.net/simtel/msdos/crossasm/ (this one may lag a few versions back)

Look for a filename in the format ASM11_xx.ZIP where a higher xx number indicates a newer version.

If you believe there is a newer version available and all else fails, write to me at <[email protected]> and I'll e-mail you the latest. Please mention your current version to avoid receiving the one you already have.