diff --git a/Raspbery-Pi-Setup.md b/Raspbery-Pi-Setup.md index 2f6e416..17a6c17 100644 --- a/Raspbery-Pi-Setup.md +++ b/Raspbery-Pi-Setup.md @@ -38,8 +38,11 @@ This guide is build on following hardware: # 0 Story The idea of this project came when I was looking in a way to get apple car play for my old car. I have a special video input that allows to connect external media with RCA, but generally this can be used on any car that have some source of RCA input. In most cases reverse camera are connected as same RCA video input. So with a little bit of creativity this can be implemented on wide area of cases. + I wanted to have something minimalistic and fast, that I can seamlessly integrate as a ready made module. My research bring me to the Autobox dongle that promised to get Carplay for any Android device. At that point of time I had Orange PI at hand that can run Android OS, so my plans were just to plug and play. But things doesn't went quite smooth and I found a problems with connection RCA to Orange PI as well as I didn't want to have the whole Android system to boot for only one application. + From there I started to investigate other options to use the dongle with Linux and found [electric-monk's pycarplay](https://github.com/electric-monk/pycarplay) implementation. Also i decided to get really minimalistic and try to run everything on Raspberry Pi Zero 2W that I have already successfully connected to my car with RCA. But the problem came that all of the implementations were not using hardware decoding or required other frameworks that was not possible to run on 512 MB or RPI Zero 2W. So after several failed attempts to get smooth Carplay on RPI and digging into sources I decided to write own piece of software with something compilable to binary that will be CPU and Memory efficient and use HW decoding. + After some coding, protocol digging and learning new thing I have ended up with this project. Also I decided to document all the steps that will allow you to get from 0 to full kiosk mode Carplay solution, cause in attempts to build a solid minimalistic system that I want, I figure out that there are no good guidance on setting up a lot of things that for me looks essential. Or if the steps are described a lot of "details" what settings are doing and why they needed are missing. So I hope that this guide will help not only people who are building FastCarPlay but it will also allow others to learn how to set up simple and effective kiosk single app solutions with RPI with minimal CPU/Memory usage. # 1 Flashing @@ -90,6 +93,7 @@ Plug your SD card in, or attach it to the virtual machine. Open **gparted** and First, increase the size of **rootfs**. Open *Partition* → *Resize/Move* and set the new partition size. About 8 GB is sufficient for a minimal setup. ![Partitioning 2](pictures/rpi-partition2.png) + Next, create a partition for **/home**. Choose *Partition* → *New* and set *Free space following* for swap (at least 512 MB on an RPI Zero 2W). Set the filesystem to **ext4**, enter a label such as **home**. ![Partitioning 3](pictures/rpi-partition3.png) diff --git a/pictures/rpi-flash1.png b/pictures/rpi-flash1.png index 49c9bbb..affd1a0 100644 Binary files a/pictures/rpi-flash1.png and b/pictures/rpi-flash1.png differ diff --git a/pictures/rpi-flash2.png b/pictures/rpi-flash2.png index 3de79c6..6084faf 100644 Binary files a/pictures/rpi-flash2.png and b/pictures/rpi-flash2.png differ diff --git a/pictures/rpi-flash3.png b/pictures/rpi-flash3.png index ea34d4a..89b2e44 100644 Binary files a/pictures/rpi-flash3.png and b/pictures/rpi-flash3.png differ diff --git a/pictures/rpi-flash4.png b/pictures/rpi-flash4.png index 3c4908f..ffff981 100644 Binary files a/pictures/rpi-flash4.png and b/pictures/rpi-flash4.png differ diff --git a/pictures/rpi-flash5.png b/pictures/rpi-flash5.png index 605acc6..daa87b4 100644 Binary files a/pictures/rpi-flash5.png and b/pictures/rpi-flash5.png differ