> For the complete documentation index, see [llms.txt](https://rgbkb.gitbook.io/rgbkb-build-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rgbkb.gitbook.io/rgbkb-build-guides/pan/flashing.md).
# Flashing
{% hint style="info" %}
Your ATmega 32A will come pre-flashed with a bootloader and default hex file. You can use [**QMK toolbox**](https://github.com/qmk/qmk_toolbox/releases) to flash a new layout.
{% endhint %}
Pan uses QMK firmware. [Documentation on installation, keymaps and compiling can be found here.](https://docs.qmk.fm/)
If QMK Toolbox doesn't work, try [these steps](https://www.reddit.com/r/olkb/comments/7jo1ob/qmk_flashing_kbd75_no_device_present/dr9jvj6)
### [Pre-compiled firmware files can be found here](https://github.com/RGBKB/Keyboard-files/tree/master/Pan/Flashing%20Files)
1. Choose ATmega32A in QMK Toolbox.
2. Choose the hex file to flash.
1. Choose a hex file based on your encoder and LED bypass configuration.
3. Hold the BOOT button, tap RESET, and release the BOOT button.
1. A device named "USBASP..." should show up.
4. Flash the board.
5. Done!
If your ATmega32A doesn't have a bootloader, you'll need to flash one using AVRdudess and an arduino
* [Set up your arduino as an ISP flasher](https://www.arduino.cc/en/tutorial/arduinoISP)
* Make sure to download the bootloader hex [here](https://github.com/RGBKB/Keyboard-files/tree/master/Pan/Flashing%20Files)
* Set MCU and fuses as indicated below
* Wire up your arduino to the ISP pins located to the right of the MCU
* Plug in your arduino to the PC and select the port
* Program the ATmega32A
---
# 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://rgbkb.gitbook.io/rgbkb-build-guides/pan/flashing.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.