rpi-eeprom VS OctoPi

I don't have Pi 5 to check this, but from what I've read, it does not support PPS. And such support is required; otherwise, even with a source that supports PPS, the connection will behave in a non-PPS fashion.

Apparently, cable quality is also demonstrating itself to be a significant factor in the Pi 5 power supply environment.

Regarding both these points:

https://github.com/raspberrypi/rpi-eeprom/issues/497

I should note, I updated the eeprom, USB hub, and network firmware using the images provided from the following repository: https://github.com/raspberrypi/rpi-eeprom. So it certainly isn't a corrupted eeprom chip, and if it was I wouldn't be able to boot the old installation I pulled from my backup drive.

Its a known issue with the current Pi 4 boot firmware. The net install option is trying to look for a keyboard and gets confused with some HIDs.

I was working on a final project for my class and needed an adc. So I ordered an ADS1115 and I had to solder the pins onto it. I've never soldered before, but I tried my best. Didn't look amazing, but didn't look like any pins were getting shorted so I plugged it in to the Pi. I then noticed that my ssh disconnected and couldn't reconnect. Tried plugging in the HDMI and there was no video output. I tried flashing a new OS onto it, didn't work. Tried EEPROM recovery from here and it didn't work. So I think I killed the Pi. It doesn't feel like it's getting warmed up or anything.

See https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md

I try to reset the pi as factory settings (following this github advice). I use pi-imager to set my SD card to lead the pi using USB boot priority and plug a USB key with raspbian OS (no desktop) and now getting green screen when booting. Think that the pi is dead.

I think it was this one:

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmwa...

I had the same problem as you, updated my eeprom and the problem was fixed

Firmware: https://github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.09.03-138a1

You can always find it on GitHub too.

OctoPi, the OctoPrint Pi distribution, uses mjpg-streamer by default and won't work with a Pi camera out of the box if you install a 64-bit OS version.

# out of the box: https://github.com/guysoft/OctoPi/issues

You can download the RC3 image from here: https://github.com/guysoft/OctoPi/issues/796. And use the RPi ImageReady to create the SD card.

I don't do any of that on my machines, I have github actions do that work anytime I change any of my scripts, or the source .img. If you're interested in the project, it is v1pi. This CustomPiOS is also used by Guy to maintain the official OctoPi image.

I run OctoPrint on a RockPi, but I also rolled my own embedded Linux distro (PrintNanny OS) to package this setup.

There are a lot of small papercuts, like OctoPrint using `vcgencmd` to measure CPU throttling. `vcgencmd` is part of Raspberry Pi's userland. Not a big deal (aliased to another util). I've also added WebRTC-based streaming to my build.

The recommended way to use OctoPrint is the OctoPi image, which is based on Raspbian / Raspberry Pi OS. The OctoPi image includes extras like haproxy and mjpg streamer for HTTP-based JPEG frame stream. If you end up baking a RockPi image, here's the OctoPi root file system for reference: https://github.com/guysoft/OctoPi/tree/devel/src/modules/oct...

OctoPi only goes up to version 0.18.0, so maybe you meant OctoPrint 1.7.2?

Might be related to this issue?