Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry Pi Zero W crash during Init #113

Closed
romoromor opened this issue Nov 30, 2020 · 8 comments
Closed

Raspberry Pi Zero W crash during Init #113

romoromor opened this issue Nov 30, 2020 · 8 comments

Comments

@romoromor
Copy link

Hi,

we have Raspberry Pi Zero W ad into this connected epd2in13bc (Waveshare® 2.13 Inch E-ink Screen Display e-Paper Module SPI Interface Partial Refresh Black Red White 212×104).
When we execute script to view something on display for example in a hour after start of Raspberry, all is ok.
But when we leave Raspberry running and do script execution after more than +- 3hours, Raspberry crashed during sending first command to display (without any error message).
epd.init()
Please, what could be wrong?
We have latest version of e-Paper, updated Raspberry, Raspberry is powered by power supply (not from PC USB).

@SSYYL
Copy link
Collaborator

SSYYL commented Dec 3, 2020

Does it come up every time? When did you buy your HAT?

@romoromor
Copy link
Author

Hi, if i set refresh once per day at 12, everyday in that time is Raspberry hard restarted.
syslog etc. are empty from that time. No message about shutdown, only starting of OS messages.
I bought HAT and Raspberry second week of October this year.
Here is screen from monitoring. You can see uptime there. 28.11.2020 was crontab task disabled and in graph are also my two reboots of device - 25.11. 8AM and 27.11.. 3PM.
obrazek

@LoieBensbane
Copy link

There is a known problem (#99 ) with connecting the HATs to pi Zero (the module+display may pull 5V, overvolting the Pi). There is no software solution I know of. A workaround is to use a ribbon cable to attach the HAT to Pi.

Double check your pin connections if you use the cable. VCC should be on 3.3V.

I hope that helps.

@SSYYL
Copy link
Collaborator

SSYYL commented Dec 4, 2020

I think this is a hardware deficiency (#92 )

@romoromor
Copy link
Author

Thanks for answer.
I did connection with cables and first try was successfull,
I leave it for a weekend and if whole weekend will be Raspberyy UP, we can close this issue 👍
Do you know, if will exist some upfgraded revision of HAT hardware without this issue. Or once solution is soldering od 3,3V to 5V pin?

@LoieBensbane
Copy link

Good to hear it's working for you now!

The issue that @SSYYL mentioned (#92 ) has some suggestions for modifying the hardware if you scroll past the "closed this issue" message. I only recognized some of your symptoms from reading other setup issues with Pi Zero. I don't know what I'm doing when it comes to soldering, so if this issue was mine, I would contact Waveshare to see if they can assist more with repair or replacement.

I had meant to order a epd2in13bc HAT (C) for use with my Pi Zero WH, but the smaller HAT was the same price as the larger epd2in9bc module (C) and there was no "action shot" of the screen connected to something for reference size. Shipping took months to get to me, so returning it was not desirable. I wasn't concerned with the pinout until I opened the box and it wasn't a HAT. I had to look at pinout maps for a couple days and read half a dozen tutorials before I felt comfortable plugging the screen into my Pi at all.

@SSYYL
Copy link
Collaborator

SSYYL commented Dec 7, 2020

@romoromor I'm glad your Pi is working. It is a pity that there is no new version at present, But it's already in the plans.

@romoromor
Copy link
Author

Hi, super, display still working without reset. I think, that is a workaround for me:-)
Thanks, you can close this case.

@SSYYL SSYYL closed this as completed Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants