Badge Issues

2025-08-25T18:20:03Z

Amoksepp:

== 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 ===
==== [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/FSK/... radio chip (RA-01SH package containing a Semtech chip). When you do not transmit (send out something) with the chip, then you do not need to connect the antenna or solder in the SMA socket. You would have a bad reception if you try to receive something but that is not a technical issue, just a practical issue.
* As soon as you start transmitting, you HAVE to connect a antenna to the SMA connector you have soldered into. Otherwise at every transmission, you are hitting and hurting hardly the chip and this would destroy the RF part of the Semtech chip. Its the same when you connect a wrong antenna for a different frequency you plan to transmit onto.
* If at some point a usabe Meshtastic firmware is available for the badge and you configure the 'region', Meshtastic automatically transmit beacons. That is why you always have to connect the correct antenna to the badge when using Meshtastic.
* [[Badge/LoRa-Antenna|Read more about the LoRa antenna]]

==== [2] Where/how to solder the antenna socket/connector? ====

Before soldering on the antenna socket, consider if you really need to. The section of the wiki about using the badge without the antenna attached has some important information.

Steps for soldering:
It's recommended to read through these steps first before you get going.

* Shut down badge. Remove batteries or other power sources.
* Take the badge apart by unscrewing all four screws, removing the front plate and the 3D printed spacer(s).
** The best fitting bit is a J0/JIS0, some iFixit kits have them. A PH0/00 may work but be careful to not strip the screw or poke in to your hand while applying pressure for unscrewing.
* Location: in the top right corner tightly along side the screen, you should now see 5 holes marked as "J5". (See image)
[[File:Badge back antenna socket holes.jpg|thumb|none]]
* Check if your 3D printed spacer has holes in that spot. The socket will be inserted in these holes from the back of the badge. The legs will stick through on the front side of the badge. Once they are soldered the spacer needs to allow some room for the pins to poke through it. If the spacer won't fit, a quick fix would be to widen the holes with you soldering iron, or use a drill to increase the size.
* The center hole of the pattern is for the signal. The surrounding 4 holes are connected to ground and provide points to strengthen the connection between the socket and the PCB. (See image)
[[File:Badge front antenna socket details.jpg|thumb|none]]
* Insert the socket from the back of the PCB. The component should be on the back of the badge where the battery holders are. The legs should stick out on the screen side of the badge.

Note: some of the holes for soldering on the socket are very close to the side of the screen. The screen is delicate and will take damage from the heat of your soldering iron. How to deal with this? (See image)

* Easy:
** Keep your iron away from the side of the screen.
** Solder only the two pins on the outside of the PCB for rigidity, and the center pin for signal. This gives you less than half a centimeter to work with. Be careful with the antenna and socket as
* Expert:
** Put one or more layers of true Kapton tape (M3 5413) on the side of the screen, all the way down to the PCB to protect the screen from heat. (See image)
[[File:Badge front kapton tape.jpg|thumb|none]]
** Still make sure your soldering iron stays away from the screen as much as possible at all times.
** Solder the four outside pins for maximum rigidity and the center pin for signal.
* Possibly hard to execute:
** Ideally you take the screen off which can be done with some dental floss, although this could damage the screen.

==== [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|none]]

Answer: This should not be an issue. This is happening often on many cells that are been taken out and put back in. For example in devices that can not charge the cells on their own.
The complete outer shell of the 18650 battery is connected to the negative terminal of the battery. Its a extreme long negative pole that is going around the whole battery from the bottom of the battery to the top of the battery. A common thing when such thing happen and the batteries are getting wet is moisture getting in there and staying between the wrap and the battery. Maybe put some thin capton tape over the hole if you want to recover the wrapping functionality.
The wrapping of the cells can also be replaced. For example take this as a opportunity to get wrapping colored in your favorite color for replacement.
The only relevant part is the upper part between the positive pole of the battery and the battery cell itself.

==== [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? ====

Unofficial answer from the OP... I was able to pry the cell holders loose using a craft knife and a little force. However, this revealed some pools of uncured epoxy, as shown in the photo. The Internet suggests leaving the badge outside for a bit of sunbathing, as the solar UV will help the epoxy to set.
* ⚠️ [https://hsnl.social/@m@martinh.net/115043789003085726 Uncured epoxy] [https://martinh.net/@m/115043788673993241 second link] - wear gloves.

[[File:Badge-post-op.jpg|thumb|none|alt=WHY badge which has had the cell holders removed using a craft knife. Along the long edge of each cell holder there is some pooling of uncured epoxy.|WHY badge with cell holders removed - showing uncured epoxy]]

==== [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? ====
A simple solution is to print out a 18650 plastic battery cell dummy the way you want it. There are many different styled 18650 dummy's out there. Take the one that fit your need the best.

==== [9] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it? ====
You can simply use an exacto knife/stanley knife to pry it off. It will usually come off clean.
Ideally you leave the top of the battery holder covered, or use a case so it can't short-circuit.
* ⚠️ [https://hsnl.social/@m@martinh.net/115043789003085726 Uncured epoxy] [https://martinh.net/@m/115043788673993241 second link] - wear gloves.

==== [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.

=== 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] 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)
* => https://wiki.why2025.org/Badge#m.2_connector

==== [8] Can not turn off
badge while charging. ====
Yet to be answered.

==== [10] Badge updates apps after starting an app that isn't the updater ====
Yet to be answered.

==== [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.

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
<s>=>There are two solutions for this.
* Print out a complete replacement for the spacer and the cover like for example here: https://www.printables.com/model/1386148-why2025-badge-2-in-1-front-panel-and-spacer
* Print out just the spacer: https://www.printables.com/model/1385989-why2025-badge-spacer-with-more-space-for-lora-ante </s>
This does not concern the spacers, but the white layers that is adhesed on the PCB where the keyboard is.

==== [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. Screen also wobbles horizontal after few minutes (see topic above) ====
Yet to be answered.

[[File:PXL 20250815 195829061.jpg|thumb|none]]

==== [2] 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.

My guess is that this is a [https://nl.aliexpress.com/item/1005007755047389.html PH 2.0 horizontal surface mount connector]? The connector is indeed PH2.0, LCSC part number [https://www.lcsc.com/product-detail/C295747.html C295747] (info taken from the KiCad design file)
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]
The Audio-Chip is a "MAX98357A", according to the datasheet 4Ohm or 8Ohm speakers both work. There are some requirements for the inductance, but its really hard to find a speaker that does not meet them.

TL;DR: Get any small speaker, add a JST-PH connector and have fun.

==== [2] 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.

==== [1] IO4 has shared usage, what is the recommendation for it? ====
Options we have are:
# 1) Break-out to header at top of badge (R45 connected - default)
# 2) On Carrier Board above the screen there is place for 6 LEDs (R51 connected)
# 3) Front Panel has place for 4 LEDs (R52 connected)

So it seems we have options on usage, but to have same app-behavior it would be good to know (or set) recommendations
Technically, the LEDs could all be used by connecting the Data Out of last Carrier Board LED to the IO4 point of the Front Panel and moving the resistor from R45 to R51. Is this recommended at all?
In that case the order of LEDs would be 0-5 for Carrier Board and 6-9 for Front Panel.

What would be the size of the Carrier Board LEDs? Looking at schematics, can the team confirm it is the WS2812B 3535 ?

Yet to be answered.

==== [1] IO3 has shared usage; header breakout or vibration motor ====
More of a good-to-know:
# 1) Break-out to header at top of badge (R53 connected - default)
# 2) Vibration Motor (R49 connected)

If you want to use the vibration motor, move the resistor from R53 to R49

==== [1] Camera usage? ====
Connector J6 is a 15 pin for MIPI CSI
* Is the firmware ready for this?
* What type of camera would work with this?

Yet to be answered.

==== [1] Is Lora usable without soldering? ====
The Kicad files showing that it was planned to use the RA-01H Chip for Lora. On my board I have the RA-01SH version. This chip has the same shape and most of the pins are equal but some are different. So the RA-01SH Version has TXEN, RXEN and BUSY Pins. Some of them are not connected as they are not needed for the old RA-01H Version.
* I know there is no LoRa support yet. But will it be possible to use without soldering additional wires?
* See [[Project:Meshtastic_on_the_WHY2025_badge]]. Be aware: It requires soldering two GPIOs on the LoRa radio to the ESP32C6 and the firmware overwrites the ESPHosted firmware, so the badges loses all WiFi and Bluetooth functionality. Also, the screen and keyboard backlight PWM is wired to the C6, so meshtastic should be modified or configured to enable this outputs.

Yet to be answered.

== Badge User 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.
==== [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" 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?

==== [5] The Hello program doesn't do anything ====

The Hello program is a minimal program that outputs "Hello BadgeVMS world!" to the serial console. Nothing more.

==== [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.
==== [12] 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 and Safari do not support the Web Serial API and can't be used for the badge flasher.
** The USB cable must be in the socket on the side. Not the bottom.
** Windows: the correct COM port is named "USB Serial". Not "USB Jtag/Serial" or "CDC"
** macOS: the serial port is called USB Serial with device name cu.wchusbserial10 or similar
?? 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.
==== [1] How to get the missing apps after reflashing the badge? ====
I have two badges. Badge 1 flashed at the event, and Badge 2 reflashed with "BadgeVMS post-event" using "WHY2025-Open" SSID at home and the web flasher https://why-prog.heplaphon.com/.

Badge 1 shows 11 Applications Available: Game of Life v1, Eat Cheese v1, crackme v3, DOOM Shareware v1, MicroPython v1.0.1, Celeste Classic v1.1, c64emu v2, why2025_sponsors v1, WHY 2025 OTA updater v3, SNAKE! v3, hello v5.

Badge 2 shows 6 Applications Available: WHY2025 Sponsors v1, WHY 2025 OTA updater v4, Name tag v6, SNAKE! v3, hello v5, System settings v1.

How to get the missing apps on the post-event firmware?

[Solved] : Ensure the WIFI and DHCP works...

=== 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]]
==== [2] 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.
==== [1] I have damaged my screen :c I cannot find the exact parts list, is there some info? Aliexpress Link? :D ====
??
==== [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]

==== [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.

==== [1] How to update using the Web Updater if not recognising the port? ====
Use the side USB, not the bottom one. Maybe an idea to put this on the website itself as well.

Wrong port: You are probably seeing a ESP32-C6 type of chip instead of a ESP32-P4. lsusb will show a device with ID 303a:1001 Espressif USB JTAG/Serial debug unit and dmesg | grep tty will show it in /dev/ttyACM0 with a VID:PID of ox303a:0x1001

Right port: dmesg | grep tty should show something like ttyS4 at I/O 0x3060 (irq = 19, base_baud = 115200) is a 16550A (in Linux if the badge is plugged into the side port.)

=== [1] System settings app not launching ===
Even after installing the lastest BadgeVMS 12 update released tonight (19.08.2025) via OTA, the System settings app is not launching. The serial console is printing:
<pre>
W (85596) TCA8418: Got keyboard event raw 0xbb scancode 0x28
Launching: System settings
W (85666) ELF: No VMEM info found
W (85706) task: Start ELF file entrypoint at 0x4a03ff00
Task 9 caused an unhandled exception, Cerberos will deal with it
W (85706) HADES: Stripping PID 9 of its worldy possessions
W (85706) task: Cleaning up open filehandle 0
W (85716) task: Cleaning up open filehandle 1
W (85716) task: Cleaning up open filehandle 2
W (85716) HADES: Task 9 escorted to my realm
</pre>
The installed version of System Settings is v2, despite BadgeHub mentioning a v3. No further OTA Updates are offered to the device.

== 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] 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

WHY2025 wiki - User contributions [en]

Badge Issues

User:Amoksepp

User:Amoksepp

User:Amoksepp