UNKNOWN OP 53

[olzeke51]

DEMO mode, checking out a program
It compiles okay but when I <RUN> it I get this:
/Analyzing F:/Coridium/FORTH/forth_tib_0730feb27.bas
/done
/*** WARNING !!! ARM is not connected !!! ***DEMO MODE*** loading PC...
/"ARMbasic[9.36f] on the PC Copyright 2015, Coridium Corp.
/"
/"... 1.18K code 0.90K data programmed
/
/"
/
/Executing on the PC...
/UNKNOWN OP @ 100: 53
/
/... Finished on the PC in 0 ms
inserting a Print "linennn" for debugging purposes - The "OP @ 100" would change.
I got it down to this SUB - TOB$, I -have been Dimmed. uart is a CONST
'
SUB F_TYPE 'outputs the TOB$ to the terminal [null terminated]
I=0
WHILE TOB$(I) '‘ is not a NULL
TXD(uart) = TOB$(I)
I+=1
LOOP

END SUB
'
'any ideas ??
'******************************
turns out the TXD() is causing the error
an RXD() further down causes an OP of 52 that is unknown !!!!!!!
** so now what??
I would have expected a flag message possibly - the Help file doesn't mention any restrictions on the TXD/RXD type of statements.
********MORE INFO
I put a zero in place of the CONST uart -- and I still get the unknown op 53
the usage of TXD0 instead of TXD(0) doesn't give the 'unkown'!!!!

[basicchip]

/*** WARNING !!! ARM is not connected !!! ***DEMO MODE*** loading PC...
/"ARMbasic[9.36f] on the PC Copyright 2015, Coridium Corp.
/"

That is the key, the PC emulator does not do any IOs

You don;t seem to be connected to the ARM board

[olzeke51]

I was well aware of being in DEMO mode.
In previous 'demo' programs , there would be i/o statements
displayed on the screen.
"

Executing on the PC...
set OUT(9)=1


... Finished on the PC in 0 ms
'
I will try and be more specific in identifying my issue - which was at the bottom of my post
** so now what??
I would have expected a flag message possibly - the Help file doesn't mention any restrictions on the TXD/RXD type of statements.
********MORE INFO
I put a zero in place of the CONST uart -- and I still get the unknown op 53
the usage of TXD0 instead of TXD(0) doesn't give the 'unkown'!!!!
'
The ISSUE I was reporting was
"UNKNOWN OP @100 :53" and 52
'
1)What/why is there an unkown op code that is compiled okay,
but when it 'Runs' it reports an error.
2)Why would TXD0 be okay in a program
BUT not TXD(0) ??? [the updated terminology!]
"The compiler is also backward compatible with the syntax -- TXD0 = char , TXD = char , or TXD1 = char"

[olzeke51]

I was checking the overall syntx/correctness of my program, before I did downloads.
I tend to mix old-Basic with your ARMbasic.
'
but I am still confused as to why one style of the command(legacy) works and the
newer command statement causes the unknown op.
'
the end result is that I must use legacy statements.
If I was to create & demo a program using two UARTs - I would be in trouble.
Gary

[basicchip]

We use the PC emulator to test the compiler, and publish it as a demo for people to evaluate the BASIC

Some people as you have use it to debug programs. We tend to debug on real ARM boards rather than on the PC.

But it was never meant as a complete BASIC for the PC, as there are lots of alternatives there.

[basicchip]

but I am still confused as to why one style of the command(legacy) works and the
newer command statement causes the unknown op.

well as TXD(x) or RXD(x) on the PC don't do anything useful, it was never tested, and is broken. Could it be fixed, sure, but how would you handle RXD, what character should it return, Yes TXD could show what was to be sent

Next would be how to handle interrupts. No real way to do it unless we try to emulate the actual ARM hardware. That is a really BIG task and not terribly useful, as timing would be different.

We also don't emulate writing to Flash, or peeking and poking ARM registers.

[olzeke51]

Thank you, now I know what the tools will do, and can use it appropriately.
Gary Olzeke