#1715 PIC16F887 asm error

closed-fixed
5
2013-05-25
2010-11-26
quantumman
No

I get an error in the asm, it appears to be two commands sitting on the same line(line 1091) but I'm not familiar enough with PIC14 asm to be sure that is the only issue.

sdcc -mpic14 -p16f887 graphics.c --use-non-free --debug-xtra -V
+ "/usr/local/bin/sdcpp" -nostdinc -Wall -obj-ext=.o -DSDCC_USE_NON_FREE -DSDCC=300 -DSDCC_REVISION=6037 -DSDCC_pic14 -D__pic14 -DSDCC_PROCESSOR="16f887" -isystem "/usr/local/bin/../share/sdcc/include/pic" -isystem "/usr/local/share/sdcc/include/pic" -isystem "/usr/local/bin/../share/sdcc/include" -isystem "/usr/local/share/sdcc/include" -isystem "/usr/local/bin/../share/sdcc/non-free/include/pic" -isystem "/usr/local/share/sdcc/non-free/include/pic" -isystem "/usr/local/bin/../share/sdcc/non-free/include" -isystem "/usr/local/share/sdcc/non-free/include" "graphics.c"
+ "gpasm" -o "graphics.o" -c "graphics.asm"
graphics.asm:1091:Error [103] syntax error
+ "gpasm" -o "graphics.o" -c "graphics.asm" returned errorcode 256

sdcc -mpic14 -p16f887 graphics.c --use-non-free
graphics.asm:1091:Error [103] syntax error

SDCC : mcs51/gbz80/z80/ds390/pic16/pic14/TININative/ds400/hc08 3.0.0 #6037 (Oct 31 2010) (Linux)

Discussion

  • quantumman

    quantumman - 2010-11-26

    source code

     
  • Raphael Neider

    Raphael Neider - 2010-11-26

    The problem was triggered by the incompletely initialized array font[]; the output routine simply concatenated the 'retlw 0x00' instructions without newlines in between.
    Fixed in svn r6067.

    BTW: Consider turning font into an array of char (8 bit) instead of int (16 bit) to save space and retrieval runtime.

     
  • Raphael Neider

    Raphael Neider - 2010-11-26
    • labels: --> pic14 target
    • milestone: --> fixed
    • status: open --> closed-fixed
     
  • Raphael Neider

    Raphael Neider - 2012-02-12
    • assigned_to: nobody --> tecodev
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks