Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot enter DFU mode with whitefox's reset key #4895

Closed
kissu opened this issue Jan 20, 2019 · 3 comments
Closed

Cannot enter DFU mode with whitefox's reset key #4895

kissu opened this issue Jan 20, 2019 · 3 comments
Labels
bug core help wanted question stale Issues or pull requests that have become inactive without resolution.

Comments

@kissu
Copy link

kissu commented Jan 20, 2019

Hi ! ✋
I'm a bit new to QMK but after some research on wiki, I cannot find a way to make the RESET button work.
Compilation and flashing with physical button on the back are totally fine ofc, just not as convenient as a button press.

System Information

  • Keyboard: Whitefox 🦊
  • Operating System: Ubuntu 18.04
  • avr-gcc version: 5.4.0
  • arm gcc version: 6.3.1 20170620
  • QMK Firmware version: 0.6.212

Additional context

Since I'm not sure how to explain things better, I have a screen of the whole thing, if it can help somehow...
image

I found the AVR MCU options page, but I don't know what can I use there since, in my case, I do have a KIIBOHD_BOOTLOADER AFAIK (in my root whitefox directory).
For the reset, I tried the RESET keycode and that little snippet

void safe_reset(qk_tap_dance_state_t *state, void *user_data){
  if (state->count >= 3){ // Reset the keyboard if you tap the key more than three times
    reset_keyboard();
    reset_tap_dance(state);
  }
}

both produce the same result ofc.

@drashna
Copy link
Member

drashna commented Feb 8, 2019

Do you know when this started? Eg, when it was working?

Also, you can use dfu-util-wait as the target, to do the waiting part automatically.

@github-actions
Copy link

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 github-actions bot added the stale Issues or pull requests that have become inactive without resolution. label Jun 17, 2022
@tzarc
Copy link
Member

tzarc commented Jun 18, 2022

Closing due to inactivity.

@tzarc tzarc closed this as completed Jun 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug core help wanted question stale Issues or pull requests that have become inactive without resolution.
Projects
None yet
Development

No branches or pull requests

3 participants