-
Notifications
You must be signed in to change notification settings - Fork 40
Waveshare compatibility? #17
Comments
Ahh... the more I look into it, the init sequences are different... This is definitely a different use case... I will work to see if I can't get this library to work with this... |
It's not something we'll ever officially support, but I don't mind offering guidance. You're of course welcome to fork this repo and produce a version for the Waveshare boards if you want! The CS pins are mapped to 0 and 1 on the SPI device nodes:
And yes there's a lot of kerfuffle in the init routines for the Inky pHAT- it does some detection of old/new board versions (we switched to a different panel type) and that governs what colours are available. |
I agree Pimoroni wouldn't really want to help with this because they want you to buy their screens.
to
It worked for me with my red screen. I'm not sure about the latest inky-phat update (that adds yellows support etc), I did this before that update. |
If someone can figure out how to make the new Inky library flexible enough to be easily compatible with Waveshare boards, I'd gladly accept a PR. See- https://github.com/pimoroni/inky |
Looks like the spi instruction set is similar/same? (I didn't look too closely), but the inky-phat library is wayyyy better.
I tried to buy a genuine inky phat but adafruit was out, and I live in the US so it was just easier to buy the chinese waveshare einkphat vs waiting for adafruit to get back in stock, or buy direct.
I went into the library and changed the pinouts, but when I try and run anything I get the following:
I figure it's because I changed the cs_pin from 0 (what is 0???) to 8, since that's what the waveshare one uses.
According to the documentation (pimoroni pinout), it appears that the inky-phat uses the the same cs_pin though... so I change it back to 0, and I get the following output after running "python test.py red"
I forgot what I did but at some point (before I reset my cloned repo) I got the programs to execute, however I wouldn't see any change on my waveshare display. It was strange, that it looked like everything was executing properly, except I would see no change. I can't figure out how I got it to that point though...
Anyway, If this is wholly unsupported you can close this issue, otherwise I feel like it might be a worthy endeavor for people stuck in my situation. At least, a fork might be doable if it's impolite to make this library compatible with a competing product.
The text was updated successfully, but these errors were encountered: