> For the complete documentation index, see [llms.txt](https://nxp.gitbook.io/hovergames/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/hovergames/developerguide/zephyr-on-fmuk66.md).

# Zephyr on FMUK66

FMUK66 is supported in Main branch for Zephyr. 

{% embed url="<https://github.com/zephyrproject-rtos/zephyr>" %}

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/boards/arm/rddrone_fmuk66>" %}

[
](<https://github.com/zephyrproject-rtos/zephyr&#xD;&#xA;https://github.com/zephyrproject-rtos/zephyr/tree/main/boards/arm/rddrone_fmuk66&#xD;&#xA;>)We will work to add examples of how to use it here in the near future.\
Meanwhile there are examples os using PWM and other interfaces which can be found in the&#x20;

### Zephyr Documentation

Zephyr documentation here:

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples>" %}

### Sample Zephyr applications:

An example of using the Servo Motor:

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/basic/servo_motor>" %}

An example of running the RGB LED test controlled by PWM&#x20;

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/basic/rgb_led>" %}

An example of using pressure sensor bme280/bmp280 over internal I2C bus

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/sensor/bme280>" %}

An example of using magnetometer sensor bmm150 over internal I2C bus

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/sensor/magn_polling>" %}

An example of using 3 axis accelerometer and 3 axis magnetometer fxos8700 over internal SPI bus

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/sensor/fxos8700>" %}

An example of running angular rate gyroscope fxas21002 over internal SPI bus

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/sensor/fxas21002>" %}

An example to communicate over socketcan

{% embed url="<https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/net/sockets/can>" %}

### Local Zephyr Repo

It is possible in the future that some development has taken place that is not yet pushed to Zephyr/ Main. Below is our local working repo where we may be working on updates.<br>

{% hint style="info" %}
Note there are many branches in this local repo.&#x20;

You can use pr-multi-socketcan for using multiple socketcan interfaces in parallel.

For any other development checkout pr-fmuk66-board<br>
{% endhint %}

{% embed url="<https://github.com/NXPHoverGames/zephyr>" %}
NXP Local repofor working with Zephyr<br>
{% endembed %}

### &#x20;AIM India Program

Aim India may also use MR-Buggy3 and similar code. A link is provided here for reference only.

{% embed url="<https://nxpaimindia.com/https://github.com/NXPHoverGames/GitBook-AIM>" %}

{% embed url="<https://nxpaimindia.com/>" %}
NXP AIM program India
{% endembed %}

<br>


---

# 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/hovergames/developerguide/zephyr-on-fmuk66.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.