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

[BUG] Adafruit BLE 32u4: OUT_AUTO not applied by default, KC_RESET not putting MCU in DFU mode. #2229

Closed
harshitgoel96 opened this issue Jan 5, 2018 · 6 comments

Comments

@harshitgoel96
Copy link
Contributor

harshitgoel96 commented Jan 5, 2018

Hi
I am using Adafruit Bluefruit 32u4 on my board, with code setup provided in MF68_BLE.

  1. When I connect the bluetooth and USB on first boot, the board is outputting on both USB and BT at the same time. This results in double character input from the board.I have added keycode to add OUT_AUTO on my keymap. Once this is pressed, this issue is resolved, and i am able to switch between BT and USB seamlessly. I initially reported this issue in defect Adafruit Feather 32U4 LE, sending signal over Bluetooth and USB simultaneously #2223, but it was more of a query.
  2. KC_RESET keycode is not putting the MCU in DFU mode, it only restarts the board.
@harshitgoel96 harshitgoel96 changed the title [BUG] Adafruit BLE 32u4 OUT_AUTO not applied by default [BUG] Adafruit BLE 32u4: OUT_AUTO not applied by default, KC_RESET not putting MCU in DFU mode. Jan 5, 2018
@colemarkham
Copy link
Contributor

I know that KC_RESET worked last time I tested it. You have to #define CATERINA_BOOTLOADER like on the pro micro, but even that isn't working now. Something must have changed between Sept/Oct and now. I'm currently not getting anything to work on my Feather BLE 32u4 with code that worked a few months ago. I do remember something about needing an older firmware version for the RF module, so I'm looking for that right now.

@harshitgoel96
Copy link
Contributor Author

@colemarkham thanks for looking into this. I can confirm that I am using the latest firmware that was available in Aug 2017. I completed the build in December and that is when I noticed the issue.

I have not tried using #define CATERINA_BOOTLOADER option. i will try to this today and let you know if this changes anything.

@drashna
Copy link
Member

drashna commented Mar 25, 2018

There was a big update to the bootloader code and make process.

Try updating QMK and see if that helps.

Also, CATERINA won't help unless you're using the caterina bootloader (such as the pro micro). If you're using DFU, then ... "nothing will happen" basically.

@harshitgoel96
Copy link
Contributor Author

@drashna first of all, thanks a lot for trying to help me with my so many queries.

As per few different post, it looks like CATERINA is the default bootloader on Feather 32u4, thought i am not sure.
I have not been able to test it yet.

@drashna
Copy link
Member

drashna commented Mar 26, 2018

Welcome. I've recently been promoted to a collaborator, so I went through the entire backlog of issues (no small task, let me tell you!).

For the Feather 32U4, if it's this:
https://learn.adafruit.com/adafruit-feather-32u4-bluefruit-le/overview

It does require a double-tap to enter bootloader, which is a distinctly CATERINA thing, IIRC.
And the newer bootloader options, you want to set the "BOOTLOADER" to caterina, as per: https://docs.qmk.fm/config_options.html#avr-mcu-options

This way, it picks up the caterina specific code, and does proper detection of file size.

@harshitgoel96
Copy link
Contributor Author

So i have tested the Bootloader option and now I can enter the DFU mode without any issues.
Closing the defect, will open a PR soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants