-
-
Notifications
You must be signed in to change notification settings - Fork 264
Dev Mode and Debug Mode
The dev mode gives you access to all parts of the system. The filesystem is mounted in read write mode and network is enabled to allow ssh access to your system.
How to enable?
-
You can enable the dev mode in
/boot/cankshaft/crankshaft_env.sh
->DEV_MODE=1
By default system boots to shell. You can optionally setDEV_MODE_APP=1
to trigger start of openauto in dev mode. -
You can place a file called
ENABLE_DEVMODE
on a usb stick an connect it to the system. During boot the file will be detected and the system will boot into dev mode. Note:/boot/crankshaft/crankshaft_env.sh
will be checked forDEV_MODE_APP=1
to decide to start openauto or not. -
You can enable dev mode by setting
DEV_PIN
GPIO to low ifENABLE_GPIO
is set to 1. By defaultDEV_PIN=4
andENABLE_GPIO=1
.
The debug mode is created to allow a normal system start including network like in dev mode and enabling some logging.
- You can enable the debug mode in
/boot/crankshaft/crankshaft_env.sh
->DEBUG_MODE=1
- You can place a file called
ENABLE_DEBUG
on a usb stick an connect it to the system During boot the file will be detected and the system will boot into debug mode - You can enable the debug mode inside settings of openauto starting with pre4
Note: If both modes are enabled debug mode is dominant.
- Start in debug mode
- Reproduce the problem - for example open settings - change value and save
- Push the gray button on bottom of main screen. You will get a text note and the button is invisible
- After creation the logs are zipped and placed on
/boot/debug.zip
- 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