Well I tried software SPI with MAX7219 and was not impressed at all - updating 32x8 pixels led display was quite slow....
Well I tried software SPI with MAX7219 and was not impressed at all - updating 32x8 pixels led display was quite slow....
I'll just point to MELABS: https://melabs.com/samples/PBP-mixed/spimast.htm That example is what I used as a basis when I first used the MSSP module for SPI (for interfacing the W5100 (search the forum for that code if you want)). See, not a single line of assembly.So if you have simple, clean to understand code for working with MSSP in PBP, I'd like to have a look...
Thanks, but that code is missing SSPBUF declaration?
No.
SSPBUF is the Synchronous Serial Port Receive Buffer/Transmit Register. It's the name of register to/from which you write/read whatever gets shifted out.
Good.
So I have to "learn" to use SPI eeprom 1st, and then use MSSP
By the way, if I leave current setup as is - using I2C, but use PIC running at say 32mhz (instead of current 8mhz), will this result 4x times faster reading speed or not?
Have you measure what clock speed you're getting?
Standard "high speed" I2C clock is 400kHz, maximum clock speed of a Microchip 24C256 when run at >2.5V is 1MHz.
SPI-interface flash chips usually has a maximum clock frequency of at least 33MHz.
Not yet, but will do. Measure what, I2C clock frequency?
Tried modifying code in a way, that only that part of screen is redrawn, which is being updated. For some uses it does helps, but not always.
Bookmarks