2 replies to this topic

[Karl G]

I'm trying to figure out the cause of messages along these lines output by DASM:

old value: $0001  new value: $000e
old value: $0007  new value: $0004
old value: $fa00  new value: $fa05
old value: $fa05 new value: $fa0a

...

There are 51 of them, and I believe that they are coming from an assembly module where I'm defining 50 text glyphs like so:

text_data

left_text

__A = * - text_data ; baseline (0)
    .byte %00100000 
    .byte %01010000
    .byte %01110000
    .byte %01010000
    .byte %01010000
    
__B = * - __A
    .byte %01100000
    .byte %01010000
    .byte %01100000
    .byte %01010000
    .byte %01100000    
    
__C = * - __A
    .byte %00110000
    .byte %01000000
    .byte %01000000
    .byte %01000000
    .byte %00110000    
    
__D = * - __A
    .byte %01100000
    .byte %01010000
    .byte %01010000
    .byte %01010000
    .byte %01100000

...

There are also definitions for the same glyphs with the glyphs on the right side, but without the labels.

 

What do these messages likely mean?  I would think that this message would be indicating that I'm redefining symbols, but I don't think that's the case here.

 

[Nukey Shay]

I saw that error before.  Turns out that I didn't declare the address location of a variable soon enough in the assembly (so that on first pass, some instructions were using absolute addressing, and then zero page addressing on the second pass).  Have Dasm make a report with the -List switch, then take a look at where the errors start.  It'll show you how many bytes each instruction is using as it builds the binary.

 

Dasm C:\folder_name\program.asm -f3 -lreport.txt -oC:\folder_name\binary.bin

Edited by Nukey Shay, Mon Feb 4, 2019 9:33 AM.

[Karl G]

Thanks!