Open
Conversation
|
Hello! Thank you som much for your work here, I was looking for something simpler to use with my v2.1 display. However, I cannot get it to work for some reason, it seems to always get stuck waiting on the BUSY pin. I know it's not a bad wiring or anything, since Waveshare's official example works just fine. I'm wondering if you could help me with this! Let me know if you need more info! Thank you so much! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
I've spent some time getting a version 2 Waveshare 2.13" working and thought it might be useful to someone else :)
I've seen a few forum posts referencing this repo with 2.13" boards and getting garbled output so I think the v2 boards are fairly common - mine's been sitting in a drawer for at least a year (maybe 2?).
The ram layout/data entry mode setting combo on this controller is a bit crazy, hence the code in display_landscape. I've tried playing with different entry mode settings but I couln't make it match framebutter's native layout as it'd need a MONO_VMSB option which doesn't exist.
I've tried to follow the coding style of the repo.
TTFN
Ant