[A83] Re: "Writing directly to the calculators hardware" - TI contest ru
[Prev][Next][Index][Thread]
[A83] Re: "Writing directly to the calculators hardware" - TI contest rules
Reading, maybe not. But writing, most likely yes. The purpose of that rule
is that they want you to use the ROM routines whenever possible. If, for
example, the ports changed on some future hardware, using ROM routines would
alleviate the problems caused by reading directly to or from the ports.
Consider the 83+SE and the link port: problems between 83+ and 83+SE can be
caused by reading directly from hardware. Also consider the 83+SE and
display: programs writing directly on the 83+ would not write properly if
run at full speed on the 83+SE (part of why the speed is set to slow unless
applications request the increased speed).
In your case, using TI's LoadCPagedInd is probably the best option, as long
as you pre-lookup the address so that you don't have to bcall it each time.
Your major bottleneck is looking up each token, not getting it from Flash.
Note also that you should be able to use the same LoadCPagedInd to read if
the variable is in RAM -- you'll need to adjust the original pointer so that
its page matches the criterion for RAM pages posted earlier.
-----Original Message-----
From: assembly-83-bounce@lists.ticalc.org
[mailto:assembly-83-bounce@lists.ticalc.org]On Behalf Of Hyperbyte
Sent: Saturday, July 07, 2001 4:28 PM
To: assembly-83@lists.ticalc.org
Subject: [A83] "Writing directly to the calculators hardware" - TI
contest rules
Would the custom rompage reading routines be considered
"Wrting directly to the calculators hardware", as prohibited in
TI's app developement contest?
--Peter-Martijn
References: