You are here: Home DOCUMENTATION information SBASIC Manual - Page 8

Technological Arts Inc.

Your Shopping Cart

Your Cart is currently empty.

SBASIC Manual - Page 8

Article Index
SBASIC Manual
Page 2
Page 3
Page 4
Page 5
Page 6
Page 7
Page 8
Page 9
Page 10
Page 11
Page 12
Page 13
Page 14
Page 15
Page 16
Page 17
Page 18
Page 19
Page 20
Page 21
Page 22
Page 23
Page 24
Page 25
Page 26
Page 27
Page 28
Page 29
Page 30
Page 31
Page 32
Page 33
Page 34
Page 35
Page 36
Page 37
Page 38
Page 39
Page 40
Page 41
Page 42
Page 43
Page 44
Page 45
Page 46
Page 47
Page 48
Page 49
Page 50
Page 51
Page 52
Page 53
Page 54
Page 55
Page 56
Page 57
Page 58
Page 59
Page 60
Table of Contents
Index
All Pages

     SBasic User's Manual     SBasic Version 2.7              Page 8
     Printed:  December 5, 1999
     where xxxx is either 6811 to generate output code for the 68HC11 MCU,
     or 6812 to generate output code for the 68HC12 MCU.  If you don't
     supply the /m option, SB will generate code for the default MCU, the
     68HC11.

     The differences in output code caused by compiling for the two
     machines mostly concerns the library files used.  See the discussion
     below on library files for more details.

     Certain variations of the 68HC12, notably the 68HC912B32, use on-chip
     firmware to take over the MCU's interrupt vector table.  Similarly,
     some 68hc11 chips include masked ROM firmware (such as BUFFALO) that
     also takes over the vector table.  In both these cases you need to
     prevent SBasic from trying to set up a vector table on the target
     machine.  You can prevent SB from creating an interrupt vector table
     by using the /i option.  The format of this option is:

          /i

     If you use the /i option and your SB program must use interrupts, you
     will have to add SB code to prepare the appropriate RAM-based jump
     table.  Refer to the Motorola literature on your target MCU for
     details.

     Note that the /i option surpresses ALL changes to the vector area,
     including the reset vector.  SB programs compiled with the /i option
     must use some resident firmware, such as BUFFALO, to transfer control
     to the start of the program.