serial pi error

StereoPi hardware discussion
Post Reply
henrique_mg
Posts: 25
Joined: Sat Jul 13, 2019 5:10 pm

serial pi error

Post by henrique_mg »

when boots the serial error message PI

User avatar
Realizator
Site Admin
Posts: 900
Joined: Tue Apr 16, 2019 9:23 am
Contact:

Re: serial pi error

Post by Realizator »

Could you please give me more details on this message? Like message text or a screenshot.
Actually we use serial port communications only in a special projects (like FPV system for the drones), but neither S.L.P., nor OpenCV image contain any code related to serial communications.
You may face such a messages if you use some very special images from us (like for ChiefPilot FPV solution, or for Cosmostreamer project for DJI-related drones and cameras), but, as I said, these images are absolutely differ from SLP and OpenCV images.
Eugene a.k.a. Realizator

henrique_mg
Posts: 25
Joined: Sat Jul 13, 2019 5:10 pm

Re: serial pi error

Post by henrique_mg »

Raspberry PI serial number
Attachments
IMG_20191010_135305280.jpg
IMG_20191010_135305280.jpg (50.29 KiB) Viewed 3982 times

User avatar
Realizator
Site Admin
Posts: 900
Joined: Tue Apr 16, 2019 9:23 am
Contact:

Re: serial pi error

Post by Realizator »

Showing a serial number is just a part of a boot process.

Your StereoPi can not boot. As I have no more details from you, I can share my suggestions:

1. Data on your micro SD is corrupted (boot partition).
This may be caused by occasional poweroff or ejecting micro SD card while boot process. If you have another Linux computer (or another Raspberry Pi), you can insert this card via cardreader and access your ext4 partition to save your data and code from this micro SD card. As S.L.P. Linux partition is read-only, your data is safe with 99.9% possibility (if micro SD is not damaged).

2. Your micro SD card is damaged
Sometimes micro SD card dies. It might be detected and recognized by the computer, but not all data can be written or read. Try to use another micro SD card.

3. You've changed something in settings, or installed some new stuff
As I have no details, it's just a suggestion. Kernel update, installing new drivers, changes in configuration files at /BOOT partition etc.
In this case I prefer to use fresh-written stock image and add new staff step-by-step. This way you can localize the step, leading to the problem.
Eugene a.k.a. Realizator

Post Reply