[Bug] AUDIO_CLICKY tuneables cause random lockups on Preonic

[era1112]

Describe the Bug

• After tuning parameters for the faux-clicky mode, using the instructions in /docs/feature_audio.md, Preonic locks up and becomes unresponsive after a short period of use.
• Keyboard becomes completely non-responsive, but RGB LEDs do stay on.
• Lockup happens randomly 30 seconds to 3 min after startup, although typing fast sometimes brings it on immediately.
• Unplugging and replugging the keyboard clears the lockup.

Code details (all in config.h):

Enabling clicky mode on it's own (ie, with default parameters) is stable.

#define AUDIO_CLICKY            

Problem presents when making reasonable adjustments to the parameters that the guide says are tuneable. This is one example of settings that cause the lockups:

// Clicky mode parameter deviations
#define AUDIO_CLICKY_FREQ_MIN       65.0f       // Default 65
#define AUDIO_CLICKY_FREQ_DEFAULT   800.0f      // Default 440
#define AUDIO_CLICKY_FREQ_MAX       1500.0f     // Default 1500
#define AUDIO_CLICKY_FREQ_FACTOR    1.18921f    // Default 1.18921
#define AUDIO_CLICKY_FREQ_RANDOMNESS    1.0f        // Default 0.05, guide suggests 1.0 for an interesting effect
#define AUDIO_CLICKY_DELAY_DURATION     1           // Default 1

You can inspect my code on my dev_branch. There are a lot of other features enabled in that keymap, but the problem is the same if I start with the default firmware and only add clicky mode.

Possible steps to remediate

• Add a note in the documentation in /docs/feature_audio.md. Specifically, add a warning to the table of options that making deviations can lead to keyboard lockups.
• Someone with deeper knowledge of QMK than me could investigate what these settings are doing behind the scenes that puts the keyboard into a lockup.

System Information

• Keyboard: OLKB Preonic
  • Revision (if applicable): rev3_drop
• Operating system: win10, win11 (many different computers)
• AVR GCC version: 8.4.0
• ARM GCC version: 10.1.0
• QMK Firmware version: 0.15.17
• Any keyboard related software installed? No

[drashna]

Is a known issue: https://github.com/qmk/qmk_firmware/issues/12080

Try setting the driver to dac_additive, as that seems to work bet for me.

[stale[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[github-actions[bot]]

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know. // [stale-action-closed]