Driver Station
The driver station has a handful of failure modes and things that can break it. Here's some common failure modes and issues.
Getting Logs
The Driver's Station prints out logs to its HDMI port. You can connect this to a monitor and the logs will be displayed. The content of these logs requires pretty deep knowledge to understand, but you may be asked to provide a picture of the Gizmo logs during debugging.
The system processor provides an event stream over its USB port when accessed as a serial port. The Gizmo will stream data at 9600,8,n,1
that will tell you what event its currently processing. This information can be useful in forming a bug report to tell what the Gizmo is trying to do at the time of encountering a bug.
Imaging Issues
During imaging you may encounter issues where Balena Etcher does not write the full image. This can usually be resolved by restarting the imaging process, disconnecting and reconnecting the micro SD card from the reader, or using a downloaded copy of the .img
file rather than the URL.
Boot Issues
If you encounter issues with booting the Gizmo DS make sure that you have supplied a gsscfg.json
file as described in the setup guide.
Under rare circumstances the micro SD card can become corrupted. If this occurs you must re-image the micro SD card.
Binding Issues
The binding process relies on passing information back and forth between the Gizmo and the driver station. After pressing the system processor BOOTSEL
button it may take up to 1 minute to complete binding. If the Gizmo has not bound within this interval, reboot both the driver's station and the Gizmo to try again.