> For the complete documentation index, see [llms.txt](https://docs.cubepilot.org/user-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubepilot.org/user-guides/service-bulletins-and-critical-notices/safety-service-bulletins/sb_0000005-i2c-storm-can-cause-inflight-reboots-chibios-only-not-nuttx-all-cube-and-pixhawk-hardw.md).

# SB\_0000005 I2C Storm can cause Inflight Reboots, Chibios ONLY, not Nuttx (all The Cube hardware)

**For the latest updates, refer to the following link:**\
[SB\_0000005 I2C Storm can cause inflight reboots, Chibios ONLY, not Nuttx (all The Cube hardware)](https://discuss.cubepilot.org/t/sb-0000005-i2c-storm-can-cause-inflight-reboots-chibios-only-not-nuttx-all-cube-and-pixhawk-hardware-including-clones-and-derivatives/2419)

**CRITICAL**

**Update ALL CHIBIOS Copter USERS MUST USE 3.6.12 or cease flight**.

Critical Safety Update is in Copter 3.6.12\
Update Friday, 13th December. This is a Chibios only issue. Old hardware running old custom or stock Nuttx firmware is not affected by this SB.

Due to an issue with a bug in the I2C system for ArduCopter for 3.6.10 version and earlier and Arduplane before 4.0.

Ground any vehicles that have not BEEN updated to Arduplane 4.0 or 3.6.11 for Arducopter or later.

This issue has lead to aircraft failing mid flight, and the details can be found in the Ardupilot release notes for 3.6.11.

A rare case can still occur in 3.6.11, 3.6.12 will be released shortly, and as soon as it is, this notice will be updated.


---

# 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://docs.cubepilot.org/user-guides/service-bulletins-and-critical-notices/safety-service-bulletins/sb_0000005-i2c-storm-can-cause-inflight-reboots-chibios-only-not-nuttx-all-cube-and-pixhawk-hardw.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.