This request must be asked at least once every week. Please do a search on the forum for 'I2CSlave' or just the word 'Slave' and you will eventually find links to PBP Code.
This request must be asked at least once every week. Please do a search on the forum for 'I2CSlave' or just the word 'Slave' and you will eventually find links to PBP Code.
Thank you Melanie. I know this has been beaten to death. All the info I have uncovered while searching 'I2Cslave' and 'Slave' etc... Just explains implementing it using the built in SSP. The examples called I2CSlave.bas and I2CMast.bas are great examples but the I2CSlave.bas (unless I am mistaken) uses the SSP of the 16F877. This routine is looking for the SSPIF to be set so it knows to check to see if there is new communications for the slave. Without an SSP I don't see how to implement a slave using this as an example. I'm sure I'm missing something important here. I'll keep studying this. Thanks.
I wouldn't say there are LINKS TO PBP CODE if there wasn't any...
http://www.picbasic.co.uk/forum/show...ighlight=Slave
Hello Melanie,
MITH just doesn't want to realize, that an 16F84 can't run as a I2C-slave !
There is no software-solution for I2C-Slave for any PIC!
I disagree, everything is possible. It's just not one of those COPY/PASTE solution.
Usually, those who did will keep it for them. As GLCD and such other.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
BigWumpus, it's not that I don't want to realize it. It's that I didn't realize it. I went back again to the link that Melanie sent and looked line by line at the code there and now I understand the limitations to the 16f84. I wasn't trying to be a burden. I thought when I etched my board that the 84 would be adaquate but it just isn't up to the task.
Thanks again Melanie. Your posts are always the most educational. I especially like the RTC example!
Mith
Bookmarks