I’ve recently come across a GoPiGo2 kit. After assembling the car and attempting to connect it to my network, I ran into a few weird situations, including the inability to connect via ethernet cable.
To try to remedy that, I reflashed the SD card with the raspbian for robots (it was a 2015 version anyways, so I thought it’d be a good idea - I followed the instructions from here). After doing that, I can’t seem to boot the raspberry pi.
Plugging in a monitor via HDMI shows the normal boot sequence (with the services starting up), but then they suddenly begin stopping every service and the last line I am able to read is something to the effect of “Starting shut-down…” before the video output is stopped and the activity light on the pi ceases completely. The power light remains on, but the board is off and I can’t seem to pull up the command line or do any of the steps mentioned in the connecting tutorial.
I have tried multiple SD cards and double checked the md5 hashes of the downloaded OSs. Trying to boot up the official raspbian OS (not from dexter industries) works fine.
This is partially incorrect. With the 2015 version I got from the kit, the kit booted up, but I was having trouble setting up the networking. As such, I’ve flashed the July 2017 version and only then the shutdown command started triggering when I attempted to boot…
That is correct. Disconnected from the GoPiGo2 board as well.
As for the suggestions:
The OS is already updated from the July 2017 version.
The black foam was removed during the assembly of the car and is not present on the boot.
Here is an album with the setup and the boot screens. I have also tried booting it while connected via ethernet, with little difference. http://imgur.com/a/Xpsmk
My mistake. It was indeed the June version. Just in case, I tried it again downloading (and double checked the MD5 hash after extracting - it wasn’t corrupted). I flashed my SD card using etcher yet again and… the problem persists.
I disconnected it from the GoPiGo2 board and the issue didn’t change.
I did notice a particular line during the boot, though, maybe it is of some use for this troubleshooting?