-
-
Notifications
You must be signed in to change notification settings - Fork 264
Installing and Updating
inspector71 edited this page Sep 21, 2018
·
21 revisions
- Download the zip of the latest version available at the top of the Releases section, under the Code tab
- Unpack the zip to a temporary location
- Write the
.img
file to your SD card, for example with Win32DiskImager (on Windows) - Insert the SC card into your Pi
Thats it.
Note: Don't remove the USB stick during the whole flash process until system is up in normal mode again!
Two methods are available:
- Manually flash the full image, erasing your existing configuration. Not the best solution ...
- Upgrade via USB stick, the recommended way to preserve your general system setup
- Place the downloaded zip on a USB stick (must be
fat32
,ext3
, orext4
formatted and min 2GB) As alternate you can place the unpacked.img
and the.md5
file on the stick to save time for unpacking on the stick) - Power off your system
- Plug in your stick
- Power on
- During startup the USB stick which is containing your zip (or
.img
and the.md5
) will be detected - If flash file is a zip it will be unpacked to the USB stick
- Now the system is preparing the flash mode and backing up default config files After finish it will reboot into flash mode
- The system starts now to flash the sd card
- After successfull flash the
config.txt
andcrankshaft_env.sh
will be restored to preserve display is working again if custom settings are needed for your display - System is rebooting again in normal mode
- During first boot some intial setups are done including resizing your sdcard
- After initial setup your backup is restored from USB stick
- Now all is done and your system will boot normal with the new software version
- The USB stick is not longer needed and can be removed
Some notes:
The system will flash every version different from current installed - there is no lock for up and downgrading. But if you switch back to older versions there is no guarantee that all will work fine.
Special info (what will be backed up during flash):
- /boot/config.txt
- /boot/crankshaft/crankshaft_env.sh
- /boot/crankshaft/gpio2kbd.cfg
- /boot/crankshaft/startup.py
- /boot/crankshaft/startup.sh
- /boot/crankshaft/triggerhappy.conf
- /boot/crankshaft/brightness
- /boot/crankshaft/brightness-night
- /boot/crankshaft/volume
- /boot/crankshaft/capvolume
- /boot/crankshaft/openauto.ini
- /boot/crankshaft/wallpaper.png
- /boot/crankshaft/wallpaper-night.png
- /boot/crankshaft/wallpaper-devmode.png
- /boot/crankshaft/wallpaper-devmode-night.png
- /etc/timezone
- /etc/X11/xorg.conf.d/99-calibration.conf
- /etc/pulse/client.conf
If you have any reason to flash again same version (possible caused by demaged system) you can place a file
called FORCE_FLASH
on same stick like the zip (or .img
and the .md5
).
The flash mode will now ignore the version check and flash it.
- Home
- Roadmap
- General Changes / Changelog
- Installing / Updating
- When Issue occur
- Hardware
- Configuration
- Features
- Home
- Get started
- Hardware
- Software and Settings
- For Advanced Users
- Et Cetera