[GH-ISSUE #192] Option -DOPK_LOG=1 makes OpenPuck disconnect/reconnect frequently #82

Open
opened 2026-10-22 05:03:07 +00:00 by roman · 0 comments
Owner

Originally created by @Bambusbro on GitHub (Jul 26, 2026).
Original GitHub issue: https://github.com/safijari/openpuck/issues/192

Description

Compiling OpenPuck with -DOPK_LOG=1 using arduino-cli results in repeated crashes/reboots during operation.

Environment

  • Board / FQBN: adafruit:nrf52:feather52840 / NRF52840 Pro Micro
  • Build Command: arduino-cli compile -b adafruit:nrf52:feather52840 --build-property "build.extra_flags=-DNRF52840_XXAA {build.flags.usb} -DCFG_TUD_HID=6 -DCFG_TUD_TASK_QUEUE_SZ=512 -DCFG_TUD_VENDOR_TX_BUFSIZE=256 -DOPK_LOG=1" OpenPuck" .

Memory Usage at Compile Time

The compiler output shows sufficient RAM available:

  • Flash: 189776 / 815104 bytes (23%)
  • SRAM: 140864 / 237568 bytes (59%)
  • Remaining for local variables: 96704 bytes

Behavior

When flashed with -DOPK_LOG=1, the OpenPuck crashes in constant reboot loop as soon as connected via USB
Without -DOPK_LOG=1, the firmware runs completely stable.

Expected Behavior

The device should boot and operate normally with diagnostic logging / capture ring enabled.

Originally created by @Bambusbro on GitHub (Jul 26, 2026). Original GitHub issue: https://github.com/safijari/openpuck/issues/192 ### Description Compiling OpenPuck with `-DOPK_LOG=1` using `arduino-cli` results in repeated crashes/reboots during operation. ### Environment - **Board / FQBN:** adafruit:nrf52:feather52840 / NRF52840 Pro Micro - **Build Command:** `arduino-cli compile -b adafruit:nrf52:feather52840 --build-property "build.extra_flags=-DNRF52840_XXAA {build.flags.usb} -DCFG_TUD_HID=6 -DCFG_TUD_TASK_QUEUE_SZ=512 -DCFG_TUD_VENDOR_TX_BUFSIZE=256 -DOPK_LOG=1" OpenPuck" .` ### Memory Usage at Compile Time The compiler output shows sufficient RAM available: - **Flash:** 189776 / 815104 bytes (23%) - **SRAM:** 140864 / 237568 bytes (59%) - **Remaining for local variables:** 96704 bytes ### Behavior When flashed with `-DOPK_LOG=1`, the OpenPuck crashes in constant reboot loop as soon as connected via USB Without `-DOPK_LOG=1`, the firmware runs completely stable. ### Expected Behavior The device should boot and operate normally with diagnostic logging / capture ring enabled.
Sign in to join this conversation.
No labels
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
safijari/openpuck#82
No description provided.