WHY2025 wiki - User contributions [en]

Badge Issues

2025-08-16T14:17:20Z

Frederik:

== Please edit this page ==

'''Please edit this page to add your issue or increase the interest counter
'''

The ''[number]'' in front of each question is the interest counter. Increase it by one if you have the same question.

== Badge Hardware Questions/Issues ==
=== Answered ===
==== [1] After reflash and exiting the intial sponsors screen, the screen stays blue ====
* => Reflash the badge using the web flasher. (https://why-prog.heplaphon.com/). Use the USB socket on the left side for flashing. After the update unplug/replug the USB. Make sure to use a good cable as the badge is power hungry.
==== [2] How do I reset the badge on battery? ====
* => Applying usb power will reset the badge
==== [4] Batteries ar being held firmly (maybe a bit too firmly) in place in the battery holder. How can I safely remove the batteries? What tool to use for this without damaging the batteries or the PCB? ====
* => Try gripping it with rubber gloves on.
* => For future handling, add strong tape around it, so that you'll have a lid to pull on for extra support

==== [3] The badge suddenly stopped working. Serial shows boot-loop with message <pre>Cannot connect to target. Error: TIMEOUT </pre> ====
* => Reseating the ESP daughterboard (fitted with a screw) helped here.
* => M.2 socket of ESP daughterboard can break off without being immediately visible. This also leads to this error. [https://chaos.social/@xro/115011118785473303 Re-soldering fixed it.]
Trace of boot-loop:
<pre>
./idf.py monitor
W (1098) fatfs-sd: SD card not mounted
E (1108) device: The device does not exist SD0
Cannot connect to target. Error: TIMEOUT
Check if the host and the target are properly connected.
E (4828) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (4828) sdio_wrapper: sdmmc_card_init failed
E (4828) H_SDIO_DRV: sdio card init failed
Crashing in ESP-IDF task
Guru Meditation Error: Core 1 panic'ed (Instruction access fault). Exception was unhandled.

--- Stack dump detected
Core 1 register dump:
MEPC : 0x00000000 RA : 0x00000000 SP : 0x4ff278c0 GP : 0x4ff18580
TP : 0x4ff278e0 T0 : 0x4ff0f4a6 T1 : 0x4ff120a8 T2 : 0xffffffff
--- 0x4ff0f4a6: spinlock_release at /home/bernhard/source/why2025-badge-firmware/components/esp_hw_support/include/spinlock.h:181
</pre>
==== [5] Some keys (the `w` key in my case) don't register. I've tried with the nametag app and with the new System Settings app, and it didn't work on either. ====
[[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 01:24, 14 August 2025 (CEST)
* => Check for [https://chaos.social/@edronik/115027350958230845 crusty stuff under the metal membrane]
==== [8] The antenna isn't connected yet. Can I use the device without damaging anything? ====
* The antenna is used by the LoRa radio. At the moment of writing there is no badge firmware available that uses the LoRa radio. This means that for now the device can safely be used without the antenna (socket) attached.
* As soon as you do start using the LoRa radio, there is a potential for damage when the badge is used without the antenna. Attaching the antenna requires some extra precautions. See the instructions on attaching the socket further down on this wiki page for tips and tricks.
** (Can not include link as the HTTP anchor contains square brackets)
==== [2] How to solder the antenna-connector? The center pin can't be reached. Do we disassemble the screen to solder from the other side? Any modifications needed, so the screen spacer still fits? ====

[[User:RobotJoosen|robotjoosen]] 22:11, 14 August 2025 (GMT)

* => You have to take the badge apart by unscrewing all four screws. Then you are able to solder on the antenna. The socket should be on the other side of the screen side, otherwise you can't put the spacer and frontplant back on.
* => The two pins closest to the screen are very close to the screen, when soldering them the screen can get damaged. When you are not confident in your solder skills you can leave them unsoldered but this does affect the rigidity of the antenna. When soldering you can use some heat resistant tape like kapton, this does not fully protect the screen but can help.
* => Ideally you take the screen of which can be done with some dental floss, although this could damage the screen.
* => The spacer won't fit with, a quick fix would be to widen the holes with you soldering iron, or use a drill to increase the size.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [3] Screen flickers sometimes. Is this a defect? I tried looking at the screen ribbon cable, it seems OK. ====
* => (bend the board -> more flicker?)
* => I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)
==== [4] screen is not turning on at all. ====
* => I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)
* => extreme case: (https://chaos.social/@xro/115011118785473303)
==== [7] Can not turn off badge while charging. ====
Yet to be answered.
==== [9] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it? ====
Yet to be answered.
==== [10] Badge updates apps after starting an app that isn't the updater ====
Yet to be answered.
==== [11] Sponsor screen replays (unskippable) after every flash ====

[[User:RobotJoosen|robotjoosen]] 22:11, 14 August 2025 (GMT)

<s>=> Press `fn + x` to skip sponsor screen</s>

[[User:Tielemans.jorim|Tielemans.jorim]] 14:13, 16 August 2025 (CEST)

`fn + x` should not be used as this force closes the sponsors app. You need to wait for it to at least play once and use the `esc` key once shown on screen.<br>Terminating the sponsors app early might result in not being able to open other apps.

==== [12] Double-tapping the power button doesn't shut down the badge ====
Yet to be answered.
==== [13] Where do we get the badge now that the event is over? The lines were huge or the stand was closed. Can we pay for shipping to get them later? ====
Yet to be answered.
==== [14] Is it possible to insert an SD card without removing the daughter board (with cells installed)? ====

[[User:RobotJoosen|robotjoosen]] 22:13, 14 August 2025 (GMT)

=> No, there is not physical space to insert a SD card without bending/breaking it. It is also not possible without the cells.

==== [1] Flashing to `BadgeVMS post_event` might work fine, until a reboot. This appears to happen only on devices with an SD-card installed, it will result in the error `Could not open APPS:[badgevms_launcher]badgevms_launcher.elf` [https://pastebin.com/zMr45zHT pastebin] ====
Yet to be answered.

* Addendum, See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [2] Damaged wrapping of an 18650 battery, is this an issue? ====
* Is this an issue? (see picture) [[File:Badge 18650 with a small mark.jpg|thumb]]

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
Yet to be answered.
==== [1] Screen wobbles horizontal (X-Axis) with random amount. (Allready flashed newest firmware (Badge VMS post_event) without any changes). Wobble gets worse the longer the device is on. Starts after about 3 Minutes. Slight wobble can be triggert by pressing a button keyboard ====
Yet to be answered.

==== [1] Screen has yellowish pixel failures [[File:PXL 20250815 195829061.jpg|thumb]] Screen also wobbles horizontal after few minutes (see topic above) ====
Yet to be answered.

==== [1] I'd like to remove the 18650 cell holders but the epoxy is holding them in a bit too well. Has anyone managed to find a non-destructive way to do this? ====
Yet to be answered.

==== [1] I'd like to power the badge using a conventional LiPo pouch, but I don't see a header anywhere that I could solder a JST connector to. Has anyone else achieved this? ====
Yet to be answered.

==== [1] There's a header (LS1) between the M.2 board and one of the cell holders which seems (from the schematics) to be for a speaker. Has anyone got this working? What parts did you use? ====
Yet to be answered.

==== [1] Badge shows yellow screen randomly (seems related to daughter M.2 board) ====

Randomly the badge display turns yellow.

What I tried:
* Swapped the daughter M.2 ESP board with another badge → the yellow screen issue followed the daughterboard, not the main board.
* Serial log shows no errors at the moment the display turns yellow.
* Tried many different firmwares, currently running the post event firmware.

This suggests the issue is related to the M.2 daughterboard, likely power instability under load.

Yet to be answered.

== Badge User Questions/Issues ==
=== Answered ===
==== [1] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3. ====
* Thank you for reporting this, I've fixed this and released a new version with improved keyboard handling (v2.0.1). --[[User:Wallaby|Wallaby]] ([[User talk:Wallaby|talk]]) 14:37, 11 August 2025 (CEST)
==== [5] WHY2025 OTA updater is not reacting. ====
* => We are working on this. For now, don't touch it and instead just wait at least 30 seconds.
** => This didn't work for me; I had to re-flash the firmware. [[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 08:53, 13 August 2025 (CEST)
** => Any update on this? "OTA" and "Hello" app don't do anything. Not even an error message. Is there a hidden Wifi settings menu or something for the "over the air" part? Maybe a USB-C to Ethernet dongle?
==== [3] There is a stripe and/or "HD3" stamp on my screen ====
* Test if you see these when the badge is off.
* There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. There's a tab to peel in the lower right corner. This tab may be under the front cover or the spacer.
* I saw at least one device where the sticky tape area was '''under''' the front cover. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** Assemblers of the spacer/keyboard/front cover were at some point instructed to keep the tab to peel of the protective layer under the spacer. Reason for this: unknown. Perhaps to reduce the change of them coming off while the badges were still being assembled. --[[User:44x|44x]] 23:33, 14 August 2025 (CEST)
==== [2] Could do one update, then three updates and then BadgeVMS Firmware Version 4. Now I a offered this update on every boot and can do nothing else, even though I have installed it already ====
* reboot fixes this.
==== [3] My Badge is showing a yellow screen. Its starting with a blue screen and shows the Menu for a few seconds an then turns yellow. What does this indicate? ====
* The v5 firmware had this bug. Reflash with a newer to fix.
==== [11] I’m finally home! How do I connect the badge to my local Wi-Fi? ====
* Lazy, hacky method: Create an open Wi-Fi network with the SSID "WHY2025-open" (the O not as a capital letter) and run the OTA update app.
* Easy method: Use the [https://why-prog.heplaphon.com/ WHY badge flasher] to install the "BadgeVMS post_event" firmware which includes an app called System Settings which allows you to connect to your home Wi-Fi network.
** This requires a desktop Google Chrome or Microsoft Edge. Firefox is not supported.
** The USB cable must be in the socket on the side. Not the bottom.
** The correct COM port is named "USB Serial". Not "USB Jtag/Serial" or "CDC"
?? What if "USB Serial is not showing up ??
* Developer method:
** Clone the badge firmware repository.
** Edit `wifi_config` in `badgevms/drivers/wifi.c`.
** Change `.ssid` to your network name.
** Directly below `.ssid` add a line with `.password = "your network password",`.
** Then build/flash the firmware: `idf.py build flash`.
* Dev-in-a-hurry:
** Collect the latest firmware here: https://gitlab.com/why2025/team-badge/firmware/-/releases
** use esptool.py -p /dev/cu.wch* write_flash 0 firmware_81d7cdf7.bin
** use the System Settings which allows you to connect to your home Wi-Fi network.

==== There's sticky transparent stuff on my badge, what should I do? ====
* The sticky stuff is UV epoxy that is not fully cured.
* It is very much recommended to fully cure the epoxy first.
** If you have touched the sticky epoxy, wash your hands.
** ⚠️ Note that according to the interwebz some people can be allergic to uncured epoxy. It is not ruled out you may see an allergic reaction. Always contact a medical professional if you see effects and have questions.
* Where can I expect epoxy on my badge?
** Epoxy should have been applied to the ends of the battery holders, where the holders are soldered onto the PCB. There are 4 spots in total. In some cases epoxy may not cover the area that needs protecting.
** You may however also observe epoxy in other spots, such as:
*** The back side near the bottom USB-C port and the screw holes, preventing screws from going through.
*** The front side of the badge near the keyboard, which may prevent the keyboard from fully functioning. This includes the area under the white membrane layer. [https://chaos.social/@edronik/115027350958230845 More information from someone who has experienced this].
*** Basically any place liquid could have flowed to from the location the epoxy was applied since the epoxy was runny when it was applied.
* How to cure the epoxy?
** The epoxy is cured by exposing it to UV light. A popular source of UV light is the sun. Even if it is cloudy or somewhat later in the afternoon, UV light is still present so you don't need to put the badge in the scorching sun to cure the epoxy.
** 1. Shut down badge, remove batteries or any other power source. Do not expose those to the hot sun.
** 2. Place your badge outside in daylight. Make sure all spots that have UV resin on them are exposed. In direct sunlight it is recommended to cover other components.
** 3. Leave for 30 to 60 minutes.
** 4. Regularly check and leave exposed to daylight until all blobs of epoxy have fully cured and are no longer sticky at all. Wash hands after every check.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [4] OTA update screen appears on first boot, after pressing space bar, blue screen with nothing happening for over an hour. ====
* Have the same problem after first OTA update. Update started but the device stuck on bluescreen for an hour or so before I removed power. After flashing a new firmware using the [https://why-prog.heplaphon.com web updater] it works again (use the USB slot on the side, otherwise you get an error message "Your ESP C6 chip is unsupported"). [https://pastebin.com/VjMA5ZZA Logfiles] --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** No, it doesn't. It displayed the sponsors page once but returned to the bluescreen afterwards. [https://pastebin.com/cCKejKCk Logs from the side USB port]. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:18, 11 August 2025 (CEST)
** Uploaded another log containing the complete first boot after flashing the new firmware: https://pastebin.com/3NiSRncL (edit: see below). Note the exception at the end: "Task 4 caused an unhandled exception, Cerberos will deal with it". After that, no new entries appear and the display stays blue. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:25, 11 August 2025 (CEST)
** Was wrong about that again. There were more log entries while I wrote the previous comments. Here is the complete log: https://pastebin.com/KMQwhBPv --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:34, 11 August 2025 (CEST)
* Anyone managed to fix that errpr and getting the Bagde running again? --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 13:16, 13 August 2025 (CEST)
==== [7] Blue screen. Nothing happening. ====
* => Not official answer: What helped for me was reflashing the badge via the flash station at the badge tent.
* Might be missing symbols, ota might work. Flash, don't reboot yet and ota first.
* Might be because of a known issue regarding the sd card, if you have this issue with an sd card inserted, try again when removing it. See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [1] Cannot build the firmware from https://gitlab.com/why2025/team-badge/firmware/. Tried to build main and flashed_at_first_handout - both fail because of the following error: https://pastebin.com/H4xwPLhC ====
* Do you have the latest ESP-IDF installed? (Version 5.5)
==== [1] stuck at do_http(https://badge.why2025.org/api/v3/projects/why2025_firmware_ota_c6/rev4/files/version.txt) error: server response: '{"reason":"No app with slug 'why2025_firmware_ota_c6' and revision '4' found"}' ====

==== [5] The badge is not detect on my mac when I connect it by side port: ====
* '''Don't''' use brew, it has been reported not to work.
* Follow these instructions: [[Badge/MacOS_Drivers]]
==== [1] I can't flash the badge - it says the board is incompatible ====
* => Use the USB-C port on the side of the board, not the one on the bottom
==== [1] The letter "a' is represented by a horizontal dash in the nametag app ====
Yet to be answered.
==== [1] The launcher says that "Enter" will launch an app while it really launches when pressing "Space". ====
Yet to be answered.
==== [1] The settings app does react veeeee*ry slowly, sometimes I have to press Enter multiple times to get to the list of WiFi networks (and sometimes, one of those keypresses instantly selects a network) ====
Yet to be answered.

== Badge Firmware Development related Questions/Issues ==
==== [2] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up? ====
Yet to be answered.
==== [1] Following the gdb debugging instructions doesn't work. ====
===== What I tried =====

I followed https://docs.espressif.com/projects/esp-idf/en/v5.5/esp32p4/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-command-line on the [https://gitlab.com/why2025/team-badge/firmware/-/tree/644f502e72259228efa9b2423a91fbc4aed5f3d4/ firmware repository with commit 644f502e72259228efa9b2423a91fbc4aed5f3d4 (tag: v6)].

I am always using the side port on the badge, and I have confirmed that flashing normally works OK. I can also monitor serial and do basic printf debugging in C.

It seems the <code>.gdbinit</code> files are generated OK (step 3).

I edited the third line in file <code>build/gdbinit/connect</code>, from <code>target remote :3333</code> to <code>target remote /dev/ttyUSB0</code> (I determined that this was the correct serial port by seeing the difference in <code>ll /dev</code> output before and after plugging in my badge).

Then I ran the command in step 4 with the correct elf file, like <code>riscv32-esp-elf-gdb -q -x build/gdbinit/symbols -x build/gdbinit/prefix_map -x build/gdbinit/connect build/badgevms.elf</code>, but it hangs. After doing ^C I can get back to a (gdb) prompt, and when I explicitly do <code>target remote /dev/ttyUSB0</code>, it still hangs.

Error log (I do ^C twice, and then ^D to quit the gdb prompt):
<pre>
$ riscv32-esp-elf-gdb -q -x build/gdbinit/symbols -x build/gdbinit/prefix_map -x build/gdbinit/connect build/badgevms.elf
Reading symbols from build/badgevms.elf...
add symbol table from file "/home/moomin/Desktop/badge/firmware/build/bootloader/bootloader.elf"
^CQuit
(gdb) target remote /dev/ttyUSB0
Remote debugging using /dev/ttyUSB0
^CQuit
(gdb) quit
</pre>

===== Resolution =====
Yet to be answered.
==== [1] After installing OTA update, application updates AND System Update "BadgeVMS Firmware, Version 4, Main Badge Firmware" the system restarts showing System Updates => "Updates available 1" => "BadgeVMS Firmware, Version 4, Main Badge Firmware". Selecting it, installing it and autorstarting leads back to this same screen. I seem to be stuck in a loop of the update process. ====
* => Shut down your badge by double tapping the power button. Restart. You should now see the application WHY Application Launcher.
** => But double-tapping the power button doesn't shut down the badge...
*** hold ot down for 13+ seconds for a hard reboot.

== BadgeHub related Questions/Issues ==
==== [2] How do I get apps from the BadgeHub onto the Badge? Is it possible without an SD card (I don't have one). I can build apps and flash the firmware, but I have no idea how to get pre-compiled ELFs on there. ====
* => If you have a SD card (if not, the mysteryhack village has a vending machine): Create the folder stucture ./BADGEVMS/APPS on there. In there, create a folder named like the badge hub project name. Download and put the .elf in there. Create a json file with the project name next to the folder and put the key/values for name, unique_identifier, version and binary_path in there. binary_path is just the full name of the .elf file.
** => the mysteryhack village vending machine has been out of SD cards since day 0 or 1

Badge Issues

2025-08-16T14:12:47Z

Frederik:

== Please edit this page ==

'''Please edit this page to add your issue or increase the interest counter
'''

The ''[number]'' in front of each question is the interest counter. Increase it by one if you have the same question.

== Badge Hardware Questions/Issues ==
=== Answered ===
==== [1] After reflash and exiting the intial sponsors screen, the screen stays blue ====
* => Reflash the badge using the web flasher. (https://why-prog.heplaphon.com/). Use the USB socket on the left side for flashing. After the update unplug/replug the USB. Make sure to use a good cable as the badge is power hungry.
==== [2] How do I reset the badge on battery? ====
* => Applying usb power will reset the badge
==== [4] Batteries ar being held firmly (maybe a bit too firmly) in place in the battery holder. How can I safely remove the batteries? What tool to use for this without damaging the batteries or the PCB? ====
* => Try gripping it with rubber gloves on.
* => For future handling, add strong tape around it, so that you'll have a lid to pull on for extra support

==== [3] The badge suddenly stopped working. Serial shows boot-loop with message <pre>Cannot connect to target. Error: TIMEOUT </pre> ====
* => Reseating the ESP daughterboard (fitted with a screw) helped here.
* => M.2 socket of ESP daughterboard can break off without being immediately visible. This also leads to this error. [https://chaos.social/@xro/115011118785473303 Re-soldering fixed it.]
Trace of boot-loop:
<pre>
./idf.py monitor
W (1098) fatfs-sd: SD card not mounted
E (1108) device: The device does not exist SD0
Cannot connect to target. Error: TIMEOUT
Check if the host and the target are properly connected.
E (4828) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (4828) sdio_wrapper: sdmmc_card_init failed
E (4828) H_SDIO_DRV: sdio card init failed
Crashing in ESP-IDF task
Guru Meditation Error: Core 1 panic'ed (Instruction access fault). Exception was unhandled.

--- Stack dump detected
Core 1 register dump:
MEPC : 0x00000000 RA : 0x00000000 SP : 0x4ff278c0 GP : 0x4ff18580
TP : 0x4ff278e0 T0 : 0x4ff0f4a6 T1 : 0x4ff120a8 T2 : 0xffffffff
--- 0x4ff0f4a6: spinlock_release at /home/bernhard/source/why2025-badge-firmware/components/esp_hw_support/include/spinlock.h:181
</pre>
==== [5] Some keys (the `w` key in my case) don't register. I've tried with the nametag app and with the new System Settings app, and it didn't work on either. ====
[[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 01:24, 14 August 2025 (CEST)
* => Check for [https://chaos.social/@edronik/115027350958230845 crusty stuff under the metal membrane]
==== [8] The antenna isn't connected yet. Can I use the device without damaging anything? ====
* The antenna is used by the LoRa radio. At the moment of writing there is no badge firmware available that uses the LoRa radio. This means that for now the device can safely be used without the antenna (socket) attached.
* As soon as you do start using the LoRa radio, there is a potential for damage when the badge is used without the antenna. Attaching the antenna requires some extra precautions. See the instructions on attaching the socket further down on this wiki page for tips and tricks.
** (Can not include link as the HTTP anchor contains square brackets)
==== [2] How to solder the antenna-connector? The center pin can't be reached. Do we disassemble the screen to solder from the other side? Any modifications needed, so the screen spacer still fits? ====

[[User:RobotJoosen|robotjoosen]] 22:11, 14 August 2025 (GMT)

* => You have to take the badge apart by unscrewing all four screws. Then you are able to solder on the antenna. The socket should be on the other side of the screen side, otherwise you can't put the spacer and frontplant back on.
* => The two pins closest to the screen are very close to the screen, when soldering them the screen can get damaged. When you are not confident in your solder skills you can leave them unsoldered but this does affect the rigidity of the antenna. When soldering you can use some heat resistant tape like kapton, this does not fully protect the screen but can help.
* => Ideally you take the screen of which can be done with some dental floss, although this could damage the screen.
* => The spacer won't fit with, a quick fix would be to widen the holes with you soldering iron, or use a drill to increase the size.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [3] Screen flickers sometimes. Is this a defect? I tried looking at the screen ribbon cable, it seems OK. ====
(bend the board -> more flicker)
I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)
==== [4] screen is not turning on at all. ====
I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)
extreme case: (https://chaos.social/@xro/115011118785473303)
==== [7] Can not turn off badge while charging. ====
Yet to be answered.
==== [9] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it? ====
Yet to be answered.
==== [10] Badge updates apps after starting an app that isn't the updater ====
Yet to be answered.
==== [11] Sponsor screen replays (unskippable) after every flash ====

[[User:RobotJoosen|robotjoosen]] 22:11, 14 August 2025 (GMT)

<s>=> Press `fn + x` to skip sponsor screen</s>

[[User:Tielemans.jorim|Tielemans.jorim]] 14:13, 16 August 2025 (CEST)

`fn + x` should not be used as this force closes the sponsors app. You need to wait for it to at least play once and use the `esc` key once shown on screen.<br>Terminating the sponsors app early might result in not being able to open other apps.

==== [12] Double-tapping the power button doesn't shut down the badge ====
Yet to be answered.
==== [13] Where do we get the badge now that the event is over? The lines were huge or the stand was closed. Can we pay for shipping to get them later? ====
Yet to be answered.
==== [14] Is it possible to insert an SD card without removing the daughter board (with cells installed)? ====

[[User:RobotJoosen|robotjoosen]] 22:13, 14 August 2025 (GMT)

=> No, there is not physical space to insert a SD card without bending/breaking it. It is also not possible without the cells.

==== [1] Flashing to `BadgeVMS post_event` might work fine, until a reboot. This appears to happen only on devices with an SD-card installed, it will result in the error `Could not open APPS:[badgevms_launcher]badgevms_launcher.elf` [https://pastebin.com/zMr45zHT pastebin] ====
Yet to be answered.

* Addendum, See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [2] Damaged wrapping of an 18650 battery, is this an issue? ====
* Is this an issue? (see picture) [[File:Badge 18650 with a small mark.jpg|thumb]]

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
Yet to be answered.
==== [1] Screen wobbles horizontal (X-Axis) with random amount. (Allready flashed newest firmware (Badge VMS post_event) without any changes). Wobble gets worse the longer the device is on. Starts after about 3 Minutes. Slight wobble can be triggert by pressing a button keyboard ====
Yet to be answered.

==== [1] Screen has yellowish pixel failures [[File:PXL 20250815 195829061.jpg|thumb]] Screen also wobbles horizontal after few minutes (see topic above) ====
Yet to be answered.

==== [1] I'd like to remove the 18650 cell holders but the epoxy is holding them in a bit too well. Has anyone managed to find a non-destructive way to do this? ====
Yet to be answered.

==== [1] I'd like to power the badge using a conventional LiPo pouch, but I don't see a header anywhere that I could solder a JST connector to. Has anyone else achieved this? ====
Yet to be answered.

==== [1] There's a header (LS1) between the M.2 board and one of the cell holders which seems (from the schematics) to be for a speaker. Has anyone got this working? What parts did you use? ====
Yet to be answered.

==== [1] Badge shows yellow screen randomly (seems related to daughter M.2 board) ====

Randomly the badge display turns yellow.

What I tried:
* Swapped the daughter M.2 ESP board with another badge → the yellow screen issue followed the daughterboard, not the main board.
* Serial log shows no errors at the moment the display turns yellow.
* Tried many different firmwares, currently running the post event firmware.

This suggests the issue is related to the M.2 daughterboard, likely power instability under load.

Yet to be answered.

== Badge User Questions/Issues ==
=== Answered ===
==== [1] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3. ====
* Thank you for reporting this, I've fixed this and released a new version with improved keyboard handling (v2.0.1). --[[User:Wallaby|Wallaby]] ([[User talk:Wallaby|talk]]) 14:37, 11 August 2025 (CEST)
==== [5] WHY2025 OTA updater is not reacting. ====
* => We are working on this. For now, don't touch it and instead just wait at least 30 seconds.
** => This didn't work for me; I had to re-flash the firmware. [[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 08:53, 13 August 2025 (CEST)
** => Any update on this? "OTA" and "Hello" app don't do anything. Not even an error message. Is there a hidden Wifi settings menu or something for the "over the air" part? Maybe a USB-C to Ethernet dongle?
==== [3] There is a stripe and/or "HD3" stamp on my screen ====
* Test if you see these when the badge is off.
* There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. There's a tab to peel in the lower right corner. This tab may be under the front cover or the spacer.
* I saw at least one device where the sticky tape area was '''under''' the front cover. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** Assemblers of the spacer/keyboard/front cover were at some point instructed to keep the tab to peel of the protective layer under the spacer. Reason for this: unknown. Perhaps to reduce the change of them coming off while the badges were still being assembled. --[[User:44x|44x]] 23:33, 14 August 2025 (CEST)
==== [2] Could do one update, then three updates and then BadgeVMS Firmware Version 4. Now I a offered this update on every boot and can do nothing else, even though I have installed it already ====
* reboot fixes this.
==== [3] My Badge is showing a yellow screen. Its starting with a blue screen and shows the Menu for a few seconds an then turns yellow. What does this indicate? ====
* The v5 firmware had this bug. Reflash with a newer to fix.
==== [11] I’m finally home! How do I connect the badge to my local Wi-Fi? ====
* Lazy, hacky method: Create an open Wi-Fi network with the SSID "WHY2025-open" (the O not as a capital letter) and run the OTA update app.
* Easy method: Use the [https://why-prog.heplaphon.com/ WHY badge flasher] to install the "BadgeVMS post_event" firmware which includes an app called System Settings which allows you to connect to your home Wi-Fi network.
** This requires a desktop Google Chrome or Microsoft Edge. Firefox is not supported.
** The USB cable must be in the socket on the side. Not the bottom.
** The correct COM port is named "USB Serial". Not "USB Jtag/Serial" or "CDC"
?? What if "USB Serial is not showing up ??
* Developer method:
** Clone the badge firmware repository.
** Edit `wifi_config` in `badgevms/drivers/wifi.c`.
** Change `.ssid` to your network name.
** Directly below `.ssid` add a line with `.password = "your network password",`.
** Then build/flash the firmware: `idf.py build flash`.
* Dev-in-a-hurry:
** Collect the latest firmware here: https://gitlab.com/why2025/team-badge/firmware/-/releases
** use esptool.py -p /dev/cu.wch* write_flash 0 firmware_81d7cdf7.bin
** use the System Settings which allows you to connect to your home Wi-Fi network.

==== There's sticky transparent stuff on my badge, what should I do? ====
* The sticky stuff is UV epoxy that is not fully cured.
* It is very much recommended to fully cure the epoxy first.
** If you have touched the sticky epoxy, wash your hands.
** ⚠️ Note that according to the interwebz some people can be allergic to uncured epoxy. It is not ruled out you may see an allergic reaction. Always contact a medical professional if you see effects and have questions.
* Where can I expect epoxy on my badge?
** Epoxy should have been applied to the ends of the battery holders, where the holders are soldered onto the PCB. There are 4 spots in total. In some cases epoxy may not cover the area that needs protecting.
** You may however also observe epoxy in other spots, such as:
*** The back side near the bottom USB-C port and the screw holes, preventing screws from going through.
*** The front side of the badge near the keyboard, which may prevent the keyboard from fully functioning. This includes the area under the white membrane layer. [https://chaos.social/@edronik/115027350958230845 More information from someone who has experienced this].
*** Basically any place liquid could have flowed to from the location the epoxy was applied since the epoxy was runny when it was applied.
* How to cure the epoxy?
** The epoxy is cured by exposing it to UV light. A popular source of UV light is the sun. Even if it is cloudy or somewhat later in the afternoon, UV light is still present so you don't need to put the badge in the scorching sun to cure the epoxy.
** 1. Shut down badge, remove batteries or any other power source. Do not expose those to the hot sun.
** 2. Place your badge outside in daylight. Make sure all spots that have UV resin on them are exposed. In direct sunlight it is recommended to cover other components.
** 3. Leave for 30 to 60 minutes.
** 4. Regularly check and leave exposed to daylight until all blobs of epoxy have fully cured and are no longer sticky at all. Wash hands after every check.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [4] OTA update screen appears on first boot, after pressing space bar, blue screen with nothing happening for over an hour. ====
* Have the same problem after first OTA update. Update started but the device stuck on bluescreen for an hour or so before I removed power. After flashing a new firmware using the [https://why-prog.heplaphon.com web updater] it works again (use the USB slot on the side, otherwise you get an error message "Your ESP C6 chip is unsupported"). [https://pastebin.com/VjMA5ZZA Logfiles] --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** No, it doesn't. It displayed the sponsors page once but returned to the bluescreen afterwards. [https://pastebin.com/cCKejKCk Logs from the side USB port]. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:18, 11 August 2025 (CEST)
** Uploaded another log containing the complete first boot after flashing the new firmware: https://pastebin.com/3NiSRncL (edit: see below). Note the exception at the end: "Task 4 caused an unhandled exception, Cerberos will deal with it". After that, no new entries appear and the display stays blue. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:25, 11 August 2025 (CEST)
** Was wrong about that again. There were more log entries while I wrote the previous comments. Here is the complete log: https://pastebin.com/KMQwhBPv --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:34, 11 August 2025 (CEST)
* Anyone managed to fix that errpr and getting the Bagde running again? --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 13:16, 13 August 2025 (CEST)
==== [7] Blue screen. Nothing happening. ====
* => Not official answer: What helped for me was reflashing the badge via the flash station at the badge tent.
* Might be missing symbols, ota might work. Flash, don't reboot yet and ota first.
* Might be because of a known issue regarding the sd card, if you have this issue with an sd card inserted, try again when removing it. See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [1] Cannot build the firmware from https://gitlab.com/why2025/team-badge/firmware/. Tried to build main and flashed_at_first_handout - both fail because of the following error: https://pastebin.com/H4xwPLhC ====
* Do you have the latest ESP-IDF installed? (Version 5.5)
==== [1] stuck at do_http(https://badge.why2025.org/api/v3/projects/why2025_firmware_ota_c6/rev4/files/version.txt) error: server response: '{"reason":"No app with slug 'why2025_firmware_ota_c6' and revision '4' found"}' ====

==== [5] The badge is not detect on my mac when I connect it by side port: ====
* '''Don't''' use brew, it has been reported not to work.
* Follow these instructions: [[Badge/MacOS_Drivers]]
==== [1] I can't flash the badge - it says the board is incompatible ====
* => Use the USB-C port on the side of the board, not the one on the bottom
==== [1] The letter "a' is represented by a horizontal dash in the nametag app ====
Yet to be answered.
==== [1] The launcher says that "Enter" will launch an app while it really launches when pressing "Space". ====
Yet to be answered.
==== [1] The settings app does react veeeee*ry slowly, sometimes I have to press Enter multiple times to get to the list of WiFi networks (and sometimes, one of those keypresses instantly selects a network) ====
Yet to be answered.

== Badge Firmware Development related Questions/Issues ==
==== [2] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up? ====
Yet to be answered.
==== [1] Following the gdb debugging instructions doesn't work. ====
===== What I tried =====

I followed https://docs.espressif.com/projects/esp-idf/en/v5.5/esp32p4/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-command-line on the [https://gitlab.com/why2025/team-badge/firmware/-/tree/644f502e72259228efa9b2423a91fbc4aed5f3d4/ firmware repository with commit 644f502e72259228efa9b2423a91fbc4aed5f3d4 (tag: v6)].

I am always using the side port on the badge, and I have confirmed that flashing normally works OK. I can also monitor serial and do basic printf debugging in C.

It seems the <code>.gdbinit</code> files are generated OK (step 3).

I edited the third line in file <code>build/gdbinit/connect</code>, from <code>target remote :3333</code> to <code>target remote /dev/ttyUSB0</code> (I determined that this was the correct serial port by seeing the difference in <code>ll /dev</code> output before and after plugging in my badge).

Then I ran the command in step 4 with the correct elf file, like <code>riscv32-esp-elf-gdb -q -x build/gdbinit/symbols -x build/gdbinit/prefix_map -x build/gdbinit/connect build/badgevms.elf</code>, but it hangs. After doing ^C I can get back to a (gdb) prompt, and when I explicitly do <code>target remote /dev/ttyUSB0</code>, it still hangs.

Error log (I do ^C twice, and then ^D to quit the gdb prompt):
<pre>
$ riscv32-esp-elf-gdb -q -x build/gdbinit/symbols -x build/gdbinit/prefix_map -x build/gdbinit/connect build/badgevms.elf
Reading symbols from build/badgevms.elf...
add symbol table from file "/home/moomin/Desktop/badge/firmware/build/bootloader/bootloader.elf"
^CQuit
(gdb) target remote /dev/ttyUSB0
Remote debugging using /dev/ttyUSB0
^CQuit
(gdb) quit
</pre>

===== Resolution =====
Yet to be answered.
==== [1] After installing OTA update, application updates AND System Update "BadgeVMS Firmware, Version 4, Main Badge Firmware" the system restarts showing System Updates => "Updates available 1" => "BadgeVMS Firmware, Version 4, Main Badge Firmware". Selecting it, installing it and autorstarting leads back to this same screen. I seem to be stuck in a loop of the update process. ====
* => Shut down your badge by double tapping the power button. Restart. You should now see the application WHY Application Launcher.
** => But double-tapping the power button doesn't shut down the badge...
*** hold ot down for 13+ seconds for a hard reboot.

== BadgeHub related Questions/Issues ==
==== [2] How do I get apps from the BadgeHub onto the Badge? Is it possible without an SD card (I don't have one). I can build apps and flash the firmware, but I have no idea how to get pre-compiled ELFs on there. ====
* => If you have a SD card (if not, the mysteryhack village has a vending machine): Create the folder stucture ./BADGEVMS/APPS on there. In there, create a folder named like the badge hub project name. Download and put the .elf in there. Create a json file with the project name next to the folder and put the key/values for name, unique_identifier, version and binary_path in there. binary_path is just the full name of the .elf file.
** => the mysteryhack village vending machine has been out of SD cards since day 0 or 1

Badge Issues

2025-08-16T14:12:01Z

Frederik:

== Please edit this page ==

'''Please edit this page to add your issue or increase the interest counter
'''

The ''[number]'' in front of each question is the interest counter. Increase it by one if you have the same question.

== Badge Hardware Questions/Issues ==
=== Answered ===
==== [1] After reflash and exiting the intial sponsors screen, the screen stays blue ====
* => Reflash the badge using the web flasher. (https://why-prog.heplaphon.com/). Use the USB socket on the left side for flashing. After the update unplug/replug the USB. Make sure to use a good cable as the badge is power hungry.
==== [2] How do I reset the badge on battery? ====
* => Applying usb power will reset the badge
==== [4] Batteries ar being held firmly (maybe a bit too firmly) in place in the battery holder. How can I safely remove the batteries? What tool to use for this without damaging the batteries or the PCB? ====
* => Try gripping it with rubber gloves on.
* => For future handling, add strong tape around it, so that you'll have a lid to pull on for extra support

==== [3] The badge suddenly stopped working. Serial shows boot-loop with message <pre>Cannot connect to target. Error: TIMEOUT </pre> ====
* => Reseating the ESP daughterboard (fitted with a screw) helped here.
* => M.2 socket of ESP daughterboard can break off without being immediately visible. This also leads to this error. [https://chaos.social/@xro/115011118785473303 Re-soldering fixed it.]
Trace of boot-loop:
<pre>
./idf.py monitor
W (1098) fatfs-sd: SD card not mounted
E (1108) device: The device does not exist SD0
Cannot connect to target. Error: TIMEOUT
Check if the host and the target are properly connected.
E (4828) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (4828) sdio_wrapper: sdmmc_card_init failed
E (4828) H_SDIO_DRV: sdio card init failed
Crashing in ESP-IDF task
Guru Meditation Error: Core 1 panic'ed (Instruction access fault). Exception was unhandled.

--- Stack dump detected
Core 1 register dump:
MEPC : 0x00000000 RA : 0x00000000 SP : 0x4ff278c0 GP : 0x4ff18580
TP : 0x4ff278e0 T0 : 0x4ff0f4a6 T1 : 0x4ff120a8 T2 : 0xffffffff
--- 0x4ff0f4a6: spinlock_release at /home/bernhard/source/why2025-badge-firmware/components/esp_hw_support/include/spinlock.h:181
</pre>
==== [5] Some keys (the `w` key in my case) don't register. I've tried with the nametag app and with the new System Settings app, and it didn't work on either. ====
[[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 01:24, 14 August 2025 (CEST)
* => Check for [https://chaos.social/@edronik/115027350958230845 crusty stuff under the metal membrane]
==== [8] The antenna isn't connected yet. Can I use the device without damaging anything? ====
* The antenna is used by the LoRa radio. At the moment of writing there is no badge firmware available that uses the LoRa radio. This means that for now the device can safely be used without the antenna (socket) attached.
* As soon as you do start using the LoRa radio, there is a potential for damage when the badge is used without the antenna. Attaching the antenna requires some extra precautions. See the instructions on attaching the socket further down on this wiki page for tips and tricks.
** (Can not include link as the HTTP anchor contains square brackets)
==== [2] How to solder the antenna-connector? The center pin can't be reached. Do we disassemble the screen to solder from the other side? Any modifications needed, so the screen spacer still fits? ====

[[User:RobotJoosen|robotjoosen]] 22:11, 14 August 2025 (GMT)

* => You have to take the badge apart by unscrewing all four screws. Then you are able to solder on the antenna. The socket should be on the other side of the screen side, otherwise you can't put the spacer and frontplant back on.
* => The two pins closest to the screen are very close to the screen, when soldering them the screen can get damaged. When you are not confident in your solder skills you can leave them unsoldered but this does affect the rigidity of the antenna. When soldering you can use some heat resistant tape like kapton, this does not fully protect the screen but can help.
* => Ideally you take the screen of which can be done with some dental floss, although this could damage the screen.
* => The spacer won't fit with, a quick fix would be to widen the holes with you soldering iron, or use a drill to increase the size.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [3] Screen flickers sometimes. Is this a defect? I tried looking at the screen ribbon cable, it seems OK. ====
* => (bend the board -> more flicker)
* => I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)
==== [4] screen is not turning on at all. ====
* => I had to resolder the m.2 connector (use flux and touch every pin with soldering iron)
* => extreme case: (https://chaos.social/@xro/115011118785473303)
==== [7] Can not turn off badge while charging. ====
Yet to be answered.
==== [9] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it? ====
Yet to be answered.
==== [10] Badge updates apps after starting an app that isn't the updater ====
Yet to be answered.
==== [11] Sponsor screen replays (unskippable) after every flash ====

[[User:RobotJoosen|robotjoosen]] 22:11, 14 August 2025 (GMT)

<s>=> Press `fn + x` to skip sponsor screen</s>

[[User:Tielemans.jorim|Tielemans.jorim]] 14:13, 16 August 2025 (CEST)

`fn + x` should not be used as this force closes the sponsors app. You need to wait for it to at least play once and use the `esc` key once shown on screen.<br>Terminating the sponsors app early might result in not being able to open other apps.

==== [12] Double-tapping the power button doesn't shut down the badge ====
Yet to be answered.
==== [13] Where do we get the badge now that the event is over? The lines were huge or the stand was closed. Can we pay for shipping to get them later? ====
Yet to be answered.
==== [14] Is it possible to insert an SD card without removing the daughter board (with cells installed)? ====

[[User:RobotJoosen|robotjoosen]] 22:13, 14 August 2025 (GMT)

=> No, there is not physical space to insert a SD card without bending/breaking it. It is also not possible without the cells.

==== [1] Flashing to `BadgeVMS post_event` might work fine, until a reboot. This appears to happen only on devices with an SD-card installed, it will result in the error `Could not open APPS:[badgevms_launcher]badgevms_launcher.elf` [https://pastebin.com/zMr45zHT pastebin] ====
Yet to be answered.

* Addendum, See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [2] Damaged wrapping of an 18650 battery, is this an issue? ====
* Is this an issue? (see picture) [[File:Badge 18650 with a small mark.jpg|thumb]]

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
Yet to be answered.
==== [1] Screen wobbles horizontal (X-Axis) with random amount. (Allready flashed newest firmware (Badge VMS post_event) without any changes). Wobble gets worse the longer the device is on. Starts after about 3 Minutes. Slight wobble can be triggert by pressing a button keyboard ====
Yet to be answered.

==== [1] Screen has yellowish pixel failures [[File:PXL 20250815 195829061.jpg|thumb]] Screen also wobbles horizontal after few minutes (see topic above) ====
Yet to be answered.

==== [1] I'd like to remove the 18650 cell holders but the epoxy is holding them in a bit too well. Has anyone managed to find a non-destructive way to do this? ====
Yet to be answered.

==== [1] I'd like to power the badge using a conventional LiPo pouch, but I don't see a header anywhere that I could solder a JST connector to. Has anyone else achieved this? ====
Yet to be answered.

==== [1] There's a header (LS1) between the M.2 board and one of the cell holders which seems (from the schematics) to be for a speaker. Has anyone got this working? What parts did you use? ====
Yet to be answered.

==== [1] Badge shows yellow screen randomly (seems related to daughter M.2 board) ====

Randomly the badge display turns yellow.

What I tried:
* Swapped the daughter M.2 ESP board with another badge → the yellow screen issue followed the daughterboard, not the main board.
* Serial log shows no errors at the moment the display turns yellow.
* Tried many different firmwares, currently running the post event firmware.

This suggests the issue is related to the M.2 daughterboard, likely power instability under load.

Yet to be answered.

== Badge User Questions/Issues ==
=== Answered ===
==== [1] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3. ====
* Thank you for reporting this, I've fixed this and released a new version with improved keyboard handling (v2.0.1). --[[User:Wallaby|Wallaby]] ([[User talk:Wallaby|talk]]) 14:37, 11 August 2025 (CEST)
==== [5] WHY2025 OTA updater is not reacting. ====
* => We are working on this. For now, don't touch it and instead just wait at least 30 seconds.
** => This didn't work for me; I had to re-flash the firmware. [[User:Bytefighter|bytefighter]] ([[User_talk:Bytefighter|talk]]) 08:53, 13 August 2025 (CEST)
** => Any update on this? "OTA" and "Hello" app don't do anything. Not even an error message. Is there a hidden Wifi settings menu or something for the "over the air" part? Maybe a USB-C to Ethernet dongle?
==== [3] There is a stripe and/or "HD3" stamp on my screen ====
* Test if you see these when the badge is off.
* There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. There's a tab to peel in the lower right corner. This tab may be under the front cover or the spacer.
* I saw at least one device where the sticky tape area was '''under''' the front cover. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** Assemblers of the spacer/keyboard/front cover were at some point instructed to keep the tab to peel of the protective layer under the spacer. Reason for this: unknown. Perhaps to reduce the change of them coming off while the badges were still being assembled. --[[User:44x|44x]] 23:33, 14 August 2025 (CEST)
==== [2] Could do one update, then three updates and then BadgeVMS Firmware Version 4. Now I a offered this update on every boot and can do nothing else, even though I have installed it already ====
* reboot fixes this.
==== [3] My Badge is showing a yellow screen. Its starting with a blue screen and shows the Menu for a few seconds an then turns yellow. What does this indicate? ====
* The v5 firmware had this bug. Reflash with a newer to fix.
==== [11] I’m finally home! How do I connect the badge to my local Wi-Fi? ====
* Lazy, hacky method: Create an open Wi-Fi network with the SSID "WHY2025-open" (the O not as a capital letter) and run the OTA update app.
* Easy method: Use the [https://why-prog.heplaphon.com/ WHY badge flasher] to install the "BadgeVMS post_event" firmware which includes an app called System Settings which allows you to connect to your home Wi-Fi network.
** This requires a desktop Google Chrome or Microsoft Edge. Firefox is not supported.
** The USB cable must be in the socket on the side. Not the bottom.
** The correct COM port is named "USB Serial". Not "USB Jtag/Serial" or "CDC"
?? What if "USB Serial is not showing up ??
* Developer method:
** Clone the badge firmware repository.
** Edit `wifi_config` in `badgevms/drivers/wifi.c`.
** Change `.ssid` to your network name.
** Directly below `.ssid` add a line with `.password = "your network password",`.
** Then build/flash the firmware: `idf.py build flash`.
* Dev-in-a-hurry:
** Collect the latest firmware here: https://gitlab.com/why2025/team-badge/firmware/-/releases
** use esptool.py -p /dev/cu.wch* write_flash 0 firmware_81d7cdf7.bin
** use the System Settings which allows you to connect to your home Wi-Fi network.

==== There's sticky transparent stuff on my badge, what should I do? ====
* The sticky stuff is UV epoxy that is not fully cured.
* It is very much recommended to fully cure the epoxy first.
** If you have touched the sticky epoxy, wash your hands.
** ⚠️ Note that according to the interwebz some people can be allergic to uncured epoxy. It is not ruled out you may see an allergic reaction. Always contact a medical professional if you see effects and have questions.
* Where can I expect epoxy on my badge?
** Epoxy should have been applied to the ends of the battery holders, where the holders are soldered onto the PCB. There are 4 spots in total. In some cases epoxy may not cover the area that needs protecting.
** You may however also observe epoxy in other spots, such as:
*** The back side near the bottom USB-C port and the screw holes, preventing screws from going through.
*** The front side of the badge near the keyboard, which may prevent the keyboard from fully functioning. This includes the area under the white membrane layer. [https://chaos.social/@edronik/115027350958230845 More information from someone who has experienced this].
*** Basically any place liquid could have flowed to from the location the epoxy was applied since the epoxy was runny when it was applied.
* How to cure the epoxy?
** The epoxy is cured by exposing it to UV light. A popular source of UV light is the sun. Even if it is cloudy or somewhat later in the afternoon, UV light is still present so you don't need to put the badge in the scorching sun to cure the epoxy.
** 1. Shut down badge, remove batteries or any other power source. Do not expose those to the hot sun.
** 2. Place your badge outside in daylight. Make sure all spots that have UV resin on them are exposed. In direct sunlight it is recommended to cover other components.
** 3. Leave for 30 to 60 minutes.
** 4. Regularly check and leave exposed to daylight until all blobs of epoxy have fully cured and are no longer sticky at all. Wash hands after every check.

=== Unanswered ===
* Got a question that is already listed but not answered yet? The ''[number]'' in front of each question is the interest counter. Edit this wiki and increase the counter by one if you have the same question. This allows us to prioritize. Thank you!
* Got an answer? Please edit the wiki, add your answer and move the question to the Answered section. Thank you for your contribution!
==== [4] OTA update screen appears on first boot, after pressing space bar, blue screen with nothing happening for over an hour. ====
* Have the same problem after first OTA update. Update started but the device stuck on bluescreen for an hour or so before I removed power. After flashing a new firmware using the [https://why-prog.heplaphon.com web updater] it works again (use the USB slot on the side, otherwise you get an error message "Your ESP C6 chip is unsupported"). [https://pastebin.com/VjMA5ZZA Logfiles] --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:03, 11 August 2025 (CEST)
** No, it doesn't. It displayed the sponsors page once but returned to the bluescreen afterwards. [https://pastebin.com/cCKejKCk Logs from the side USB port]. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:18, 11 August 2025 (CEST)
** Uploaded another log containing the complete first boot after flashing the new firmware: https://pastebin.com/3NiSRncL (edit: see below). Note the exception at the end: "Task 4 caused an unhandled exception, Cerberos will deal with it". After that, no new entries appear and the display stays blue. --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:25, 11 August 2025 (CEST)
** Was wrong about that again. There were more log entries while I wrote the previous comments. Here is the complete log: https://pastebin.com/KMQwhBPv --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 00:34, 11 August 2025 (CEST)
* Anyone managed to fix that errpr and getting the Bagde running again? --[[User:Cybso|Cybso]] ([[User talk:Cybso|talk]]) 13:16, 13 August 2025 (CEST)
==== [7] Blue screen. Nothing happening. ====
* => Not official answer: What helped for me was reflashing the badge via the flash station at the badge tent.
* Might be missing symbols, ota might work. Flash, don't reboot yet and ota first.
* Might be because of a known issue regarding the sd card, if you have this issue with an sd card inserted, try again when removing it. See also: [https://gitlab.com/why2025/team-badge/firmware/-/issues?show=eyJpaWQiOiI5IiwiZnVsbF9wYXRoIjoid2h5MjAyNS90ZWFtLWJhZGdlL2Zpcm13YXJlIiwiaWQiOjE3MTg4NzgyNX0%3D Boot is stuck, when fitted with an SD card]

==== [1] Cannot build the firmware from https://gitlab.com/why2025/team-badge/firmware/. Tried to build main and flashed_at_first_handout - both fail because of the following error: https://pastebin.com/H4xwPLhC ====
* Do you have the latest ESP-IDF installed? (Version 5.5)
==== [1] stuck at do_http(https://badge.why2025.org/api/v3/projects/why2025_firmware_ota_c6/rev4/files/version.txt) error: server response: '{"reason":"No app with slug 'why2025_firmware_ota_c6' and revision '4' found"}' ====

==== [5] The badge is not detect on my mac when I connect it by side port: ====
* '''Don't''' use brew, it has been reported not to work.
* Follow these instructions: [[Badge/MacOS_Drivers]]
==== [1] I can't flash the badge - it says the board is incompatible ====
* => Use the USB-C port on the side of the board, not the one on the bottom
==== [1] The letter "a' is represented by a horizontal dash in the nametag app ====
Yet to be answered.
==== [1] The launcher says that "Enter" will launch an app while it really launches when pressing "Space". ====
Yet to be answered.
==== [1] The settings app does react veeeee*ry slowly, sometimes I have to press Enter multiple times to get to the list of WiFi networks (and sometimes, one of those keypresses instantly selects a network) ====
Yet to be answered.

== Badge Firmware Development related Questions/Issues ==
==== [2] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up? ====
Yet to be answered.
==== [1] Following the gdb debugging instructions doesn't work. ====
===== What I tried =====

I followed https://docs.espressif.com/projects/esp-idf/en/v5.5/esp32p4/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-command-line on the [https://gitlab.com/why2025/team-badge/firmware/-/tree/644f502e72259228efa9b2423a91fbc4aed5f3d4/ firmware repository with commit 644f502e72259228efa9b2423a91fbc4aed5f3d4 (tag: v6)].

I am always using the side port on the badge, and I have confirmed that flashing normally works OK. I can also monitor serial and do basic printf debugging in C.

It seems the <code>.gdbinit</code> files are generated OK (step 3).

I edited the third line in file <code>build/gdbinit/connect</code>, from <code>target remote :3333</code> to <code>target remote /dev/ttyUSB0</code> (I determined that this was the correct serial port by seeing the difference in <code>ll /dev</code> output before and after plugging in my badge).

Then I ran the command in step 4 with the correct elf file, like <code>riscv32-esp-elf-gdb -q -x build/gdbinit/symbols -x build/gdbinit/prefix_map -x build/gdbinit/connect build/badgevms.elf</code>, but it hangs. After doing ^C I can get back to a (gdb) prompt, and when I explicitly do <code>target remote /dev/ttyUSB0</code>, it still hangs.

Error log (I do ^C twice, and then ^D to quit the gdb prompt):
<pre>
$ riscv32-esp-elf-gdb -q -x build/gdbinit/symbols -x build/gdbinit/prefix_map -x build/gdbinit/connect build/badgevms.elf
Reading symbols from build/badgevms.elf...
add symbol table from file "/home/moomin/Desktop/badge/firmware/build/bootloader/bootloader.elf"
^CQuit
(gdb) target remote /dev/ttyUSB0
Remote debugging using /dev/ttyUSB0
^CQuit
(gdb) quit
</pre>

===== Resolution =====
Yet to be answered.
==== [1] After installing OTA update, application updates AND System Update "BadgeVMS Firmware, Version 4, Main Badge Firmware" the system restarts showing System Updates => "Updates available 1" => "BadgeVMS Firmware, Version 4, Main Badge Firmware". Selecting it, installing it and autorstarting leads back to this same screen. I seem to be stuck in a loop of the update process. ====
* => Shut down your badge by double tapping the power button. Restart. You should now see the application WHY Application Launcher.
** => But double-tapping the power button doesn't shut down the badge...
*** hold ot down for 13+ seconds for a hard reboot.

== BadgeHub related Questions/Issues ==
==== [2] How do I get apps from the BadgeHub onto the Badge? Is it possible without an SD card (I don't have one). I can build apps and flash the firmware, but I have no idea how to get pre-compiled ELFs on there. ====
* => If you have a SD card (if not, the mysteryhack village has a vending machine): Create the folder stucture ./BADGEVMS/APPS on there. In there, create a folder named like the badge hub project name. Download and put the .elf in there. Create a json file with the project name next to the folder and put the key/values for name, unique_identifier, version and binary_path in there. binary_path is just the full name of the .elf file.
** => the mysteryhack village vending machine has been out of SD cards since day 0 or 1

User:Jstsmthrgk

2025-02-06T18:54:57Z

Frederik:

{{UserInfo
|Name=jstsmthrgk
|Village=Village:/dev/lol
|HackerSpace=/dev/lol
|Languages=EN
|NickName={{PAGENAME}}
}}

User:Frederik

2025-02-06T18:54:48Z

Frederik:

{{UserInfo
|NickName={{PAGENAME}}
|Languages=EN
|Village=Village:/dev/lol
|HackerSpace=/dev/lol
}}

User:Frederik

2025-01-11T14:58:04Z

Frederik:

{{UserInfo
|NickName={{PAGENAME}}
|Languages=EN
|HackerSpace=/dev/lol
}}

User:Frederik

2025-01-11T14:54:20Z

Frederik: create user page

{{UserInfo
|NickName={{PAGENAME}}
|Languages=EN
|HackerSpace=
}}