> 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/~/changes/mvMsnRI8xnoKpbe3XhLK/autopilot/the-cube-series-firmware-and-connection-troubleshooting.md). # The Cube - Firmware Installation & Connection Troubleshooting ## The Cube Autopilot All Models Out The Box All Cube Autopilot models now come with no autopilot software installed from the factory and as such you will need to install your chosen firmware such as Ardupilor or PX4 before you can use it. ### Supported Ardupilot Versions The Cube Black, Purple and Blue models are compatible with older versions of Ardupilot and PX4 software however the Cube Orange and Cube Yellow modes are using the STM32F7 and the STM32H7 microcontrollers that require you are using the latest drivers and software to use these models. **Note** It is strongly advised to use the latest stable release of Ardupilot at all times to ensure you are uptosdate with any bug and feature updates. ### Cube Black, Blue and Purple These Cube models are supported in older versions of Ardupilot however its strogly advised to use Arducopter 3.6.12 or Arduplane 3.9.11 or later due to a critical I2C Storm bug fixes. More Information on this specific issue can be found in the Cubepilot bulitins or Ardupilot forum. Cubepilot Bulletin's Ardupilot forums ### The Cube Orange and Cube Yellow These models are supported in Arducopter, Rover and Plane version 4.0 and later only. **Note** Its strongly advised to be using ChibiOS versions of Ardupilot with all Cube models unless you have a specific reasons otherwise. ## --- # 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/~/changes/mvMsnRI8xnoKpbe3XhLK/autopilot/the-cube-series-firmware-and-connection-troubleshooting.md?ask=&goal= ``` `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.