Crankshaft dev mode

Development mode

This page is being written. There will be more interesting features regarding the dev mode, check back this page later for more tips and tricks.

As Crankshaft is designed as a "plug-n-play" solution, it mostly doesn't need to be configured. But if you want to save the settings or change the system, you could do so by starting it in dev mode. This feature is offered on image 2018-03-05 or later.

To enable dev mode, put a jumper on GPIO4/Ground (Pin 07-09). Then start the system, then wait for it to restart. Voila! You're in dev mode. You can now plug a keyboard or SSH into the system.

To quit dev mode, remove the jumper, then issue sudo reboot. It will reboot twice, and you'll be out of dev mode.

• It will enable network services that are normally not enabled.
• It will mount the system in the read-write mode so your changes are saved.
• It will not start the head unit app automatically until you ask it to (issue sudo systemctl start autoapp).
• It will enable the OpenSSH daemon. Plug a wired connection in, and you can SSH into the system (on Mac & Linux, ssh pi@crankshaft, on Windows, use PuTTY). Use default username pi and password raspberry. Note: Every time you enable dev mode, it will generate a new key. Your computer might warn you about changed host signatures - that's OK. Just remove the old sigs so it doesn't complain anymore.

Test app under X11 (compatibility mode)

Enable dev mode. Issue:

sudo apt -y install xserver-xorg xterm xinit

# if you're on SSH, you need to do this command next, otherwise skip
# choose "Anybody"
sudo dpkg-reconfigure xserver-xorg-legacy

echo "exec autoapp --platform xcb" > ~/.xinitrc

xinit

See if that works better for you. If it does, then edit the file /etc/systemd/system/autoapp.service. Find the line where it says: ExecStart=/usr/local/bin/autoapp and replace it with just /usr/bin/xinit. This might be automated in the future.