# build/rewrite screen
`Windows` `macOS` `Linux` `RasPi`
### During Build
This is the screen during the build process. The contents of the build commands are output to the console screen. ..." in the screen shows the number of files being built. is the number of files being built, and the darker color at the bottom is the name of the file being built.
### Build error
If the build fails, the screen will look like the above. You can execute a rebuild or view the error log. It will also return to the straight line menu as time expires after a certain period of time.
Only typical error messages are displayed on the screen. When a build fails, error messages may not be displayed.
| Operation | Desc. |
| ------------------ | --------------------------------------------------------------------------------------------------------- |
| `[ A ]` long press | Exit this screen and return to the previous menu. |
| `[ B ]` | Rebuild on error |
| `[ C ]` | Show error log (Windows/Mac)
The error log is {project folder}/build/builderr.log.
|
| `[ C ]` long press | Open a folder (project, related folders). You can set it to open in VS Code in the settings menu. |
| ESC | Exit this screen and return to the rewriting menu. |
### Programming (Writing firmware)
If the build is successful, the screen for writing firmware is displayed.
After v1.0.2 or later, after the firmware is rewritten, a verification process is performed to read and check the rewritten contents.
### Failure while programming
If the programming is in error, the screen will look like the above
| Operation | Desc. |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `[ A ]` long press | Exit this screen and return to the previous menu. |
| `[ B ]` | Perform programming again (returns to the previous programming menu. Since the menu item for programming is still selected, press `[ B ]` again to perform the programming again). |
| ESC | Exit this screen and return to the programming menu. |
### Completion of programming
If the programming is successfully completed, the above message is displayed.
From v1.0.2 onward, after the firmware is rewritten, a verification process is performed to read and check the rewritten contents.
| Operation | Desc. |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| `[ A ]` long press | Exit this screen and return to the previous menu. |
| `[ B ]` | Reset the TWELITE radio module and go to the Interactive settings mode screen (or terminal, depending on your settings) screen. |
| ESC | Exit this screen and return to the programming menu. |
| 操作 | |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| `[ A ]` long press | Exit this screen and return to the previous menu. |
| `[ B ]` | Reset the TWELITE wireless module and go to the Interactive settings mode screen (or terminal, depending on your settings) screen. |
| ESC | Exit this screen and return to the programming menu. |
---
# Agent Instructions: 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:
```
GET https://stage.twelite.info/eng/usage/screens/main_menu/firm_prog/build_screen.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.