ARMweb BASIC compile time
Posted: Thu Dec 06, 2012 4:45 pm
> When I have the usb board connected it spends a lot of time
> (~500ms) printing all the frame2.htm web page basic commands
> on the basictools window. Does it still tie up the arm
> trying to print this output when no usb interface is
> connected?
We have the <?BASIC compile and output of that compile going to the USB for
debug, not sure its worth removing. It could conceivably be turned off when the
Autostart/Security is turned on.
The ARMweb would be held up by strings longer than 16 bytes. We should probably
add interrupt service with a larger buffer on transmit at some point. But the
delay should be only 0.5 msec per character.
I haven't really done any benchmarking on how long it takes to compile a web
<?BASIC command and it has to be done each time its accessed, but that may be
the bulk of the 500 ms. Don't look for that to really improve, there's not much
we can do about it.
> (~500ms) printing all the frame2.htm web page basic commands
> on the basictools window. Does it still tie up the arm
> trying to print this output when no usb interface is
> connected?
We have the <?BASIC compile and output of that compile going to the USB for
debug, not sure its worth removing. It could conceivably be turned off when the
Autostart/Security is turned on.
The ARMweb would be held up by strings longer than 16 bytes. We should probably
add interrupt service with a larger buffer on transmit at some point. But the
delay should be only 0.5 msec per character.
I haven't really done any benchmarking on how long it takes to compile a web
<?BASIC command and it has to be done each time its accessed, but that may be
the bulk of the 500 ms. Don't look for that to really improve, there's not much
we can do about it.