--- In David Hawkins <> wrote:
>
> Hi Yan,
>
> > What I'm seeing is that 32 bit reads work if they're aligned on 16-bit
> > boundaries, 8 bit reads work if they're on 16-bit boundaries, and 16
> > reads don't work regardless of boundaries.... (Yes, it makes no sense
> > to me either. I'm not discounting the possibility that I am doing
> > something unbelievably stupid.)
>
> Can you dig up a copy of the TS PEEK/POKE routines
> and try those?
>
> I would assume there is a 16-bit version in there.
> You could see what inline assembly instruction they
> are forcing, and compare it to the version your
> c-coded code is generating.
>
Ooooh boy.
That's what started this whole mess. The particular monster I am
fighting started with the keypad driver. Then various chunks got
grafted in from other programs, with pointers, PEEK/POKE, and other
sundry stuff, all with different programming styles and methods. Now
it's a nearly unmaintainable 1,000 lines of code.
It all worked, though - mostly.
So I decided to "clean up the code" at which point the whole house of
cards came down and the driver quit working.
I'll follow up on the assembler tomorrow. I'll also read up on
readb/writeb and friends; I forgot about those.
--Yan
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|