Needs (multiple) reset to start - possible solution.

[nebelgrau77]

I've tried the driver with an ST7735 on a breakout board, and it always seemed like I had to be very lucky to see the actual screen content, not just the backlight. I always blamed it on the poor connection on the breadboard, loose jumper wires and such.
Now I'm trying it on the Adafruit PyBadge, though, where the display is firmly attached to everything else. It takes two-three resets after flashing the board to see the desired content, same after unplugging/shutting off the board. Basically it won't just work after power up.
I had a similar problem with the SSD1306 and the solution was a tiny 100 ms delay at boot, so that the I2C could start correctly.

With that, the problem ceased to exist. And it seems to be helping here as well: https://github.com/nebelgrau77/pybadge_display_test

Have you ever encountered this problem?

[sajattack]

I think we used to have a longer reset and it was shortened by a contributor.

[sajattack]

Nevermind, I guess I'm mistaken. It looks like delays for hard reset were added, and we already have delays in software reset which have never changed. Perhaps hard reset delays could be lengthened.

[nebelgrau77]

OK, I will try this "small delay" approach on the breakout board display as well, and report back. Maybe it's just something that can be solved like this, so it could be a note in the readme file, and that's it.

[LuckyTurtleDev]

Have a similar issue. After flashing the display of the pybdage does not work until pressing reset.

[sajattack]

Have a similar issue. After flashing the display of the pybdage does not work until pressing reset.

Probably an issue with the bootloader on the pybadge

[LuckyTurtleDev]

Probably you are right. Is their an option to force a display reset without destroying the display struct?

[sajattack]

init calls hard_reset on the display