-
Notifications
You must be signed in to change notification settings - Fork 126
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
Pi stuck after flashing .zip/img onto SD #73
Comments
That lightning icon on the top right corner means that your Raspberry Pi is not receiving the right voltage, which generally means it's underpowered: you should use a better power source! |
Have the same problem on my pi 3b+ (he probably also uses the same device). I'm using the official power supply. Probably it just lacks support for the new pi. |
Yea i'm also using the pi 3b+ with the original charger, i guess every OS has to get updated to 3b+ since the normal 3 versions doesn't seem to work on the 3b+ yet.. I guess we're going to have to wait a couple weeks for that |
No, it's only one OS that has to be updated. That's ThreadX which is the primary OS running on the primary CPU (dual core VideoCore IV). The ARM cores running the secondary operating system (eg. Linux) are only guests. All the hardware initialization is done on the primary CPU cores by the primary OS. This one lives on the FAT(32) partition usually mounted as But for the new Ethernet chip also Linux support is needed (both driver and Wi-Fi then of course also needs new firmware. See the pending PR on |
Addendum: ThreadX is contained in these files:
If you use latest Raspbian Stretch image to copy files over please exclude the other files especially cmdline.txt since incompatible. |
Closing due to the same topic #75 |
Whenever i finish flashing the zip/img onto the Pi and boot it up i get stuck on this screen and its been over 20 minutes, isn't it working for me, or am i doing something wrong?
This is my screen https://i.gyazo.com/889d4342e04a7f4161069ae47efcc96f.jpg
The text was updated successfully, but these errors were encountered: