Hi,
PBP uses a software based I2C so it does not actually matter if your chip has an onboard hardware I2C. It will never use it.
Hi,
PBP uses a software based I2C so it does not actually matter if your chip has an onboard hardware I2C. It will never use it.
Regards
Sougata
Thanks Sougata,
This is what I thought since I use a 12F675 and a 24LCxxx memory via I2C and this PIC has no specific I2C interface (...and, of course, it works).
So what is the "advantage" or simply the reason for certain PICs to have a I2C interface?
Roger
well, usually faster than most software solution, usually provide interrupts triggers, etc etc etc. Same for USART (HSERIN/HSEROUT) against SEROUT/SERIN etc etc.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
...just try to code a slave-I2C !
Then you will see, what advantages a hardware-modul can give to you !
...and it gives you so much performance, if you use the hardware in an intelligent way!
PBP 2.50C, MCS+ 3.0.0.5, MPLAB 8, MPASM 5.14, ASIX Presto, PoScope, mE mikroBasic V7.2, PICKIT2
Somewhere out there, is a site with practically complete I2C-slave code, uses the hardware and PBP to handle things. Apparently it works like a champ. A 2nd PIC18F452 is slave-I2C programmed to act just like a 24LC256 and it's accessed by the 1st 18F452 using PBP's I2C commands. Wish I remembered where that was...
Many of us have done this but for professional reasons we are unable or unwilling to share the code. However, Robert Soubie detailed his adventures with I2CSlave using Melabs PICBasic, and posted all his code here...
http://www.astrosurf.com/soubie/pic_as_an_i2c_slave.htm
Well done Robert!
Hi Melanie,
i tried Roberts I2C Slave routine, but it is not clear how to access the Slave with I2CREAD / I2CWRITE with Melabs PBP from the Master.
In the I2CREAD and I2CWRITE commands are also "address" parameters given, is this the same to be used as the parameter RXBuffer(0)?
Does any one have an exmaple for me?
Regards,
Ralf
Bookmarks