I tried the microchip website, but it didn't return the 18F45J10 in the list. Have requested samples, and I'll be placing the order for the screen soon
Thanks Henrik
I tried the microchip website, but it didn't return the 18F45J10 in the list. Have requested samples, and I'll be placing the order for the screen soon
Thanks Henrik
Scampy, Let me ask you a question if you don't mind. Why do you need 2 I2C buses? You cant use them at the same time? Just connect the I2C DS1307 RTC chip and the display that uses SPI on the same clock and data lines? It is doable you know..
Dave Purola,
N8NTA
EN82fn
Confusion Dave, just confusion..
I took advice from a well known and respected forum where nearly each post advises the poster to ready the datasheet
I was looking at using a different display that use the SPI protocol, and it seems that the data and clock lines on a MSSP module are shared and the datasheet states that you have to run either / or. Hence the assumption that getting PIC with two independent MSSP's, one for the i2c and the other for the SPI was the logical way forward. That was before I was reminded that PBP SPI and i2c comms are software driven and thus I could use any other digital pins... it doesn't have ti be the hardware MSSP.
That's kind of what I was aiming at. How ever, SPI usually has an CE line to enable comm to the host. I was thinking along the lines of using the same DATA and Clock lines for both devices. With the CE disabled to the SPI device you would then communicate to the I2C device. I have done this in the past mixing SPI and I2C memory devices.
Dave Purola,
N8NTA
EN82fn
Bookmarks