>>  Here is the result of running the command
>>    "xwisp.py COM1 target=16f628 verbose go tut2_1"
>>
>> C:\Program Files\XWisp\xwisp.py COM1 target=16f628 verbose go tut2_1
>> XWisp 1.08, command line mode
>> Traceback (most recent call last):
>>   File "C:\Program Files\XWisp\xwisp.py", line 3563, in ?
>>     XWisp_Main()
>>   File "C\Program Files\XWisp\xwisp.py",line 3560, in XWisp_Main
>>     Wisp_Line().Interpret()
>>   File "C\Program Files\XWisp\xwisp.py",line 3180, in Interpret
>>     self.Execute( Command )
>>   File "C\Program Files\XWisp\xwisp.py",line 3162, in Execute
>>     exec( 'self.CMD' + Command.upper() + '()' )
>>   File "<string>", line 1
>>     self.CMD_TARGET-16F628()
>>                          ^
>> SyntaxError:  invalid syntax
>>
>>
> try "xwisp.py COM1 target 16f628 go tut2_1"


Wow.  Just Wow.  That's some error message!

In the course of that MacOS AVRA droplet I developed, I discovered
that the avra command line:
    ./avra -D ATTINY11=ATTINY85 ../ledmatrix.asm
generates the error message "Bus error", which really means "You
can only -D things to numbers; didn't you read the manual?" (it
attempts to print filename and line number, and since it hasn't
gotten to the file yet, these aren't valid pointers), and
I guess the python traceback is what you get if you get a similar
error in a nice interpreted language.  But still...

BillW
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist