Assembly (Stage 3) -- interpreting the assembly errors in the listing file e1v1.lst

Click here to see e1v1.lst, the listing generated from the command

as68000 -V68020 -L -m -o e1v1.o e1v1.s


The meaning of the lines in the listing file "e1v1.lst"

  1. The assembler has accepted that the "word" (or label) C has the "meaning" (value) of hexadecimal 00202200.
              	C	EQU	$202200    
  2. The SDS assembler does not recognize the HVZ standard Motorola assembler directive ORG
    	      		ORG	$201150
    ----ERROR----> unknown instruction 'ORG'    
  3. The SDS assembler has recognized the need to set aside storage for the word-length (16 bits) value 639, storing it as the hexadecimal value 027F. This suggests that for ease of recognition during code development, we should change all "easy" decimal values into "easy" hexadecimal (hex) values when using the SDS tool set.
    000000 		       	A	DC.W	639   
  4. 000002 FF29	       	B	DC.W	-215 

    This line is correct. Note that the hex value FF29 ($FF29 or 0xFF29) is the 16 bit equivalent of the negative decimal value -215

  5. Note that the comment after the END statement has disappeared.

    This is not a problem here, but can develop into one later if you are not careful.

    Many people use the incremental approach in developing code. You develop, assemble, test and debug a small section of code before adding further code. If you forget to remove the END statement between the old and new code (a LSD I have performed many times) you will get very frustrated wondering why the lines are in your source code and not your object and listing files!



Last modified: July 22, 1996 11:58 AM by M. Smith.
Copyright -- M. R. Smith