> For the complete documentation index, see [llms.txt](https://irseeker.buildingblockrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://irseeker.buildingblockrobotics.com/board-update.md).

# Board Update

Your IRSeeker has version 2 installed. This version will work with SPIKE Legacy. If you would like to use the new SPIKE Version 3, you will need to follow the process to update your board.

**Step 1:** Download the [version 2.1 firmware](https://s3.amazonaws.com/www.buildingblockrobotics.com/firmware/firmware2-1b.uf2) for SPIKE Version 3.

**Step 2**: Plug the board into your computer with a USB cable.

**Step 3**: Quickly Double tap the reset button on the board. When done correctly, a new USB device will appear.

**Step 4**. Copy the downloaded file from Step 1 onto the board.

This [firmware page](/updates/firmware.md) has more details on how to update the firmware version of your board.


---

# 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://irseeker.buildingblockrobotics.com/board-update.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.