I switched the project type to "public" and it appears to clone correctly for me. Do you get an authentication error when you type the following?joan wrote:How do you access the source code? It may be a cookie problem (I disable all cookies by default) but I'm not familiar with gitlab and nothing I click produces anything useful.
I got mine working on a Dell XPS 13 running Ubuntu. I just tested bit banging so far. The I2C support is disappointing because it's not really "built-in", but requires a whole bunch of additional software. I will be testing it when I have some time and report by here when I have some results.tenochtitlanuk wrote:Perhaps off-topic on a Pi forum, but relevant....
I've been trying to use the Adafruit ft232h breakout from a fully up-to-date Linux Mint installation on a desktop.
It steadfastly refuses to be seen as a usb or tty device.
The installation followed Adafruit's instructions, and the Adafruit_FTDI and ftdi1 installs both worked.
At present Adafruit have been unable to help. Web searches suggest using modprobe to remove two modules- but breakout board is still 'invisible'.
Have you got yours working on a Lnux machine? Did you have any problems.
I've yet to try it directly from one of my Pis, and am a bit disheartened. In the past I've used USB bords like the Bitwacker with no problems...
That sounds like a good idea, but it's beyond what my needs are for this code. I can humbly suggest that you or a like minded developer please make such a change, do a pull request and I'll add it to the library.danjperron wrote: ↑Tue May 14, 2019 6:22 pmThanks, what about utf-8 and multi-language.
I was stuck with some library and I had to make my own also. I changed one libray that I found and create a table of characters using utf-8.
To minimize the cost in rom size you could specify which character you want.
Fonts are a tricky topic and I just took the easiest route with this code. There are licensing issues and data format issues. I'm sorry, but I don't have a good answer for you. I've seen websites that can dynamically generate a font, but it will probably not come out in the right format to use my existing code. There are other OLED libraries (at least for Arduino) which offer much better font support. Converting the code to run on Linux/RPI is easy since the only functions you need to change are to access the I2C bus.DarkElvenAngel wrote: ↑Wed May 15, 2019 12:24 amI wanted to thank you for sharing your library!
I have a few questions how do you customize the font? I would just want to add some custom symbols. Is it best to define a new font or extend one that exists?
As I've never used an OLED until yesterday I was wondering how difficult is it to add support for the SSD1327? Or is this deserving of its own thread?
All in all I really like this code it's simple and doesn't have all the bulk others have, Thanks again for sharing.
Thanks for the tips, I was only looking to make symbols in this case not port any fonts per say. Maybe I need a simple way to add a glyph to the frame buffer?bitbank wrote: Fonts are a tricky topic and I just took the easiest route with this code. There are licensing issues and data format issues. I'm sorry, but I don't have a good answer for you. I've seen websites that can dynamically generate a font, but it will probably not come out in the right format to use my existing code. There are other OLED libraries (at least for Arduino) which offer much better font support. Converting the code to run on Linux/RPI is easy since the only functions you need to change are to access the I2C bus.
I haven't used the SSD1327 before, but I was a bit curious about it. I support color OLEDs in my other project:
Most LCD/OLED displays have a very similar command set, so I would think it would take very little effort to change my SPI_LCD project to support the SSD1327.