Semi-random pixels on SSD1322 - how to fix? about luma.oled

[TheoVDBerge]

As silly as it sounds, taking off the power and restarting it was one of the first things I tried to do. Maybe I plugged it back in too quickly, because I just tried to run nit just now (after letting it sit unplugged since I wrote this post), and it is back to normal again.

Sorry and thanks for you time!

[thijstriemstra]

However, the screen worked normally prior to this,

When? how? under what (other)circumstances?

[TheoVDBerge]

Thanks for your reply and apologies for the lack of details!

So, I have a SSD1322 that I have connected using a 4SPI protocol to my Raspberry Pi Zero WH. I have wired it according to the documentation here, for which many thanks again.

Using this set-up I have been able to print some text on the screen just fine, hence this is what I consider 'prior' to the above case. However, (I think) what caused this issue is that during prototyping I moved around the screen a bit, which caused one of the jumper cables (I believe it was the power-in jumper cable from the Raspberry Pi) to temporarily disconnect. Since then the screen has been stuck on semi-random pixels and a bit of what I previously had programmed to be displayed on the screen.

I also would like to highlight that I do not think there is anything wrong or missing with the library, but maybe due to the cable temporarily disconnecting something went wrong in the memory or internals? Given this GitHub page, I was hoping you (or someone else) might have run into a similar issue before and would know how to 'reset' the screen, as I did not find much information about it and I am relatively new to tinkering with such electronics.

Thank you again!

[thijstriemstra]

what caused this issue is that during prototyping I moved around the screen a bit, which caused one of the jumper cables (I believe it was the power-in jumper cable from the Raspberry Pi) to temporarily disconnect. Since then the screen has been stuck on semi-random pixels and a bit of what I previously had programmed to be displayed on the screen.

You tried taking off the power and restarting?

, but maybe due to the cable temporarily disconnecting something went wrong in the memory or internals?

Sounds likely.