> For the complete documentation index, see [llms.txt](https://nxp.gitbook.io/8mmnavq/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nxp.gitbook.io/8mmnavq/untitled.md).

# NavQ and HoverGames

<div align="center"><img src="/files/-M5ShVnvV7pW0j8H7mI4" alt="NXP HoverGames Drone Software Competition"></div>

While the 8MMNavQ is a standalone computer, it has been designed with NXP HoverGames coding competition in mind. And specifically the NXP[ KIT-HGDRONEK66](https://www.nxp.com/applications/solutions/industrial/aerospace-and-mobile-robotics/uavs-drones-and-rovers/nxp-hovergames-drone-kit-including-rddrone-fmuk66-and-peripherals:KIT-HGDRONEK66) using the [RDDRONE-FMUK66](https://www.nxp.com/design/designs/px4-robotic-drone-fmu-rddrone-fmuk66:RDDRONE-FMUK66?\&tid=vanRDDRONE-FMUK66) flight controller. &#x20;

* [www.HoverGames.com](https://nxp.gitbook.io/8mmnavq/www.HoverGames.com)
* <https://nxp.gitbook.io/HoverGames>

{% hint style="info" %}
As a result of HoverGames planning, the NavQ also makes a great companion computer for many other PX4 or Ardupilot flight controllers &#x20;
{% endhint %}

[HoverGames](https://www.hovergames.com) specific features include

* NavQ can connect to HoverGames (RDDDRONE-FMUK66)
  * via serial
  * via Ethernet (using 100BaseT1 2 wire ethernet adapter)
  * via USB (requires specific configuration)
* RGB LED onboard for status reporting
* USB-C console for debugging
* Power input via USB-C or JST-GH power header
* MicroUSB port for peripherals (hub, usb cameras, sensors)
* IX industrial Ethernet jack
* Serial ports using JST-GH connectors
* I2C/SPI port using JST-GH connectors
* 3 wire LED strip connector with power supply
* Wifi and Bluetooth
* MIPI Camera intereface (Google Coral Camera default)
* eMMC and removable SDCard memories
* MIPI DSI for display (particularly for Rover applications)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nxp.gitbook.io/8mmnavq/untitled.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.