The RMW problem is solved but now I have a new problem with a Pic16f819 and I need some door pins to be used as inputs for buttons.
Unfortunately it is currently unable to read the state of some single pin, there is also the provisional possibility of achieving this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wrote test program.
It does not read the button on Portb.0 but on Latb.0
I also noticed a strange behavior, if you take off the line code 25 (portb.2=0) support is not activated RMW !!
I hope I explained myself well.
Thank you
We are looking at two issues in the recent RWM implemention.
So, for now ( as I am travelling ) use ASM to resolve. The ASM will read the port.bit state not LATB. I am sure this this will lead to other issues but you should be able to resolve by writing the state of the port.bit to the LATB variable.
I have more work to do to ensure the RWM is 100% solid and I thank you for your patience.
#chip16F819,8#optionexplicit#optionShadowregisterPORTB#definePULSPORTB.0'p.6-inputpulsantedirportb.0in//IF PULS = 1 THEN BTFSCPORTB,0;TestactualpinstateofPORTB.0GOTOPORTB0_HIGH;SkipifPORTB.0ishighPORTB0_LOW:// Do thingsPORTB0_HIGH:// Do things// Remainder of code
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The RMW problem is solved but now I have a new problem with a Pic16f819 and I need some door pins to be used as inputs for buttons.
Unfortunately it is currently unable to read the state of some single pin, there is also the provisional possibility of achieving this.
Post example code to show the issue.
I wrote test program.
It does not read the button on Portb.0 but on Latb.0
I also noticed a strange behavior, if you take off the line code 25 (portb.2=0) support is not activated RMW !!
I hope I explained myself well.
Thank you
We are looking at two issues in the recent RWM implemention.
So, for now ( as I am travelling ) use ASM to resolve. The ASM will read the port.bit state not LATB. I am sure this this will lead to other issues but you should be able to resolve by writing the state of the port.bit to the LATB variable.
I have more work to do to ensure the RWM is 100% solid and I thank you for your patience.
Okay there is no problem I don't have something urgent, I wait for the definitive MRW implementation to be placed.