diff --git a/doc/asm/macro.htm b/doc/asm/macro.htm index 25798bb5..97d0dd39 100644 --- a/doc/asm/macro.htm +++ b/doc/asm/macro.htm @@ -35,7 +35,7 @@ arguments to them and they can then react to the input using IF-constructs.

When the assembler meets MyMacro it will insert the macrodefinition (the text enclosed in MACRO/ENDM). -

Suppose your macro contains a loop.
+

Suppose your macro contains a loop.

diff --git a/doc/fix.htm b/doc/fix.htm index 46446328..e72867b7 100644 --- a/doc/fix.htm +++ b/doc/fix.htm @@ -19,7 +19,7 @@
  • Usage
  • Options -


    History

    +

    History">History

    • @@ -44,7 +44,7 @@
    The history of RGBFix

    -


    Usage


    +

    Usage


        rgbfix [options] image[.gb]

    Options are preceded by a dash (-) and go as follows:
    @@ -59,7 +59,7 @@ Options are preceded by a dash (-) and go as follows:
    I have chosen to release it in the ASMotor package instead from now on. Its usage has changed a bit from that of GBFix for the sake of consistence with the other ASMotor tools. Being part of RGBDS means RGBFix' distribution now follows the same rules as the rest of the ASMotor package. GBFix still follows its own rules.
    -


    Options

    +

    Options

    How to use the various options.


    Titlefield

    diff --git a/doc/geninfo.htm b/doc/geninfo.htm index a1ecbfe0..9d25b4a6 100644 --- a/doc/geninfo.htm +++ b/doc/geninfo.htm @@ -24,7 +24,7 @@
  • The Documentation
  • History -


    BlahBlahBlah

    +

    BlahBlahBlah

    The ASMotor package (xAsm, xLink, RGBFix, examples and documentation) is freeware and distributed as is. The author retains his copyright and right to modify the specifications and operation of the software without notice.

    In other words this means I encourage you to... @@ -43,7 +43,7 @@ you choose to use ASMotor you do so at your own risk.

    I am happy to say that xAsm and xLink use PMODE/W as DOS-extender for the MS-DOS port! This means fast assembling of your sourcecodes. A lot faster. PMODE/W is a drop-in replacement for the bulky DOS4GW. If you are a programmer you should check out http://www.di.net/pmw
    "PMODE/W is Copyright (c) 1994-1997, Charles Scheffold and Thomas Pytel. All rights reserved."
    -


    The Author

    +

    The Author

    Any questions? Write me!

    Carsten Sorensen
    @@ -52,12 +52,12 @@ Guildford
    Surrey GU2 6QW
    United Kingdom

    -e-mail:
    +

    e-mail:

    surfsmurf@matilde.demon.co.uk (private)
    csorensen@ea.com (work)

    Get the latest version from my web page at http://www.matilde.demon.co.uk -


    Introduction

    +

    Introduction

    ASMotor is a package currently consisting of three programs (xAsm, xLink and RGBFix) originally designed for development on the Gameboy hand-held video-game console by Nintendo but recently it has moved towards being a target independent shell for making development of new assemblers for different processors easier.
    @@ -71,11 +71,11 @@ Don't like it? Something you'd like to see added? Mail me

    The assembler and linker are written entirely in ANSI C using Bison for the parser. I try to maintain two pre-compiled ports of ASMotor, one for the MS-DOS environment and one for Linux. Bison is a GNU tool (compiler-compiler) tailored to aid in the development of compilers which you will need if you want to compile it afresh.
    -


    Installation

    +

    Installation

    Anywhere on your HD will do. For maximum enjoyment I recommend adding the directory to your path. Alternatively you can run it from a floppy.
    -


    The Documentation

    +

    The Documentation

    The documentation only comes in one flavour. HTML. This has several advantages for me

    -


    History

    +

    History

    diff --git a/doc/lib.htm b/doc/lib.htm index f48faee1..5c597033 100644 --- a/doc/lib.htm +++ b/doc/lib.htm @@ -19,10 +19,8 @@
  • Usage
  • The commands -


    -
    -
    -History

    +
    +

    History

    • The history of ASMotor
    @@ -39,12 +37,10 @@

    -

    Usage

    +

    Usage

        xlib library command [module1 module2 ... modulen]
    -

    -
    -The Commands

    +

    The Commands

    The command specified after library on the commandline tells xLib what to do.

    The following commands are available:

    The history of xLib
    diff --git a/doc/link.htm b/doc/link.htm index ed1aac76..71e51ad0 100644 --- a/doc/link.htm +++ b/doc/link.htm @@ -22,10 +22,8 @@
  • Operation for Gameboy small mode
  • Operation for Psion2 relocatable modules -


    -
    -
    -History

    +
    +

    History

    • @@ -79,7 +77,7 @@ resolve, things would go horribly wrong.


    -

    Usage

    +

    Usage

        xlink [options] linkfile

    Options are preceded by a dash (-) and go as follows:

    @@ -92,9 +90,7 @@ resolve, things would go horribly wrong.
    zHX : Set the byte value (hex format) used for uninitialised data (default is ? for random)

    -

    -
    -The Linkfile

    +

    The Linkfile

    A linkfile is used to tell xLink which objects to include and what the outputname should be. It is in plain ASCII-format.

        # Linkfile for foobar.gb
@@ -110,22 +106,19 @@ resolve, things would go horribly wrong.
    
     foobar.gb

    A line starting with # is ignored.

    If you use libraries they will only be included if one of the objects actually reference them. This works on a SECTION level and not on a module level. This means that when you write libraries you can put each subroutine in its own SECTION so only the relevant bits are included. -


    -Operation for Gameboy (-tg)

    +

    Operation for Gameboy (-tg)

    Sections created with HOME in the assembler are placed in the GB bank #0 (the fixed bank $0000-$3FFF) in the order they are loaded from the objectfiles specified in the linkfile. So you want the first file in the linkfile to contain your header. CODE/DATA sections are placed in any bank other than #0. This means you have absolutely no control over which sections goes where. This insures minimal slack (unused bytes) at the end of each bank in the image.

    Currently the linker doesn't calculate the GB checksums. You must use RGBFix to do this.

    -


    -Operation for Gameboy small mode (-ts)

    +

    Operation for Gameboy small mode (-ts)

    Small mode forces all DATA/CODE sections to be of type HOME and increases the HOME section size from 16kB to 32kB. This also means that CODE/DATA/HOME sections are written to the final image in the order you have specified in the linkfile.

    Currently the linker doesn't calculate the GB checksums. You must use RGBFix to do this.

    -


    -Operation for Psion2 relocatable modules (-tp)

    +

    Operation for Psion2 relocatable modules (-tp)

    This is a fileformat for the Psion2 that allows you to load your code into where ever there's any free space. The only sections types allowed are HOME, DATA and BSS. All CODE and DATA sections are written to the output file in the order specified in the linkfile. The BSS are actually then expanded to DATA sections filled with zeroes and appended. This might change later.
    The file looks like this (all values are big endian): 

    diff --git a/doc/rgb0.htm b/doc/rgb0.htm
index 790901e8..5272bec5 100644
--- a/doc/rgb0.htm
+++ b/doc/rgb0.htm
@@ -20,14 +20,14 @@
 	
  • Rpn Data
 
 
    
-

    Background
    
+
    Background
    
 
    I developed the RGB0 fileformat mainly because I needed a suitable dataformat to hold the output from xAsm that was powerful to accomodate all the features I needed and also would make it easy for me to add
 new ones.
 The reason for documenting it is so people can write converters between it and other formats. Perhaps even develop other compilers for it?
    
 
    
 The RGB1 fileformat saw the light of day with the V1.02 of the old RGBDS release because of the addition of fixed sections.
    
 The RGB2 fileformat emerged because I needed to add support for big endian CPUs.
-

    FileStructure
    
+
    FileStructure
    
 LONG is a 32-bit integer stored in little-endian  format (Intel)
    
 BYTE is an 8-bit integer
    
 STRING is a 0 terminated string of BYTE
    
@@ -93,7 +93,7 @@ Down to business...
    
             ENDR
         ENDC
     ENDR
    • -


    Rpn Data

    +

    Rpn Data

    Expressions in the objectfile are stored as RPN. This is an expression of the form "2 5 +". This will first push the value "2" to the stack. Then "5". The "+" operator pops two arguments from the stack, adds them, and then pushes the result on the stack, effectively replacing the two top arguments with their sum. In the RGB format RPN

    The history of xLink