Wouter van Ooijen writes:
> The only thing this macro does is what is in its body:
>=20
>     movwf       (arg^0x80)
>=20
> It inverts the 8th bit (assuming the LSB is the 0th) of the supplied=20
> address and writes W to that address. What is the purose? To write to an=
=20
> address that is in bank 1 without the assembler complaining (I dunno=20
> about gpasm, but mpasm would complain) about the address not being in=20
> bank 0. It does NOT set the bank bits!
>=20

	Ah! I see what you mean. Inverting the MSB of the
address does actually give you the range of 0x8x, but it doesn't
set the bank. I had convinced myself that it got aroundhthis
need for at least that one operation.

	Yes, gpasm complains when you write outside the bank.
You can suppress the message but you still have the bad code if
you insist on not correcting the underlying problem.

> If you want it to set the bank bits, just add a line that does so in the=
=20
> body of the macro.

Thank you.

> (But why use assembler anyway? These days there are free C compilers, and=
=20
> there is Jal, and if that is not enough there is Basic, Pascal, ...)

	That is a long story but the short version is I am
working on that. My OS of choice is Linux. As a computer user
who happens to be blind, I need the screen reader which is an
open-source part of Linux. I've been trying to get gnome which
also does have a screen reader to function so as to try mplab-x but
that has been an up-hill slog so far.

	Mac's OSX also has a good screen reader which is part of
the OS and I down-loaded mplab-x and immediately ran in to a
total inability to even start the installation process probably
due to java issues.

	If I ever saw something like gcc and the gdb debugger
able to program PIC's, I would know that I had died and was in
the Promised land. The interface is ASCII and works on anything
from a KSR33 to the latest flat-screen monitor. Nobody cares
what you developed it on if it ultimately works when installed.

	Just for information, Linux and Mac OSX are
blind-friendly in that there are screen readers provided as part
of the OS. Since both are unix-based, it's easier to make screen
readers work but there are issues when things get very complex
such as some web design and java applets which assume everybody
uses a mouse or bit-mapped images are valid text. They don't and
they aren't.

	Windows is another beast alltogether. Screen readers
must be bought separately for incredible amounts of extra money
and you, the customer, get to finance their bug fixes.

	Just kidding about the KSR33. I actually carried one of
those across a room and I fancied the whole building tilted as I
moved. My spine was relieved when I set it down.

Martin
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.