WHY2025 wiki - User contributions [en]

Badge Issues

2025-08-11T11:03:15Z

Halbrot:

== Please edit this page ==

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

== Badge Hardware Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [3 People have this question/issue] screen is not turning on at all.
* [1 People have this question/issue] Can not turn off badge while charging.
* [1] How do I reset the badge on battery?
** => Applying usb power will reset the badge
* [1 People have this question/issue] The antenna isn't connected yet. Can I use the device without damaging anything?
* [2 People have this question/issue] 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?
* [1] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it?
* [2 People have this question/issue] The badge suddenly stopped working. (possibly coincides with first time plugging in USB-C and charging my own protected cells). Removing Batteries did not help. Re-Flashing with newest firmware did not help.
** => Reseating the ESP daughterboard (fitted with a screw) helped here.
Trace of boot-loop:
<pre>
./idf.py monitor

Order 8, (256) 1 blocks (256 pages)
Order 9, 0 blocks (0 pages)
Waste: 0 blocks (0 pages)
Total free pages: (calculated) 510 (stored) 510 max_order_free: 8
W (1078) ldo: The voltage value 0 is out of the recommended range [500, 2700]
E (1098) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (1098) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
HINT: Please verify if there is an SD card inserted into the SD slot. Then, try rebooting the board.
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
--- (inlined by) vPortExitCriticalMultiCore at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/portable/riscv/port.c:550
--- 0x4ff120a8: xTaskGenericNotify at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/tasks.c:5977
S0/FP : 0x00000000 S1 : 0x00000000 A0 : 0x0000002b A1 : 0x00000000
A2 : 0x00000004 A3 : 0x00000000 A4 : 0x20800008 A5 : 0x00000000
A6 : 0x00000003 A7 : 0x4000bf2a S2 : 0x00000000 S3 : 0x00000000 --- 0x4000bf2a: usb_serial_jtag_write at /home/bernhard/source/esp-idf_why2025/components/esp_driver_usb_serial_jtag/src/usb_serial_jtag_vfs.c:184
S4 : 0x00000000 S5 : 0x00000000 S6 : 0x00000000 S7 : 0x00000000
S8 : 0x00000000 S9 : 0x00000000 S10 : 0x00000000 S11 : 0x00000000
T3 : 0x4ff24aef T4 : 0x00000001 T5 : 0x00000000 T6 : 0x00000001
MSTATUS : 0x00011880 MTVEC : 0x4ff00003 MCAUSE : 0x00000001 MTVAL : 0x00000000
--- 0x00011880: SDLgfx_rotateSurface at :?
--- 0x4ff00003: _vector_table at ??:?
MHARTID : 0x00000001
</pre>

== Badge User Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3.
* [3 People have this question/issue] 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)
* [7 People have this question/issue] Blue screen. Nothing happening.
* [5 People have this issue] 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.
* [3 People have this question/issue] There is a stripe in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
*** 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)
* [2 People have this question/issue] There is a stamp HD3 in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
* [2 People have this question/issue] 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 People have this question/issue] 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?
* [1 Person has this question/issue] 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

== Badge Firmware Development related Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up?
* [5 People have this issue] The badge is not detect on my mac when I connect it by side port:
** => Install this driver: https://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html
*** Make sure to carefully follow the instructions, a 3rd party kernel extension is needed and restart might be needed as well.
*** '''Don't''' use brew, it has been reported not to work.
* [1 People have this question/issue] 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.
* [1 Person has this issue] 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

==BadgeHub related Questions/Issues==
* [0 People have this question/issue] Add your question/issue here or increase the number.

Badge Issues

2025-08-11T11:02:37Z

Halbrot:

== Please edit this page ==

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

== Badge Hardware Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [3 People have this question/issue] screen is not turning on at all.
* [1 People have this question/issue] Can not turn off badge while charging.
* [1] How do I reset the badge on battery?
** => Applying usb power will reset the badge
* [1 People have this question/issue] The antenna isn't connected yet. Can I use the device without damaging anything?
* [2 People have this question/issue] 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?
* [1] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it?
* [2 People have this question/issue] The badge suddenly stopped working. (possibly coincides with first time plugging in USB-C and charging my own protected cells). Removing Batteries did not help. Re-Flashing with newest firmware did not help. --> Reseating the ESP daughterboard (fitted with a screw) helped here.
Trace of boot-loop:
<pre>
./idf.py monitor

Order 8, (256) 1 blocks (256 pages)
Order 9, 0 blocks (0 pages)
Waste: 0 blocks (0 pages)
Total free pages: (calculated) 510 (stored) 510 max_order_free: 8
W (1078) ldo: The voltage value 0 is out of the recommended range [500, 2700]
E (1098) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (1098) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
HINT: Please verify if there is an SD card inserted into the SD slot. Then, try rebooting the board.
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
--- (inlined by) vPortExitCriticalMultiCore at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/portable/riscv/port.c:550
--- 0x4ff120a8: xTaskGenericNotify at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/tasks.c:5977
S0/FP : 0x00000000 S1 : 0x00000000 A0 : 0x0000002b A1 : 0x00000000
A2 : 0x00000004 A3 : 0x00000000 A4 : 0x20800008 A5 : 0x00000000
A6 : 0x00000003 A7 : 0x4000bf2a S2 : 0x00000000 S3 : 0x00000000 --- 0x4000bf2a: usb_serial_jtag_write at /home/bernhard/source/esp-idf_why2025/components/esp_driver_usb_serial_jtag/src/usb_serial_jtag_vfs.c:184
S4 : 0x00000000 S5 : 0x00000000 S6 : 0x00000000 S7 : 0x00000000
S8 : 0x00000000 S9 : 0x00000000 S10 : 0x00000000 S11 : 0x00000000
T3 : 0x4ff24aef T4 : 0x00000001 T5 : 0x00000000 T6 : 0x00000001
MSTATUS : 0x00011880 MTVEC : 0x4ff00003 MCAUSE : 0x00000001 MTVAL : 0x00000000
--- 0x00011880: SDLgfx_rotateSurface at :?
--- 0x4ff00003: _vector_table at ??:?
MHARTID : 0x00000001
</pre>

== Badge User Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3.
* [3 People have this question/issue] 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)
* [7 People have this question/issue] Blue screen. Nothing happening.
* [5 People have this issue] 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.
* [3 People have this question/issue] There is a stripe in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
*** 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)
* [2 People have this question/issue] There is a stamp HD3 in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
* [2 People have this question/issue] 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 People have this question/issue] 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?
* [1 Person has this question/issue] 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

== Badge Firmware Development related Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up?
* [5 People have this issue] The badge is not detect on my mac when I connect it by side port:
** => Install this driver: https://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html
*** Make sure to carefully follow the instructions, a 3rd party kernel extension is needed and restart might be needed as well.
*** '''Don't''' use brew, it has been reported not to work.
* [1 People have this question/issue] 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.
* [1 Person has this issue] 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

==BadgeHub related Questions/Issues==
* [0 People have this question/issue] Add your question/issue here or increase the number.

Badge Issues

2025-08-11T09:28:49Z

Halbrot:

== Please edit this page ==

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

== Badge Hardware Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [3 People have this question/issue] screen is not turning on at all.
* [1 People have this question/issue] Can not turn off badge while charging.
* [1] How do I reset the badge on battery?
** => Applying usb power will reset the badge
* [1 People have this question/issue] The antenna isn't connected yet. Can I use the device without damaging anything?
* [2 People have this question/issue] 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?
* [1] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it?
* [2 People have this question/issue] The badge suddenly stopped working. (possibly coincides with first time plugging in USB-C and charging my own protected cells). Removing Batteries did not help. Re-Flashing with newest firmware did not help.
Trace of boot-loop:
<pre>
./idf.py monitor

Order 8, (256) 1 blocks (256 pages)
Order 9, 0 blocks (0 pages)
Waste: 0 blocks (0 pages)
Total free pages: (calculated) 510 (stored) 510 max_order_free: 8
W (1078) ldo: The voltage value 0 is out of the recommended range [500, 2700]
E (1098) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (1098) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
HINT: Please verify if there is an SD card inserted into the SD slot. Then, try rebooting the board.
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
--- (inlined by) vPortExitCriticalMultiCore at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/portable/riscv/port.c:550
--- 0x4ff120a8: xTaskGenericNotify at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/tasks.c:5977
S0/FP : 0x00000000 S1 : 0x00000000 A0 : 0x0000002b A1 : 0x00000000
A2 : 0x00000004 A3 : 0x00000000 A4 : 0x20800008 A5 : 0x00000000
A6 : 0x00000003 A7 : 0x4000bf2a S2 : 0x00000000 S3 : 0x00000000 --- 0x4000bf2a: usb_serial_jtag_write at /home/bernhard/source/esp-idf_why2025/components/esp_driver_usb_serial_jtag/src/usb_serial_jtag_vfs.c:184
S4 : 0x00000000 S5 : 0x00000000 S6 : 0x00000000 S7 : 0x00000000
S8 : 0x00000000 S9 : 0x00000000 S10 : 0x00000000 S11 : 0x00000000
T3 : 0x4ff24aef T4 : 0x00000001 T5 : 0x00000000 T6 : 0x00000001
MSTATUS : 0x00011880 MTVEC : 0x4ff00003 MCAUSE : 0x00000001 MTVAL : 0x00000000
--- 0x00011880: SDLgfx_rotateSurface at :?
--- 0x4ff00003: _vector_table at ??:?
MHARTID : 0x00000001
</pre>

== Badge User Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3.
* [3 People have this question/issue] 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)
* [7 People have this question/issue] Blue screen. Nothing happening.
* [5 People have this issue] 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.
* [3 People have this question/issue] There is a stripe in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
*** 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)
* [2 People have this question/issue] There is a stamp HD3 in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
* [2 People have this question/issue] 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 People have this question/issue] 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?
* [1 Person has this question/issue] 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

== Badge Firmware Development related Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up?
* [5 People have this issue] The badge is not detect on my mac when I connect it by side port:
** => Install this driver: https://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html
*** Make sure to carefully follow the instructions, a 3rd party kernel extension is needed and restart might be needed as well.
*** '''Don't''' use brew, it has been reported not to work.
* [1 People have this question/issue] 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.
* [1 Person has this issue] 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

==BadgeHub related Questions/Issues==
* [0 People have this question/issue] Add your question/issue here or increase the number.

Badge Issues

2025-08-11T09:27:43Z

Halbrot: /* Badge Hardware Questions/Issues */

== Please edit this page ==

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

== Badge Hardware Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [2 People have this question/issue] screen is not turning on at all.
* [1 People have this question/issue] Can not turn off badge while charging.
* [1] How do I reset the badge on battery?
** => Applying usb power will reset the badge
* [1 People have this question/issue] The antenna isn't connected yet. Can I use the device without damaging anything?
* [2 People have this question/issue] 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?
* [1] One battery holder has a big blob of epoxy where it should contact the battery. Is there a good way to remove it?
* [2 People have this question/issue] The badge suddenly stopped working. (possibly coincides with first time plugging in USB-C and charging my own protected cells). Removing Batteries did not help. Re-Flashing with newest firmware did not help.
Trace of boot-loop:
<pre>
./idf.py monitor

Order 8, (256) 1 blocks (256 pages)
Order 9, 0 blocks (0 pages)
Waste: 0 blocks (0 pages)
Total free pages: (calculated) 510 (stored) 510 max_order_free: 8
W (1078) ldo: The voltage value 0 is out of the recommended range [500, 2700]
E (1098) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
HINT: Please reboot the board and then try again
E (1098) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
HINT: Please verify if there is an SD card inserted into the SD slot. Then, try rebooting the board.
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
--- (inlined by) vPortExitCriticalMultiCore at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/portable/riscv/port.c:550
--- 0x4ff120a8: xTaskGenericNotify at /home/bernhard/source/why2025-badge-firmware/components/freertos/FreeRTOS-Kernel/tasks.c:5977
S0/FP : 0x00000000 S1 : 0x00000000 A0 : 0x0000002b A1 : 0x00000000
A2 : 0x00000004 A3 : 0x00000000 A4 : 0x20800008 A5 : 0x00000000
A6 : 0x00000003 A7 : 0x4000bf2a S2 : 0x00000000 S3 : 0x00000000 --- 0x4000bf2a: usb_serial_jtag_write at /home/bernhard/source/esp-idf_why2025/components/esp_driver_usb_serial_jtag/src/usb_serial_jtag_vfs.c:184
S4 : 0x00000000 S5 : 0x00000000 S6 : 0x00000000 S7 : 0x00000000
S8 : 0x00000000 S9 : 0x00000000 S10 : 0x00000000 S11 : 0x00000000
T3 : 0x4ff24aef T4 : 0x00000001 T5 : 0x00000000 T6 : 0x00000001
MSTATUS : 0x00011880 MTVEC : 0x4ff00003 MCAUSE : 0x00000001 MTVAL : 0x00000000
--- 0x00011880: SDLgfx_rotateSurface at :?
--- 0x4ff00003: _vector_table at ??:?
MHARTID : 0x00000001
</pre>

== Badge User Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Inside program “c64emu” v1 trying Shift+{number} prints the number to console and not the symbol. This behaviour works in “crackme” v3.
* [3 People have this question/issue] 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)
* [7 People have this question/issue] Blue screen. Nothing happening.
* [5 People have this issue] 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.
* [3 People have this question/issue] There is a stripe in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
*** 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)
* [2 People have this question/issue] There is a stamp HD3 in my screen.
** There is a protective cellophane sheet attached to the screen for protection against scratches and dirt. Remove the cellophane sheet by peeling it off. Start in the lower right corner. There should be some sticky tape area of 8x8mm you can use to start peeling it off.
* [2 People have this question/issue] 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 People have this question/issue] 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?
* [1 Person has this question/issue] 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

== Badge Firmware Development related Questions/Issues ==
* [0 People have this question/issue] Add your question/issue here or increase the number.
* [1 Person has this question/issue] Flashing takes forever (>40 seconds) for a trivial application. Can I speed this up?
* [5 People have this issue] The badge is not detect on my mac when I connect it by side port:
** => Install this driver: https://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html
*** Make sure to carefully follow the instructions, a 3rd party kernel extension is needed and restart might be needed as well.
*** '''Don't''' use brew, it has been reported not to work.
* [1 People have this question/issue] 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.
* [1 Person has this issue] 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

==BadgeHub related Questions/Issues==
* [0 People have this question/issue] Add your question/issue here or increase the number.

User:Halbrot

2025-01-27T15:23:25Z

Halbrot:

{{UserInfo
|Bringing=Dei Mudder sei Sogge
|Village=Village:ZTL
|Languages=EN
|NickName={{PAGENAME}}
}}
cook
eat
sleep
nerd
repeat

User:Halbrot

2025-01-27T15:22:04Z

Halbrot:

{{UserInfo
|Village=Village:ZTL
|Languages=EN
|NickName={{PAGENAME}}
}}

User:Halbrot

2025-01-27T15:17:23Z

Halbrot: create user page

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