> 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/mun/flashing.md).

# Flashing

{% hint style="info" %}
Mün currently uses a fork [here](https://github.com/RGBKB/qmk_firmware/tree/development/keyboards/rgbkb/mun), specifically the /development branch. When split RGB & encoders has fully been implemented into QMK, the fork will be pulled into the master branch.
{% endhint %}

{% hint style="info" %}
Touch buttons are currently disabled. Add keycodes to line 86 and 87 of keymap.c to enable.
{% endhint %}

{% file src="/files/3iYvdQSauCOH9izIX8De" %}
Mün Left 9/13/2022
{% endfile %}

{% file src="/files/l5r7V16XUNUPahbMcpsl" %}
Mün Right 9/13/2022
{% endfile %}

Mun uses QMK firmware. [Documentation on installation, keymaps and compiling can be found here.](https://docs.qmk.fm/)​

**To install the default keymap: (LED PCBs do not need to be installed)**

1. Install [QMK Toolbox](https://github.com/qmk/qmk_toolbox/releases)​
2. Flash the left half
   1. Push the slide switches into place, away from the port you want to connect to the PC. An indicator for the standard setup is on the bottom of the LED PCB.
   2. QMK Toolbox: Choose the **left** firmware .bin with **`Open`**.
   3. Plug in the leftmost port to the PC.
   4. Reset the board by pressing the reset switch on the PCB.
   5. Flash: Press the flash button in QMK Toolbox.
3. Flash the right half
   1. Repeat the above with the **right** .bin file, using the rightmost port to the PC.
4. Plug the leftmost port into your PC, and the two middle ports into each other.
5. After the initial setup, you can update your keymap using [QMK Toolbox](https://github.com/qmk/qmk_toolbox), and you only need to flash the primary half.

​For custom keymaps, do the following (To be changed when Mün enters QMK master)

1. Install [QMK MSYS](https://msys.qmk.fm/) and open, run the following:
2. `git clone -b development https://github.com/rgbkb/qmk_firmware`
3. `qmk setup` - press Y when asked to install submodules
4. `qmk doctor`
5.  `qmk flash -kb rgbkb/mun -km default -bl dfu-util-split-left`
   1. Reset the board, it will flash automatically
   2. Flash the right half with  `qmk flash -kb rgbkb/mun -km default -bl dfu-util-split-right`

If QMK Toolbox doesn't work, try [these steps](https://www.reddit.com/r/olkb/comments/7jo1ob/qmk_flashing_kbd75_no_device_present/dr9jvj6)

To update your repo, run the following

1. `cd qmk_firmware`
2. `git remote add upstream -t development https://github.com/rgbkb/qmk_firmware`
3. `git pull upstream development`
4. `cd ..`
5. If dependencies have changed, you may need to re-run `qmk doctor` or run `python3 -m pip install -U qmk`


---

# 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/mun/flashing.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.