Skip to content

U8G2 HW SPI breaks after update from 2.6.2 to 3.6.0 #1733

Discussion options

You must be logged in to vote

Gotta say that I'm pretty stumped now. No issues with other SPI users so there still must be something specific about this use case. I'm thinking it might not be the protocol so much as something else here.

SPI interfaces normally have a CS, yes? Are you sure the CS pin is disabled until the GFX lib starts communicating? There might always be some glitchiness as the SPI unit comes online and takes over the pins, but it would be ignored since CS would be deasserted until a real command comes. Can you capture the CS pin as well and see that it's disabled until the 1st valid bit of data?

Replies: 1 comment 15 replies

Comment options

You must be logged in to vote
15 replies
@mattthegamer463
Comment options

@earlephilhower
Comment options

@mattthegamer463
Comment options

@earlephilhower
Comment options

Answer selected by mattthegamer463
@mattthegamer463
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants