-
-
Notifications
You must be signed in to change notification settings - Fork 263
Dev Mode and Debug Mode
hawkeyexp edited this page Jun 25, 2019
·
8 revisions
The dev mode gives you access to all parts of the system.
- Filesystem is mounted in read write mode
- Network is enabled, allowing SSH access
- System boots to shell (terminal)
There are three methods available for enabling Dev Mode:
- Via
/boot/crankshaft/crankshaft_env.sh
->DEV_MODE=1
- By creating a file named
ENABLE_DEVMODE
on a USB stick, inserting the USB stick and rebooting - Within the Crankshaft settings app,
CS Env
tab,Enable GPIO
,Dev Mode
select GPIO which must be set to low to trigger Dev Mode.
Note: You can optionally set DEV_MODE_APP=1
if you want OpenAuto to start, instead of the dev mode default of booting to shell (terminal). /boot/crankshaft/crankshaft_env.sh
will be checked for DEV_MODE_APP=1
, to determine whether to start OpenAuto, regardless of which method used to enable Dev Mode.
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