Access pin using index

[Sharky]

I am not really sure that I understand your question.

I assume that you have an change on PORTA interrupt and that you want to know which of PORTA pins that triggered your interrupt.

Maybe you could as the first thing in your interrupt handler read the lower 5 bits of PORTA to see there status.

If I remember it right (don't have my manual here at work)
You can isolate the lower 5 bits and put them into a variable

youvar = PORTA & $1f    ' put lower 5 bits of PORTA into youvar

Then if PORTA.3 is low and the others are high you will get the value 23 in youvar

Hope I remember it right

[arniepj]

I believe this document was off this forum.It describes indexing port bits.

[xnihilo]

I am not really sure that I understand your question.

I assume that you have an change on PORTA interrupt and that you want to know which of PORTA pins that triggered your interrupt.

Maybe you could as the first thing in your interrupt handler read the lower 5 bits of PORTA to see there status.

If I remember it right (don't have my manual here at work)
You can isolate the lower 5 bits and put them into a variable

youvar = PORTA & $1f    ' put lower 5 bits of PORTA into youvar

Then if PORTA.3 is low and the others are high you will get the value 23 in youvar

Hope I remember it right

No, I know what pin triggered the int. I jut can write a routine that will read the incoming data on the specific pin as I don't know at the time I write he routine what pin it will be so I have to use an index but there is no way I can make it work.

[sinoteq]

Hi
Indexing pins is not a totally safe thing to do with PBP. This is a "Extra feature" and works really great with some commands and not at all with others. I have had some really strange results using indexed pins and Pulsin. It would not be a big surprise if While was a no-no.

One other thing, please forgive me if I am wrong, are you sure you are using Interupt? When I look at your code. Unless it is in the interupt handler I would say you are polling the pin to get the status and generate a "software interupt". IF this is the case there are more efficient ways to do that is much faster and will save a ton of codespace.

if (porta.0 == 0) THEN
pin = 0 'set the number of the pin for the score managment (update_scores)
GOTO got_pin 'bypass
ENDIF

[sheepdog]

Will it work via a pointer
SYMBOL PORT_PIN = PORTA

while PORT_PIN.0[pin] = 0
Worth a try I guess, unable to test.

or a loop of
mybyte = portA
while mybyte.0(pin) = 0

By the way re: "You are right, bit shuffling and time wasting"
MOVE?BB PORTA, _B0
AND?BCB _B1, 00Fh, _B1
NCD?BB _B1, _B0
LABEL?L L00002

END
thats the size of the code in assembly using ncd added the "and" to remove msb

[xnihilo]

Hi
Indexing pins is not a totally safe thing to do with PBP. This is a "Extra feature" and works really great with some commands and not at all with others. I have had some really strange results using indexed pins and Pulsin. It would not be a big surprise if While was a no-no.

One other thing, please forgive me if I am wrong, are you sure you are using Interupt? When I look at your code. Unless it is in the interupt handler I would say you are polling the pin to get the status and generate a "software interupt". IF this is the case there are more efficient ways to do that is much faster and will save a ton of codespace.

if (porta.0 == 0) THEN
pin = 0 'set the number of the pin for the score managment (update_scores)
GOTO got_pin 'bypass
ENDIF

Yes, I am using interrupts on PORTA.