Hi,

Ken Pergola wrote:
<snip>
>Because I make mistakes and I trust MPASM (more than myself) to do the
grunt
>work for me -- I leave RAM access bit decision-making to MPASM.

Well many moons ago, when the 18-series was only little more than an
glimpse
in the postman's eyes, I did to :)

But yes, returning to subject, I did have some very odd problems
originally
when writing code for the 18-series. It turned out that the access/bsr bit
was
not set properly by the assembler/linker. I.e. an variable within the
access
bank still used the BSR for example.
Not findning the exact cause of the problem I had manually add the ,A and
,B where
appropiate. Eventually I found of what was causing the problem, it was an
error in the linker
that did not allow variables in access ram to be shared (UDATA_OVR did not
work
with access ram). Due to the grief that cuased me I have been manually
adding
the bsr/access bit up til recently. However I'm beginning to trust the
linker again
and my code now does not contain any of theese oddities.

/Tony


###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft
Exchange.
For more information, connect to http://www.F-Secure.com/

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body