my ic2 oled ssd1306 shows a block char (like 178) when sent char above 127, used it to build big numbers (portrait view), used a tca9548a on 1 i2c bus to drive 4 oleds.
The I2C multiplexer is one of the ideas I had in mind when I said "there are ways around the I2C address issue". I like the idea for using block chars, reminds me of creating box menus using ASCII characters in DOS programs back in the 90s. I'm currently looking at using bitmap fonts to create large numbers. I only need digits so looking at creating custom images and blit then to half the screen at a time giving values up to 99.
Another benefit of the SPI interface is that the coms are normally a lot faster, which means that you can get more fps. If you 'play games' and limit precisely which areas of the screen you draw/show, you can get very high fps.
my ic2 oled ssd1306 shows a block char (like 178) when sent char above 127, used it to build big numbers (portrait view), used a tca9548a on 1 i2c bus to drive 4 oleds.
The I2C multiplexer is one of the ideas I had in mind when I said "there are ways around the I2C address issue".
I like the idea for using block chars, reminds me of creating box menus using ASCII characters in DOS programs back in the 90s.
I'm currently looking at using bitmap fonts to create large numbers. I only need digits so looking at creating custom images and blit then to half the screen at a time giving values up to 99.
Another benefit of the SPI interface is that the coms are normally a lot faster, which means that you can get more fps.
If you 'play games' and limit precisely which areas of the screen you draw/show, you can get very high fps.