These fixes are common for older versions. If you don't run into issues with the sections stated below, you shouldn't need to use these fixes.
Currently the image does not include connman due to a bug in the build system. Also, for connman to work, it requires a package called dhcpc5. To install connman and dhcpc5, connect your NavQ to the internet using ethernet, and run the following:
Use the quick start guide to connect to WiFi once you're finished installing those packages.
There is an issue with resolv.conf that prevents you from connecting to the internet on WiFi due to an incorrect DNS setup. To fix this, edit /etc/resolv.conf by removing the current nameserver IP and replacing it with 8.8.8.8.
By default, the navq user on the HoverGames-Demo image is not in the dialout and video groups. If your user is not in those groups, you will not have control of the camera nor the UART port for communication to the FMUK66. To fix this, run the following commands:
It is necessary to log out to ensure that the Linux kernel knows that your user is part of those user groups.
In the current build, there is an issue with ldconfig which causes the v4l2src driver to not be found. To fix this, run the following commands:
Currently the patches for the linux device tree in our build system are not working. To fix hardware issues like the camera, HDMI, and WiFi, you'll need to replace the *.dtb file on the boot partition of your SD card. You'll need the following file to follow the steps below:
Insert your SD card into your computer
Open the boot partition that is mounted by default.
Drag and drop the imx8mm-cube.dtb file into the boot partition.
Boot your NavQ. Quickly connect to it using a serial monitor such as PuTTY.
Press Enter repeatedly after it boots to bring up the u-boot=> prompt.
In the u-boot=> prompt, run the following commands:
Once you have completed these steps, you should be good to go until you reflash your SD card with a new image.