WHY2025 wiki - User contributions [en]

Badge/LoRa-Antenna

2025-08-21T13:45:15Z

Fbb: Add more information to summary because of possible questions

== WHY2025 badge LoRa antenna ==

The badge comes with a LoRa, FSK, ... radio module [https://fcc.report/FCC-ID/2ATPO-RA-01SH/5055365.pdf Ra-01SH] containing a [https://www.semtech.com/products/wireless-rf/lora-connect/sx1262 Semtech SX1262] capable of operating between 803-930MHz. In order not to damage this radio module, do not use transmission functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is not tuned at the correct frequency. Several measurements confirm that. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz. But this is not the case for all antennas. There is high variation at what frequency the antenna is tuned by the manufacturer.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb|Fixed antenna to use in Europe]]

== SUMMARY ==

You can correct your antenna frequency by properly tuning it.
If you do not want or can not do the measurements, hand out the antenna to some Ham Radio people or other hackers who would have fun fixing the antenna and get yourself a proper antenna. The SMA-connector can also be reused for other custom antenna builds. Do not throw away things other people could and would like to use!

Be careful when ordering cheap no name antennas. There are many terrible antennas out there that have issues like this one. In general you want to have access to a VNA to be able to detect issues like this and not get scammed.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|-
| Fbb || || >4 at EU frequency || 915MHz || fixed by soldering copper (see picture)
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

File:Antenna-fixed.jpg

2025-08-21T13:35:08Z

Fbb: Simplify description

Fixed antenna for EU usage

Badge/LoRa-Antenna

2025-08-21T13:33:53Z

Fbb: Simplify description

== WHY2025 badge LoRa antenna ==

The badge comes with a LoRa, FSK, ... radio module [https://fcc.report/FCC-ID/2ATPO-RA-01SH/5055365.pdf Ra-01SH] containing a [https://www.semtech.com/products/wireless-rf/lora-connect/sx1262 Semtech SX1262] capable of operating between 803-930MHz. In order not to damage this radio module, do not use transmission functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is not tuned at the correct frequency. Several measurements confirm that. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz. But this is not the case for all antennas. There is high variation at what frequency the antenna is tuned by the manufacturer.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb|Fixed antenna to use in Europe]]

== SUMMARY ==

You can correct your antenna frequency by properly tuning it.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|-
| Fbb || || >4 at EU frequency || 915MHz || fixed by soldering copper (see picture)
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

Badge/LoRa-Antenna

2025-08-21T13:25:19Z

Fbb: Link to Ra-01SH without additional build in PA

== WHY2025 badge LoRa antenna ==

The badge comes with a LoRa, FSK, ... radio module [https://fcc.report/FCC-ID/2ATPO-RA-01SH/5055365.pdf Ra-01SH] containing a [https://www.semtech.com/products/wireless-rf/lora-connect/sx1262 Semtech SX1262] capable of operating between 803-930MHz. In order not to damage this radio module, do not use transmission functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is not tuned at the correct frequency. Several measurements confirm that. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz. But this is not the case for all antennas. There is high variation at what frequency the antenna is tuned by the manufacturer.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb|Fixed antenna for EU ISM band]]

== SUMMARY ==

You can correct your antenna frequency by properly tuning it.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|-
| Fbb || || >4 at EU ISM || 915MHz || fixed by soldering copper (see picture)
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

Badge/LoRa-Antenna

2025-08-21T13:22:11Z

Fbb: Add picture description

== WHY2025 badge LoRa antenna ==

The badge comes with a LoRa, FSK, ... radio module [https://web.archive.org/web/20250821130358/https://en.ai-thinker.com/Uploads/file/20240927/20240927114430_30249.pdf Ra-01SH] containing a [https://www.semtech.com/products/wireless-rf/lora-connect/sx1262 Semtech SX1262] capable of operating between 803-930MHz. In order not to damage this radio module, do not use transmission functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is not tuned at the correct frequency. Several measurements confirm that. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz. But this is not the case for all antennas. There is high variation at what frequency the antenna is tuned by the manufacturer.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb|Fixed antenna for EU ISM band]]

== SUMMARY ==

You can correct your antenna frequency by properly tuning it.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|-
| Fbb || || >4 at EU ISM || 915MHz || fixed by soldering copper (see picture)
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

Badge/LoRa-Antenna

2025-08-21T13:14:44Z

Fbb: There have to be some RF misunderstanding when reading the 'especially for local communications'. The health of a transmitter is not related to its range. These are two different topics.

== WHY2025 badge LoRa antenna ==

The badge comes with a LoRa, FSK, ... radio module [https://web.archive.org/web/20250821130358/https://en.ai-thinker.com/Uploads/file/20240927/20240927114430_30249.pdf Ra-01SH] containing a [https://www.semtech.com/products/wireless-rf/lora-connect/sx1262 Semtech SX1262] capable of operating between 803-930MHz. In order not to damage this radio module, do not use transmission functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is not tuned at the correct frequency. Several measurements confirm that. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz. But this is not the case for all antennas. There is high variation at what frequency the antenna is tuned by the manufacturer.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb]]

== SUMMARY ==

You can correct your antenna frequency by properly tuning it.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|-
| Fbb || || >4 at EU ISM || 915MHz || fixed by soldering copper (see picture)
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

Badge/LoRa-Antenna

2025-08-21T13:11:03Z

Fbb: Some parts was written too unspecific. My antenna had a terrible SWR at the EU ISM band

== WHY2025 badge LoRa antenna ==

The badge comes with a LoRa, FSK, ... radio module [https://web.archive.org/web/20250821130358/https://en.ai-thinker.com/Uploads/file/20240927/20240927114430_30249.pdf Ra-01SH] containing a [https://www.semtech.com/products/wireless-rf/lora-connect/sx1262 Semtech SX1262] capable of operating between 803-930MHz. In order not to damage this radio module, do not use transmission functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is not tuned at the correct frequency. Several measurements confirm that. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz. But this is not the case for all antennas. There is high variation at what frequency the antenna is tuned by the manufacturer.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb]]

== SUMMARY ==

You can improve your antenna performance by properly tuning it, however the current antenna will be allright to use, especially for local communications.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|-
| Fbb || || >4 at EU ISM || 915MHz || fixed by soldering copper (see picture)
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

Badge/LoRa-Antenna

2025-08-21T12:54:23Z

Fbb: /* measurement results */

== WHY2025 badge LoRa antenna ==

Your badge comes with a LoRa radio module installed operating on the 868MHz LoRa band. In order not to damage your badge, do not use LoRa functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is bad, but several measurements confirm that, while not ideal, the antenna is fit for purpose. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz.

While performance could be better, this is an acceptable result.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb]]

== SUMMARY ==

You can improve your antenna performance by properly tuning it, however the current antenna will be allright to use, especially for local communications.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|-
| Fbb || || >4 at EU ISM || 915MHz || fixed by soldering copper (see picture)
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

Badge/LoRa-Antenna

2025-08-21T12:49:21Z

Fbb: Picture fixed antenna

== WHY2025 badge LoRa antenna ==

Your badge comes with a LoRa radio module installed operating on the 868MHz LoRa band. In order not to damage your badge, do not use LoRa functionality before properly installing a connector and antenna.

There was some indication that the antenna that was handed out with the badge is bad, but several measurements confirm that, while not ideal, the antenna is fit for purpose. It looks like the manufacturer wanted to sell the same antenna for both 868MHz and 915MHz and placed it's tuned frequency in between at ~890MHz.

While performance could be better, this is an acceptable result.

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

[[File:Antenna-fixed.jpg|thumb]]

== SUMMARY ==

You can improve your antenna performance by properly tuning it, however the current antenna will be allright to use, especially for local communications.

== measurement results ==
{| class="wikitable"
|+ Table with measurement results
|-
! measured by !! return loss !! VSWR !! resonance at frequency || remarks
|-
| {{UserLink|Pa3weg}} || 13.64dB || 1.52 || 889.8MHz || measured S11 (return loss)
|-
| {{UserLink|Purple}} || 18.49dB || 1.27 || || measured VSWR
|-
| Ash || 11.73dB || 1.7 || || measured VSWR
|}

== Comment ==

Purple: My antenna measures very acceptable at 1.27 SWR for 868Mhz, considering the size and the affordability of the antenna I don't see this as an issue? I'd be happy if the antenna did 1.5 SWR or better at its size. It's not like the chip cares much either as long as it's not 3.0 or worse?

[[File:Why2025antennaswr.jpg|thumb]]

- Can a different antenna be used instead of trying to adapt this one?

Answer: Yes of course :)

Ash: I also measure an SWR of around 1.7, but definitely looks like a 915 antenna with a low of 1.2

Wouter ({{UserLink|Pa3weg}}): I also tested mine and it looks like the antenna was made to resonate between the two bands so it would do OK for both! Return loss is >13dB for both bands. Note this is not measured with a fully calibrated set-up.
[[File:VNA plot of badge antenna.jpg|thumb|alt=VNA plot of badge antenna|VNA plot of badge antenna by @pa3weg with the resonance at ~890MHz, right between 868 and 915 MHz]]
[[File:Mic stand with LoRa antenna on it.jpg|thumb|Microphone stand with the LoRa antenna under test. The red line shows the calibration boundary.]]

File:Antenna-fixed.jpg

2025-08-21T12:48:04Z

Fbb:

Fixed antenna for EU ISM band

Badge Issues

2025-08-21T12:38:06Z

Fbb: /* Answered */

== 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|LoRa antenna is not for EU usage!]]

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

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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

Badge Issues

2025-08-21T12:37:29Z

Fbb: /* Unanswered */

== 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|LoRa antenna is not for EU usage!]]

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

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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

Badge Issues

2025-08-21T12:36:48Z

Fbb: /* Unanswered */

== 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|LoRa antenna is not for EU usage!]]

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

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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:35:25Z

Fbb: /* Unanswered */

== 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|LoRa antenna is not for EU usage!]]

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:34:53Z

Fbb: /* Unanswered */

== 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|LoRa antenna is not for EU usage!]]

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:33:36Z

Fbb: /* Answered */

== 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|LoRa antenna is not for EU usage!]]

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:33:12Z

Fbb: /* Answered */

== 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|LoRa antenna is not for EU usage!]]

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:30:09Z

Fbb: /* Answered */

== 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/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|LoRa antenna is not for EU usage!]]

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:28:59Z

Fbb: /* Unanswered */

== 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/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|LoRa antenna is not for EU usage!]]

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

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:25:33Z

Fbb: /* Answered */

== 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/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|LoRa antenna is not for EU usage!]]

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

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:23:49Z

Fbb: /* Unanswered */

== 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/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|LoRa antenna is not for EU usage!]]

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

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:22:12Z

Fbb: /* Answered */

== 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/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|LoRa antenna is not for EU usage!]]

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

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

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

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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge Issues

2025-08-21T12:21:27Z

Fbb: /* Unanswered */

== 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/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|LoRa antenna is not for EU usage!]]

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

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

==== [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

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

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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

Badge App Requests

2025-08-21T12:10:38Z

Fbb: /* Retro-Go */

== Please edit this page ==

'''Please edit this page to report which app you are dreaming of. Maybe some genious developer without ideas can pick this up.
'''
=== atmosphere and pressure stats/a "tricorder"===
* [6 people want this]
''' An app that shows the stats of the BME690 -> atmosphere, pressure, temperature, air quality, as well of the BMI270 -> orientation/gyro,
possibly also attached external sensors,
possibly also able to log to a text file on the SD card.

Remark from someone else: the badge has no proper CO2 sensor, I'd appreciate it if the app in question would not include eCO2/CO2eq, as [https://queer.party/@ao/111779978098588711 it's a completely made up number that differs significantly from the real number, in a non-correlating way]. It's very misleading, not showing it is better than showing a completely fake number.

=== LED Matrix add-on app ===
* [1 people want this]
''' Like the other add-ons that were for sale, we need apps to use them. So a scrolling or changing text on the led matrix add-on would be great! '''

=== MP4/Media player ===
* [4 people want this]
''' Pretty much as the title states. A media player app that will let me choose an mp4 file to play from a list of existing files. Some very rudimentary controls like play, pause, rewind, forward. Watching Shrek in style.'''

=== Badge stats ===
* [2 people want this]
'''I would love an app that shows how many badges have come online, same as what is visible on the [https://stats.why2025.org/d/568320c2-75ff-4278-8d89-42b9e18fa04b/why20253a-badgehub?orgId=1&from=now-6h&to=now&timezone=browser badge grafana dashboard]'''

=== Subreddit or something alike ===
* [1 people wants this]
'''Maybe somebody can start a subreddit (or something alike) so we can ask questions about the badge and exchange ideas?
'''

=== Battery check app ===
* [3 people wants this]
''' When you have a case it is hard to check how full the badge is. It would be nice to have a digital indicator of this.

'''

=== LoRA chat app / run Meshtastic LoRa stuff (merged) ===
* [50 people want this] (merged 34 + 17)
'''Would love to see Meshtastic (https://meshtastic.org) running on the badge to chat with people around me. As App or separated firmware.

Please contact the people from:
[[Project:Meshtastic on the WHY2025 badge]]
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge
https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h
'''

=== SSH Client ===
* [30 people want this]
''' A SSH client that can be used for the badge, to connect to SSH servers. Making the badge a powerhouse of a remote-in device. Support for ed25519 keys would be much appreciated. '''

I started to work on this as a litte agentic coding experiment. You can see the current state here: https://github.com/kaistierl/why2025-badge-firmware/tree/main/sdk_apps/sshterm - there is a basic terminal emulation already, but SSH and networking are not yet implemented. ~[[User:Cyb3rk4t|cyb3rk4t]]

=== Web browser ===
* [5 people want this]
''' A basic web browser that can render (basic) HTML'''

=== WHY 2025 Design App ===
* [3 people want this]
'''A client for the awesome WHY2025 design/logo/nametag generator, see https://design.why2025.org/'''

=== WHY 2025 MQTT Client ===
* [5 people want this]
'''Something where you can fill in an MQTT topic and see the data from https://mqtt.why2025.org/'''

=== Home Assistant support ===
* [14 people want this]
'''It would be nice to use the badge in combination with Home Assistant.
Luxim is already planning to work on this, will update once a working prototype can be made public. '''

=== PICO-8 Fantasy Console ===
* [3 people want this]
'''Run PICO-8 cartridges (https://www.lexaloffle.com/pico-8.php). Not quite sure if this is even possible or not, but it might be a cool idea :P'''

=== Retro-Go ===
* [8 people want this]
'''
Run e.g. Gameboy Color games:
https://github.com/ducalex/retro-go
'''
Thanks to the powerful ESP32-P4 even GENESIS, SNES and GBA could work: https://github.com/ducalex/retro-go/issues/211

=== App Manager ===
* [14 people wants this]
'''Download and update Apps via WiFi from [https://badge.why2025.org/ BadgeHub] directly to SD card or delete them from the storage so we don't have to disassemble half of the badge or rebuild the firmware every time we want to get new apps.'''

=== Power Off App ===
* [1 people wants this]
'''Some casings make the on/off button hard to reach without a pen. It would be nice to have a shutdown command/app in the OS.'''

=== External Keyboard/Macro pad/Jiggler ===
* [1 people wants this]
'''If Badge is able to present as a USB HID device, app to allow it to be used to send keyboard codes to a connected computer, send definable macros using the action buttons, a mode to send occasional scroll locks or other keystrokes to keep a host computer awake, perhaps even send mouse inputs somehow, so badge can be used as a handy input device'''

=== Fileserver via CopyParty ===
* [2 people wants this]
'''It would be great to execute the CopyParty FOSS project to execute a local fileserver so that the badge could host and serve files over CIFS / SSH / HTTP. According to the project description, it's a single python file with no deps, but I am not sure if it will run over the micropython environment. Extended information available over [https://github.com/9001/copyparty CopyParty Github repo]

=== FlipperZero // Bruce (successor of CapibaraZero) ===
* [4 people wants this]
'''It would be wonderful if I could use the badge in a manner similar to a FlipperZero or Bruce (successor of CapibaraZero), with all the tools that are supported by this hardware.'''

The most RF features FlipperZero and other tools got famous for are based on the CC1101 chip. Such a chip would have to be connected externally to the badge. Second most things the FlipperZero got famous for is the NFC functionality that is also not part of the badge. It would be probably a better idea to get a FlipperZero clone like the T-Embed CC1101 that have both parts already build in.

=== Serial interface ===
* [1 people wants this]
'''It would be nice to be able to use the gpio pins on the top to connect to a Serial Interface via UART for hardware hacking purposes'''

=== Note taking app ===
* [1 people wants this]
'''doesn't have to syncronise with anything (would be nice though) but have something to write down contacts or project ideas you have while wondering around whatever next camp will be'''

== Fulfilled requests ==
=== Name Tag app ===
* Fulfilled with: https://badge.why2025.org/page/project/why2025_namebadge

'''A simple app to set text you want shown on the badge, preferably it will remember the text. Bonus to flip the screen orientation and text formatting.'''

Status: Done.

=== WiFi Settings App ===
* [10 people want this]
'''Control your Wireless lan settings at home'''

Status: Done.

Badge App Requests

2025-08-21T12:07:31Z

Fbb: /* FlipperZero // CapibaraZero */

== Please edit this page ==

'''Please edit this page to report which app you are dreaming of. Maybe some genious developer without ideas can pick this up.
'''
=== atmosphere and pressure stats/a "tricorder"===
* [6 people want this]
''' An app that shows the stats of the BME690 -> atmosphere, pressure, temperature, air quality, as well of the BMI270 -> orientation/gyro,
possibly also attached external sensors,
possibly also able to log to a text file on the SD card.

Remark from someone else: the badge has no proper CO2 sensor, I'd appreciate it if the app in question would not include eCO2/CO2eq, as [https://queer.party/@ao/111779978098588711 it's a completely made up number that differs significantly from the real number, in a non-correlating way]. It's very misleading, not showing it is better than showing a completely fake number.

=== LED Matrix add-on app ===
* [1 people want this]
''' Like the other add-ons that were for sale, we need apps to use them. So a scrolling or changing text on the led matrix add-on would be great! '''

=== MP4/Media player ===
* [4 people want this]
''' Pretty much as the title states. A media player app that will let me choose an mp4 file to play from a list of existing files. Some very rudimentary controls like play, pause, rewind, forward. Watching Shrek in style.'''

=== Badge stats ===
* [2 people want this]
'''I would love an app that shows how many badges have come online, same as what is visible on the [https://stats.why2025.org/d/568320c2-75ff-4278-8d89-42b9e18fa04b/why20253a-badgehub?orgId=1&from=now-6h&to=now&timezone=browser badge grafana dashboard]'''

=== Subreddit or something alike ===
* [1 people wants this]
'''Maybe somebody can start a subreddit (or something alike) so we can ask questions about the badge and exchange ideas?
'''

=== Battery check app ===
* [3 people wants this]
''' When you have a case it is hard to check how full the badge is. It would be nice to have a digital indicator of this.

'''

=== LoRA chat app / run Meshtastic LoRa stuff (merged) ===
* [50 people want this] (merged 34 + 17)
'''Would love to see Meshtastic (https://meshtastic.org) running on the badge to chat with people around me. As App or separated firmware.

Please contact the people from:
[[Project:Meshtastic on the WHY2025 badge]]
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge
https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h
'''

=== SSH Client ===
* [30 people want this]
''' A SSH client that can be used for the badge, to connect to SSH servers. Making the badge a powerhouse of a remote-in device. Support for ed25519 keys would be much appreciated. '''

I started to work on this as a litte agentic coding experiment. You can see the current state here: https://github.com/kaistierl/why2025-badge-firmware/tree/main/sdk_apps/sshterm - there is a basic terminal emulation already, but SSH and networking are not yet implemented. ~[[User:Cyb3rk4t|cyb3rk4t]]

=== Web browser ===
* [5 people want this]
''' A basic web browser that can render (basic) HTML'''

=== WHY 2025 Design App ===
* [3 people want this]
'''A client for the awesome WHY2025 design/logo/nametag generator, see https://design.why2025.org/'''

=== WHY 2025 MQTT Client ===
* [5 people want this]
'''Something where you can fill in an MQTT topic and see the data from https://mqtt.why2025.org/'''

=== Home Assistant support ===
* [14 people want this]
'''It would be nice to use the badge in combination with Home Assistant.
Luxim is already planning to work on this, will update once a working prototype can be made public. '''

=== PICO-8 Fantasy Console ===
* [3 people want this]
'''Run PICO-8 cartridges (https://www.lexaloffle.com/pico-8.php). Not quite sure if this is even possible or not, but it might be a cool idea :P'''

=== Retro-Go ===
* [7 people want this]
'''
Run e.g. Gameboy Color games:
https://github.com/ducalex/retro-go
'''

=== App Manager ===
* [14 people wants this]
'''Download and update Apps via WiFi from [https://badge.why2025.org/ BadgeHub] directly to SD card or delete them from the storage so we don't have to disassemble half of the badge or rebuild the firmware every time we want to get new apps.'''

=== Power Off App ===
* [1 people wants this]
'''Some casings make the on/off button hard to reach without a pen. It would be nice to have a shutdown command/app in the OS.'''

=== External Keyboard/Macro pad/Jiggler ===
* [1 people wants this]
'''If Badge is able to present as a USB HID device, app to allow it to be used to send keyboard codes to a connected computer, send definable macros using the action buttons, a mode to send occasional scroll locks or other keystrokes to keep a host computer awake, perhaps even send mouse inputs somehow, so badge can be used as a handy input device'''

=== Fileserver via CopyParty ===
* [2 people wants this]
'''It would be great to execute the CopyParty FOSS project to execute a local fileserver so that the badge could host and serve files over CIFS / SSH / HTTP. According to the project description, it's a single python file with no deps, but I am not sure if it will run over the micropython environment. Extended information available over [https://github.com/9001/copyparty CopyParty Github repo]

=== FlipperZero // Bruce (successor of CapibaraZero) ===
* [4 people wants this]
'''It would be wonderful if I could use the badge in a manner similar to a FlipperZero or Bruce (successor of CapibaraZero), with all the tools that are supported by this hardware.'''

The most RF features FlipperZero and other tools got famous for are based on the CC1101 chip. Such a chip would have to be connected externally to the badge. Second most things the FlipperZero got famous for is the NFC functionality that is also not part of the badge. It would be probably a better idea to get a FlipperZero clone like the T-Embed CC1101 that have both parts already build in.

=== Serial interface ===
* [1 people wants this]
'''It would be nice to be able to use the gpio pins on the top to connect to a Serial Interface via UART for hardware hacking purposes'''

=== Note taking app ===
* [1 people wants this]
'''doesn't have to syncronise with anything (would be nice though) but have something to write down contacts or project ideas you have while wondering around whatever next camp will be'''

== Fulfilled requests ==
=== Name Tag app ===
* Fulfilled with: https://badge.why2025.org/page/project/why2025_namebadge

'''A simple app to set text you want shown on the badge, preferably it will remember the text. Bonus to flip the screen orientation and text formatting.'''

Status: Done.

=== WiFi Settings App ===
* [10 people want this]
'''Control your Wireless lan settings at home'''

Status: Done.

Badge App Requests

2025-08-21T11:57:47Z

Fbb: /* LoRA chat app / run meshtastic lora stuff (merged) */

== Please edit this page ==

'''Please edit this page to report which app you are dreaming of. Maybe some genious developer without ideas can pick this up.
'''
=== atmosphere and pressure stats/a "tricorder"===
* [6 people want this]
''' An app that shows the stats of the BME690 -> atmosphere, pressure, temperature, air quality, as well of the BMI270 -> orientation/gyro,
possibly also attached external sensors,
possibly also able to log to a text file on the SD card.

Remark from someone else: the badge has no proper CO2 sensor, I'd appreciate it if the app in question would not include eCO2/CO2eq, as [https://queer.party/@ao/111779978098588711 it's a completely made up number that differs significantly from the real number, in a non-correlating way]. It's very misleading, not showing it is better than showing a completely fake number.

=== LED Matrix add-on app ===
* [1 people want this]
''' Like the other add-ons that were for sale, we need apps to use them. So a scrolling or changing text on the led matrix add-on would be great! '''

=== MP4/Media player ===
* [4 people want this]
''' Pretty much as the title states. A media player app that will let me choose an mp4 file to play from a list of existing files. Some very rudimentary controls like play, pause, rewind, forward. Watching Shrek in style.'''

=== Badge stats ===
* [2 people want this]
'''I would love an app that shows how many badges have come online, same as what is visible on the [https://stats.why2025.org/d/568320c2-75ff-4278-8d89-42b9e18fa04b/why20253a-badgehub?orgId=1&from=now-6h&to=now&timezone=browser badge grafana dashboard]'''

=== Subreddit or something alike ===
* [1 people wants this]
'''Maybe somebody can start a subreddit (or something alike) so we can ask questions about the badge and exchange ideas?
'''

=== Battery check app ===
* [3 people wants this]
''' When you have a case it is hard to check how full the badge is. It would be nice to have a digital indicator of this.

'''

=== LoRA chat app / run Meshtastic LoRa stuff (merged) ===
* [50 people want this] (merged 34 + 17)
'''Would love to see Meshtastic (https://meshtastic.org) running on the badge to chat with people around me. As App or separated firmware.

Please contact the people from:
[[Project:Meshtastic on the WHY2025 badge]]
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge
https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h
'''

=== SSH Client ===
* [30 people want this]
''' A SSH client that can be used for the badge, to connect to SSH servers. Making the badge a powerhouse of a remote-in device. Support for ed25519 keys would be much appreciated. '''

I started to work on this as a litte agentic coding experiment. You can see the current state here: https://github.com/kaistierl/why2025-badge-firmware/tree/main/sdk_apps/sshterm - there is a basic terminal emulation already, but SSH and networking are not yet implemented. ~[[User:Cyb3rk4t|cyb3rk4t]]

=== Web browser ===
* [5 people want this]
''' A basic web browser that can render (basic) HTML'''

=== WHY 2025 Design App ===
* [3 people want this]
'''A client for the awesome WHY2025 design/logo/nametag generator, see https://design.why2025.org/'''

=== WHY 2025 MQTT Client ===
* [5 people want this]
'''Something where you can fill in an MQTT topic and see the data from https://mqtt.why2025.org/'''

=== Home Assistant support ===
* [14 people want this]
'''It would be nice to use the badge in combination with Home Assistant.
Luxim is already planning to work on this, will update once a working prototype can be made public. '''

=== PICO-8 Fantasy Console ===
* [3 people want this]
'''Run PICO-8 cartridges (https://www.lexaloffle.com/pico-8.php). Not quite sure if this is even possible or not, but it might be a cool idea :P'''

=== Retro-Go ===
* [7 people want this]
'''
Run e.g. Gameboy Color games:
https://github.com/ducalex/retro-go
'''

=== App Manager ===
* [14 people wants this]
'''Download and update Apps via WiFi from [https://badge.why2025.org/ BadgeHub] directly to SD card or delete them from the storage so we don't have to disassemble half of the badge or rebuild the firmware every time we want to get new apps.'''

=== Power Off App ===
* [1 people wants this]
'''Some casings make the on/off button hard to reach without a pen. It would be nice to have a shutdown command/app in the OS.'''

=== External Keyboard/Macro pad/Jiggler ===
* [1 people wants this]
'''If Badge is able to present as a USB HID device, app to allow it to be used to send keyboard codes to a connected computer, send definable macros using the action buttons, a mode to send occasional scroll locks or other keystrokes to keep a host computer awake, perhaps even send mouse inputs somehow, so badge can be used as a handy input device'''

=== Fileserver via CopyParty ===
* [2 people wants this]
'''It would be great to execute the CopyParty FOSS project to execute a local fileserver so that the badge could host and serve files over CIFS / SSH / HTTP. According to the project description, it's a single python file with no deps, but I am not sure if it will run over the micropython environment. Extended information available over [https://github.com/9001/copyparty CopyParty Github repo]

=== FlipperZero // CapibaraZero ===
* [4 people wants this]
'''It would be wonderful if I could use the badge in a manner similar to a FlipperZero or CapibaraZero, with all the tools that are supported by this hardware.'''

=== Serial interface ===
* [1 people wants this]
'''It would be nice to be able to use the gpio pins on the top to connect to a Serial Interface via UART for hardware hacking purposes'''

=== Note taking app ===
* [1 people wants this]
'''doesn't have to syncronise with anything (would be nice though) but have something to write down contacts or project ideas you have while wondering around whatever next camp will be'''

== Fulfilled requests ==
=== Name Tag app ===
* Fulfilled with: https://badge.why2025.org/page/project/why2025_namebadge

'''A simple app to set text you want shown on the badge, preferably it will remember the text. Bonus to flip the screen orientation and text formatting.'''

Status: Done.

=== WiFi Settings App ===
* [10 people want this]
'''Control your Wireless lan settings at home'''

Status: Done.

Badge Issues

2025-08-20T13:17:29Z

Fbb: /* [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? */

== 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/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|LoRa antenna is not for EU usage!]]

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

==== [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. 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|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] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

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

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

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

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

Badge Issues

2025-08-20T13:13:34Z

Fbb: /* [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? */

== 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/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|LoRa antenna is not for EU usage!]]

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

==== [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. 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|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] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

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

==== [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? ====
Yet to be answered.

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

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

Badge Issues

2025-08-20T13:12:18Z

Fbb: /* [1] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? */

== 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/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|LoRa antenna is not for EU usage!]]

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

==== [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. 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|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] The white overlay(layer) between the keyboard and the PCB is missing, so typing does not work, can I obtain this somewhere? ====
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

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

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

[[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? ====
Yet to be answered.

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

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

Badge Issues

2025-08-20T13:08:05Z

Fbb: /* [2] Damaged wrapping of an 18650 battery, is this an issue? */

== 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/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|LoRa antenna is not for EU usage!]]

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

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

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

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

[[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? ====
Yet to be answered.

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

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

Badge Issues

2025-08-20T12:57:23Z

Fbb: /* [9] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it? */

== 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/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|LoRa antenna is not for EU usage!]]

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

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

Answer: if you are very sure it's only the heat shrink that is damaged, this should not be an issue. The outer shell of the battery is connected to the negative terminal so do make sure not to short it. Maybe put some electrical tape over it or just replace the heat shrink (find some 18650 heat shrink on your favorite webshop).
If there's a chance the outer shell is damaged too, better play it safe and drain the battery and turn it in for recycling.

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

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

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

[[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? ====
Yet to be answered.

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

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

Badge Issues

2025-08-20T12:54:38Z

Fbb: /* [8] The antenna isn't connected yet. Can I use the device without damaging anything? */

== 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/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|LoRa antenna is not for EU usage!]]

==== [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 of which can be done with some dental floss, although this could damage the screen.

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

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

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

Answer: if you are very sure it's only the heat shrink that is damaged, this should not be an issue. The outer shell of the battery is connected to the negative terminal so do make sure not to short it. Maybe put some electrical tape over it or just replace the heat shrink (find some 18650 heat shrink on your favorite webshop).
If there's a chance the outer shell is damaged too, better play it safe and drain the battery and turn it in for recycling.

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

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

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

[[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? ====
Yet to be answered.

==== [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]? Can the team confirm?
[[File:Screenshot 2025-08-18 LS1.png|thumb|none|LS1 connector from photo of prototype]]

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

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

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

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

Project:Meshtastic on the WHY2025 badge

2025-08-20T12:39:53Z

Fbb: Add warning at meshtastic that is 869,5Mhz in europe but the antenna is 915Mhz ISM band

{{Projects
|Name=Mesthastic on WHY badge
|Has project tag=meshtastic, badge
|Has description=A WiP port for the WHY badge
}}
* ⚠️ [[Badge/LoRa-Antenna|LoRa antenna is not for EU usage!]]

I am porting a meshtastic version that should work on the WHY badge. Currently it works and you can interact with it using the USB serial port.
Feel free to edit this page to add your developments and point to your own github repo with your progress.

The code is [https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge here] (note it is not the main git branch) and it is based on the c6 port [https://github.com/alexbegoon/firmware/tree/add%20seeed%20xiao%20esp32c6%20variant here]

Further instructions on compiling and flashing meshtastic can be found [https://meshtastic.org/docs/development/firmware/build/ here], be sure to use the correct git branch and use the "why2025-badge" variant (it should be the default one on my fork) - the USBC port for the ESP32C6 is the bottom one.

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.

Also, be aware, the LoRa radio [https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/7169/RA-01SH.pdf datasheet] shows different pinout from the KiCad schematics:

[[File:Captura de pantalla 20250811 155120.png]]

So, meshtastic requires the CAD (channel activity detection) and busy pins to be soldered between the LoRa radio and the ESP32, this is documented in [https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h this file], but you can edit at your pleasure.

You can see a modified badge here:

[[File:Badge-lora-solder.jpg]]

Next step when the radio is working should be porting this to have a fully functioning independent device:

[https://github.com/meshtastic/device-ui/tree/master Meshstastic Device UI]

Badge

2025-08-20T12:30:08Z

Fbb: Add link to antenna wiki page

{{whybox|title=WHY2025 Badge|content=
'''Warning'''
* ⚠️ [[Badge/Fire hazard|Fire Hazard]]
* ⚠️ [https://hsnl.social/@m@martinh.net/115043789003085726 Uncured epoxy] [https://martinh.net/@m/115043788673993241 second link] - wear gloves.
* ⚠️ [[Badge/LoRa-Antenna|LoRa antenna is not for EU usage!]]

'''Articles'''
* [https://why2025.org/post/494 Blogpost 01] - A First Look at the WHY2025 Badge: Prototyping Complete
* [https://why2025.org/post/697 Blogpost 02] - Build With Us: The WHY2025 Badge and the Last‑Mile Push
* [https://www.youtube.com/watch?v=-uMUSUYVGkU WHYCast Episode41]
* [https://tweakers.net/geek/237414/dit-is-de-why2025-badge-met-twee-esp32s-en-een-loramodule.html Tweakers article] (Dutch) - Dit is de WHY2025-badge met twee ESP32's en een loramodule

'''Documentation'''
* [https://badge.why2025.org/ BadgeHub] and its [https://badge.why2025.org/api-docs/ API Docs]
* [https://gitlab.com/why2025/team-badge Team:Badge GitLab repo] (files + documentation)
* Flash your badge with the BadgeVMS firmware at [https://why-prog.heplaphon.com/ WHY2025 Badge Web Flasher]
* Report your [[Badge Issues]]
* Report your [[Badge App Requests]]
* [[How to develop an app]]
* [[Badge/MacOS_Drivers]]
}}

<hr>

== Reflash your badge ==

You're home and the badge won't update over WiFi anymore?

Use the [https://why-prog.heplaphon.com/ WHY badge flasher] (requires Chrome or Edge browser).

Select "BadgeVMS post_event" for a firmware supporting WiFi setup.

If you don't want to install Chrome or Edge on your machine, you can compile the current firmware version yourself, using the instructions on [[How to develop an app]]. The updated firmware will automatically add the new settings app to your badge.

== Hardware repair ==
=== m.2 connector ===
If the m.2 connection is flaky, the system will probably boot-loop. Symptoms: serial output with hard crashes every few seconds, no backlight/picture. Bas' connector broke off entirely.

* https://hsnl.social/@bas/115048503119046256

[[File:Badge-broken-m2.jpg|thumb|none]]

Rework the connector with a bit of flux, solder etc and it should be back to normal. Recommended for everyone is to put two *small* drops of self-curing epoxy or a glue on either side of the connector to improve mechanical strength. A user recommended E6000 glue and to let it cure for 24hrs.

A soldering tutorial might appear within a week.

== Batteries ==

* Beware of the [[Badge/Fire hazard]] warning before you use batteries in the device.
* insert Cell Positive (+) side, which is the 'middle' of the badge, first, and Cell Minus (-), near the 'edge' of the badge, second.
* don't forget to take it out when not in use because of https://why2025.org/post/822
* you can flash with the batteries in, for charging you can use any of the two ports.

== Badge Case Info ==

Currently cases are designed around the prototype PCBs. The final boards might be slightly different, so best advise is currently to wait until (after) the camp with printing one - the badges will be usable without a case. Instead, maybe help with printing the 3mm full-frame spaces (see above).

• Designing your own case? Use the existing screw holes on the badge.
• Bring M2 screws, up to 15 mm in length depending on your case design.
• Badges function fully without a case.
• Note: Cases take much longer to print than spacers.

Case Examples by the community:
 
* [https://www.printables.com/model/1372316-why2025-badge-case Semi-official case] by @Dynom
* [https://www.printables.com/model/1376706-why-2025-badge-case-remix Remix of above for printing without supports]
* [https://www.printables.com/model/1377822-why2025-transparent-case Other case design which allows for transparent cases]
* [https://www.printables.com/model/1387194-slim-case-for-why2025-event-badge]
* [https://momakemore.com/micropages/why2025/ Two Case Designs by @MoMakeMore] (based on the cutouts by @Dynom)
** HEAVY - The Camp Case. Full feature, Heavy Duty.
** SLIM - After Camp: Minimal Design, minimal breakouts + Lora, no 18650 support
* [https://www.printables.com/model/1380554-why2025-badge-case-speedy-print-the-boat-hull Speedy Print Case by @MattGrayYes], which can print in under an hour on a Prusa MK4
* [https://www.thingiverse.com/thing:7118590 Top cover for the "semi-official case" by Shmuma (with and without logo versions)]

== Installing apps from BadgeHub via microSD Card ==
You need a microSD card for this.

# 1. Create the folder stucture ./BADGEVMS/APPS on there.
# 2. In the APPS folder, create a folder named like the badge hub project name.
# 3. Download the app from [https://badge.why2025.org/ BadgeHub] and put the .elf in there.
# 4. Create a json file with the project name next to the folder
# 5. Put the key/values for name, unique_identifier, version and binary_path (full name of the .elf file) in that json file.

== ℹ️🪛 Update! State of "Not assembled" Badges ==
For the badges that were handed out in an unassembled state, please make sure to follow this guide for assembly:

2 variants spacers were added to the white bags that were handed out with your badge:
* 1 variant has a fully printed frame with holes on each corner.
** This one needs to be placed between the badge carrier PCB and the front plate and will cover all electronics on the side.

* the other variant has (at least) 4 small black plastic cilinders. The cilinders look like the following:

[[File:Badge with small spacers.jpg|300px|alt=Badge with small spacers]]

Please make sure to install them between the badge and the front plate like this:

[[File:Spacers on badge.jpg|300px|alt=spacers on badge]]
[[File:Screenshot 2025-08-12 at 20.03.55.png|300px|alt=Badge with small spacer installed and front plate screwed.]]

You have installed these correctly if you can see a clear gap between the badge carrier PCB and the front plate like in the picture above.

== Badge Assembly at BadgeTent ==

We aim to conduct the full-scale assembly during the whole day of Friday, which will involve a maximum of 30 volunteers working in the 15*15 meters BadgeTent.

Assembly involves screwing everything together.

Assembling your first '''WHY2025''' badge might feel overwhelming, that’s okay.

Take your time, explore the parts, and build confidence.

With repetition:
* 1st time = You're learning. -> Instructions on how to handle the components will be provided.
* 5th time = You gain confidence by knowing your tools and how to grab them the best way.
* 500th time = Congratulations, you have accomplished the assembly and will have a Foxconn recruiter on the line.

Parts to assemble:
* CarrierBoard
* Keyboard Dome Layer
* Keyboard Silicon Layer
* 3mm Spacers
* 4x M2 Screws
* Front Panel PCB

If you want to help out in the Badge Assembly on Friday during the day -> then join this Signal group.

[https://signal.group/#CjQKIIORCgY9yjX3a834iz-RQeOQu80fIZtg-i3G56EYqnaQEhBaRn9aHmtLggM6oH7dWXC5 Badge Assembly - Signal group].

=== Lessons Learned during Badge Assembly ===

We encountered a small number of badges (three in total) where the Keyboard Dome Layer was slightly misaligned, leading to a few non-responsive keys. Thanks to our initial test-flashing process, we were able to detect these issues early and have since improved our application method for the Dome Layer.

To ensure quality, every badge will undergo a final quality control check, including a visual inspection of the epoxy and final firmware flashing, so that everyone receives a fully functional badge.

== LoRa Details ==

• The LoRa connector will not be pre-soldered but will be handed out as a compontent separately.
• You’ll also receive a screw-on LoRa antenna.

If you want to use another antenna, use a 868MHz antenna with a SMA connector.

Have a look in here:
https://github.com/n0p/mesthastic-fw-why-badge/tree/why2025-badge

https://github.com/n0p/mesthastic-fw-why-badge/blob/why2025-badge/variants/why_badge/variant.h

== SAO's ==
Shitty Add-Ons.

* https://github.com/a-little-wifi/WHY2025-SAOadapter

== Photo Sections ==

Pictures of 3D printed Full-frame Spacers:

[[File:Signal-2025-08-04-11-10-44-889.jpg|300px]]

[[File:Geraffel printed.jpg|300px]]

Pictures of WHY2025 Badge Cases:

[[File:Signal-2025-08-03-15-22-08-679.jpg|300px]]

[[File:Signal-2025-08-03-15-22-15-031.jpg|300px]]

[[File:20250804_140303.jpg|300px]]

Pictures of Final WHY2025 Badges with LoRa Antenna:

Martin has build and flashed Doom and the badge is now running Doom. See also [[Badge_Doom_how_to]].

[[File:Doom-Why-Badge.jpg|300px]]

== Replacement parts ==
Components and schematics can be found in the [https://gitlab.com/why2025/team-badge/Hardware/ hardware repository]: [https://gitlab.com/why2025/team-badge/Hardware/-/blob/main/Carrier/fp-lib-table?ref%20type=heads fp-lib-table]

* Keyboard (buttons) -- https://www.solder.party/keeb/
* Display -- [https://www.alibaba.com/product-detail/4-Inch-3-95-Square-LCD_1600816725949.html W395HDC001-A on alibaba]

== 3mm Full-frame Spacer Status ==

* [https://gitlab.com/why2025/team-badge/Hardware/-/blob/main/Spacer/3d_print/Full_Spacer_with_LoRa_Antenna_WHY2025.stl Original spacer]
* [https://www.printables.com/model/1385989-why2025-badge-spacer-with-more-space-for-lora-ante Slightly modified spacer with added space for the LoRa antenna solder joint]
* [https://www.printables.com/model/1386148-why2025-badge-2-in-1-front-panel-and-spacer Spacer + front plate combination by arturo182 for easier keyboard use]

=== Current Contributors ===
{| class="wikitable"
|+ Full-frame Spacer Contributors
|-
! Number
! Credits to
! Printer
! Layer
|-
| 783 || [[Village:Geraffel]] [[File:Geraffel 3D black.jpg|80px|thumb]] || YES, MANY ||
|-
| 343 || Sander {{UserLink|Jar0d}} || BambuLab H2D & X1C ||
|-
| 200 || Klaas ({{UserLink|KlaasYK}}) & Harry & Ilja || Prusa Mk4 & Mk3S and a big thank you to DJO Groningen! ||
|-
| 174 || {{UserLink|krekr}} (Gregor) || Creality K1 Max || 0.2mm
|-
| 105 || Michael ({{UserLink|MikeS}}) || Prusa MK3.9 and two dusted off MK2.5's ||
|-
| 100 || {{UserLink|rick}} || Prusa MK4S|| 0.20mm
|-
| 86 || {{UserLink|Edwinm}} || Prusa MK3 || 0.20mm
|-
| 72 || {{UserLink|Elborro}} || Bambu Lab X1C || 0.20mm
|-
| 71 || {{UserLink|Sndrsmnk}} || Bambu Lab P1S || 0.20mm
|-
| 68 || {{UserLink|Dude77}} || Bambu Lab P1S || 0.20mm
|-
| >60 || Henri ({{UserLink|Fashice}}) | already at badge tent| ||
|-
| 60 || {{UserLink|Renssies}} || - Bambu Lab X1C 2x (1 @ home, 1 @ work) - Bambu Lab A1 (@ Pixelbar, now @ Village) || 0.20mm
|-
|60 || {{userLink|ScoutHack42}} and buurman || Bambu Lab A1 || 0.20mm
|-
| 58 || Wouter ({{UserLink|Pa3weg}}) || Bambu LAN P1S || 0.20mm
|-
| 50 || Jan-Willem ({{UserLink|jwrm22}}) || Bambu Lab P1S || 0.20mm, suport material stacks
|-
| 46 || Saskia ({{UserLink|Sassy}}) || Prusa MK4S || 0.20mm
|-
| >45 || Alex ({{UserLink|Tinyledmatrix}}) || Prusa MK2, Bambulab A1 Mini, Qidi X-Smart3 ||
|-
|45 || {{userLink|kap}} || Bambu Lab X1C || 0.20 mm
|-
| 42 || {{UserLink|Jelmo2}} || ||
|-
|40 || {{UserLink|Willow}} || Bambu Lab P1S || 0.20mm
|-
|32 || {{UserLink|LordGaav}} || Voron V2.4 (V2.4523) || 0.20mm
|-
| 30 || Fabian || ||
|-
|30 || {{UserLink|Jap}} || Bambu Lab P1S || 0.20mm
|-
| 28 || {{UserLink|NinjaLikesCheez}} || Bambu Lab X1C || 0.20mm
|-
|21 || {{UserLink|Iikkak}} || Ender 3 S1 pro || 0.20mm
|-
|20 || {{UserLink|MagicalDuck}} || Ender 3 || 0.24mm
|-
|13 || {{userLink|Tijnoz}} || Prusa Mk3.9 || 0.20 mm
|-
|11 || {{UserLink|Bx}} || Bambu Lab X1C || 0.20mm
|-
|11 || {{UserLink|Galactum}} || Bambu Lab A1 || 0.20mm
|-
|>10 || {{UserLink|Habbie}} || Bambu Lab A1 || 0.20mm
|-
| 10 || Frankkie || ||
|-
|10 || {{userLink|Stare}} || Creality CR10 ||
|-
|10> || {{userLink|Jayblue}} || Flashforge Adventurer 5M || 0.20mm
|-
|9 || {{UserLink|q3k}} || MK3S+ || 0.20mm
|-
|8 || {{userLink|fmurodov}} || Bambu Lab A1Mini || 0.20 mm
|-
|6 || {{userLink|FrancisD}} || GEEETECH A20 || 0.20mm
|-
|6 || {{UserLink|Foorschtbar}} || Prusa XL || 0.20mm
|-
| 5 || {{UserLink|Luxim}} || Ender 3 v3 KE || 0.20mm
|-
|5 || {{userLink|PHiAX}} || Creality Ender3 S1 || 0.20 mm
|-
|4 || {{UserLink|Xylitol}} || CR-10S Pro || 0.20mm
|-
| 3 || Wouter || ||
|-
|2 || {{userLink|Miizix}} || Ender 3 || 0.20mm
|-
}

Current total: '''>2702''' units printed / 3500 needed (76.1%)

Add your amount and name to this list. Thank you.

Badge/LoRa-Antenna

2025-08-20T12:27:46Z

Fbb: Add page about wrong antenna

== WHY2025 badge LoRa antenna is 915Mhz and NOT 868Mhz ==

The antenna that was handed out with the badge is bad for the health of your lora module. The antenna is not made for Europe!

== General antenna information ==

Transmitters have to use antennas that fit the frequency the transmitter is capable to transmit and fit the used frequency. Antennas are resonant at specific frequencies. In general people using antennas try to meet a [https://en.wikipedia.org/wiki/Standing_wave_ratio SWR] of 1.2 or better. If you leave the antenna disconnected, the TX power of the transmitter gets reflected back into the transmitter and destroy the transmitter. That is why you should never use a transmitter without connected antenna.
When you use a wrong antenna, the result is about the same. The SWR is endlessly high and that is the same case like with missing antenna.

== How to fix ==

You need a VNA ( Vector Network Analyzer ). The antenna from the badge have to be connected to the VNA and then you have to solder on the antenna the missing amount of copper to reduce the frequency from 915Mhz to 868Mhz (or more exact 869,5Mhz for Meshtastic use in Europe).

TODO: This have been already done and the plan is to provide pictures of how it looks like when its been fixed.

== SUMMARY ==

DO NOT USE THE ANTENNA YOU GOT WITH YOUR BADGE IN EUROPE WHEN THE ANTENNA IS NOT CORRECTED. ITS A 915Mhz ISM BAND ANTENNA!!!

User:Fbb

2025-08-20T12:04:16Z

Fbb: create user page

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