Home          Features           Downloads          Support          Order          

  Do I have to assemble my program in SXWIZ?

Not if your using SX-KEY.   SX-KEY automatically assembles the
compiled source program when using the SX-KEY DEBUG command
of the RUN menu.  You do have the option of assembling within SXWIZ
to examine the form of the assembled program, the location of data
and also to produce a .SRC hex file, but only if you want to.  One click
on compile and you're ready for SX-KEY.

  How many variables can I have in my program?

Typically about 96 bytes of data is available for the user's program;  the
total data space of the SX is 144 bytes.  This translates into 96 byte,
48 integer or 768 bit variables.  String variables require 1+max character
length. Data space varies with the complexity of expressions and the
number of user functions and subroutines.

  How much program space is available?

SXWIZ requires 15 words of memory as overhead;  SX-KEY requires 153
words for the debugger but this space is only reserved with the DEBUG
directive.  It is highly desirable to keep debug resident even in the target
application since debugging in the field with a laptop is then possible.
The program space of the SX is 2048 words leaving 1880 for user program.

  Where does SXWIZ store my files?

SXWIZ provides a Project option which gives each project a name and folder;
all files generated are then stored in that directory.   The emulator opens to
these folders for download.   There is also a desktop icon pointing to these
files.

  Do I really  need an emulator such as SX-KEY to work with the SX?

Yes and no.   You could compile, assemble and produce a .SXH hex file and
then download it into the chip with an SX programmer such as the Parallax
SX Blitz.  You would not, however, then be able to debug the program.  This
is a frustrating and time consuming way to get a program up and running and
is NOT recommended.   Also, the cost of the SX Blitz is so close to that of
the emulation systems,  it isn't worth the damage.

   Does SXWIZ support emulators other than the Parallax SX-KEY?

Not at this time.   Other emulators such as the Nohau EMULSX-PC are 3 to 5
times more expensive than the SX-KEY, and we are targeting a development
system very low in cost.   The output of the compiler is a standard source using
only native SX instructions, however, and may be compatible for upload into other
systems.

   Does SXWIZ support the Ubicom SX48 and SX52 micros?

No.   SXWIZ supports the  SX18 and SX28.   A compiler for these devices is
under development.  The SX-KEY emulator may be used for these devices.

   Can the emulator-programmer be purchased with the SXWIZ compiler?

No.   SX-KEY can be purchased only through Parallax.   We sell only the
SXWIZ Compiler.

   Are all the chip registers accessable?

Yes and by using Basic directives.   Also SLEEP and WATCHDOG functions.

  How difficult is interrupt coding?

The following is all the code required to set-up a timer interrupt to execute
your interrupt code at 8.5 microsecond intervals.

TIMEBASE 8.5                  'set the timebase in microseconds'
TIMER ON                        

TIMERIPT:                                             'sxwiz reserved label for the timer ipt'

        (your code in Basic)

ENDIPT

 
RB interrupts are just as easy and you do have control of edge and enable
functions in foreground with simple Basic directives.  SAVEREG and RESREG
commands are available to shelter foreground accumulators.  Your only other
concern is that the execution of the interrupt code not exceed the interrupt rate.

 How does SXWIZ display errors in my program?

Errors for syntax, ambiguous symbols, reserved words, and about 150 other
error conditions, flag anything wrong with your program , display a message
on the caption of the screen your using and identify where the error is in your
program by highlighting it.