Re: A86: 86 interrupts?
[Prev][Next][Index][Thread]
Re: A86: 86 interrupts?
TGaArdvark@aol.com wrote:
> First of all, that's not the best proof. Silent linking, CBL com-
> munication, and TI-Basic variable transfer are also disabled
> during graphing. Second, you may be right about it being
> _getkey. I truthfully have no clue what routine it is. But if
> it is _getkey, then _getkey happens to be the linkport
> interrupt he was looking for. I didn't say there was a
> separate linkport interrupt. I just said there was one.
> Thirdly, what does _getkey have to do with the link and
> why would TI have it handle the linkport?
Well, something is obviously playing with the link port in the
middle of my program. I connected the calculator to a simple
AVR program setup to acknowledge all incoming bits and then to
send what the other calculator is doing to the || port.. a
makeshift logic analyzer program is showing that something is
DEFINITELY playing with the link port, because behavior is
extremely eratic. _getkey is never called by my program except
to pause but I am not attempting any kind of link activity
when the program is paused (waiting for a key) and the link
port should be inactive ($C0). I'll give the di a try and if
that fails I'll replace all of the _getkey calls with my own
lame pause routine that uses GET_KEY.
I have a feeling aardvarc is wrong... if there were a link port
interrupt there would be some kind of masking in the ROM link
port routines to prevent it from being called mid-transfer.
But something has to be messing with the link port in my
program...
Anybody know what _getky returns? Is it the same thing as
GET_KEY?
Bryan
Follow-Ups:
References: