Menu

Tree [r10] /
 History

HTTPS access


File Date Author Commit
 CHANGELOG 2008-01-03 l33tbunni [r7] assembler.c: re-wrote logic to determine what ...
 Makefile 2008-01-12 l33tbunni [r10] Changed makefile, thank you Bert Regeer, update...
 README 2008-01-01 l33tbunni [r5]
 assembler.c 2008-01-12 l33tbunni [r10] Changed makefile, thank you Bert Regeer, update...
 assembler.h 2008-01-07 l33tbunni [r8] assembler.c/.h: FINALLY got variable names work...
 gsasm.c 2008-01-01 l33tbunni [r5]
 gsasm.h 2008-01-01 l33tbunni [r5]
 hex_file.c 2008-01-01 l33tbunni [r5]
 hex_file.h 2008-01-01 l33tbunni [r5]
 sxhexout.c 2008-01-01 l33tbunni [r5]
 sxhexout.h 2008-01-01 l33tbunni [r5]
 sxkey.c 2008-01-01 l33tbunni [r5]
 sxkey.h 2008-01-01 l33tbunni [r5]
 sxkey_new.c 2008-01-01 l33tbunni [r5]
 sxkey_new.h 2008-01-01 l33tbunni [r5]
 sxkey_old.c 2008-01-01 l33tbunni [r5]
 sxkey_old.h 2008-01-01 l33tbunni [r5]

Read Me

This is GSASM, the GNU SX Assembler.

This is _NOT_ intended to be a replacement for Parallax's SXKey 
software, this is _NOT_ supported by Parallax, this is my creation in 
order to have a GNU alternative to Parallax's software.

More information can be found at http://gsasm.sourceforge.com

This software is still currently in alpha stages, expect problems, I 
have done as much as I can to make sure all errors are caught and input 
to output is mimicked as best as possible from Parallax's SXKey IDE.  

GSASM is designed to be exactly like SXKey in terms of assembly syntax, 
my goal is to be able to simply to have any source file in Parallax's 
SXKey to compile the exact same way in GSASM.


QUIRKS/BUGS

Right now ALL registers MUST be refered to as their hex locations, RA, RB, RC, FSR, etc, 
except for W, !WDT, and !OPTION.  There is no syntax for variables and naming,
at this stage it ends up being hard core assembly.  DEVICE directives are the 
same as referenced by SASM/Parallax, FREQ can be specified, but is ignored, 
ID can be specified, but is ignored.  GSASM now has the ability to 
program chips using gsxprog which I have incorporated in to GSASM.  I 
have found an error when using code protect FUSE setting, the readback 
verification fails, but the chip gets programmed correctly.  In time I 
will build my own programmer, this is just something to allow me to 
advance my program quickly.  


INSTALLING

simply

$ make
# make install

It will be installed to /usr/bin, if you do not want it there, change 
the Makefile

Questions, bugs, comments direct to kbahnsen@gmail.com

Kris Bahnsen, 2007
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.