Recently, Raspberry Pi and its peripherals come to be broken.

-Messages are not output from the GPS module,

-I knew how to break the OS kernel 100% on reboot,

-I also encountered a case where the Raspberry Pi was “completely silent”

-----

"Once Raspberry Pi has been constructed and started up stably, it is rarely broken."

In fact, our home security server, Raspberry Pi, has been running for more than five years.

However, over the past six months, I continued to refurbish more than a dozen Rasppies in order to bring out their capabilities, I would encounter various failures.

I guess this is just a parameter issue. If the number is large, the rate of encountering failures naturally increases.

-----

Nevertheless, Raspberry Pi is very useful during the research phase.

After all, it is not certified as a PC, so it is easy to purchase even in the company.

If I make a new function and it fails, and if I have the backup in the SD card, I can easily return to the point before the failure (The time of writing for 32 GB SD card is less than 30 minutes).

And if you only have a copy of that SD card, Raspberry Pi with the same configuration will work reliably.

In particular, when transferring technology, it is very felpful for me to just pass on an SD card instead of creating specifications and setting manuals

(There are Vmware and Docker with the same concept, but I have never been able to run those virtual environments in one shot)

-----

"No specifications or instruction manual"

"I'll give you this SD card, so please read and understand the code directly."

"Any modifications in the SD card is allowed"

"The condition is "Never ask me anything""

Raspberry Pi, which enables such a technology transfer, is quite nice. Even if they often break down.