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

NeXT-USB: Wakeup problem on Mac and Remote Wakeup #753

Closed
tmk opened this issue Feb 26, 2023 · 1 comment
Closed

NeXT-USB: Wakeup problem on Mac and Remote Wakeup #753

tmk opened this issue Feb 26, 2023 · 1 comment

Comments

@tmk
Copy link
Owner

tmk commented Feb 26, 2023

Found that NeXT-USB has two problems on suspend/wakeup.

1. Wakeup problem on Mac

reported by some user. The converter stops working after wakeup on Mac.
On Windows 10 and Linux(Ubuntu 22.04.2 LTS) it has no problem.

I don't own Mac to test and could not look into.

without the build option below LUFA on atmega32u2 cannot provide suspend and wake event. This seems to lead wake problem on Mac.

Delay after RemoteWakeup on QMK

Also this 200ms delay would be interested if further wake/sleep issue still exists, but not tested by me.

https://github.com/spidey3/qmk_firmware/blob/cf51106cc61000b026c06e6162e5e671435d1bab/tmk_core/protocol/lufa/lufa.c#L1086-L1094

qmk/qmk_firmware#11450

2. Remote Wakeup

The converter cannot RemoteWakeup computer by pressing a key at least on Windows 10 and Linux(Ubuntu 22.04.2 LTS).

Not tested on Mac.

Cause

Makefile in next_usb define variable MCU like: MCU ?= atmega32u2 # TMK converter
in this case tmk_core/protocol/lufa.mk fails to define build option NO_LIMITED_CONTROLLER_CONNECT for LUFA.

This prevents RemoteWakeup on atmega32u2:
#361

tmk added a commit that referenced this issue Feb 27, 2023
the condition didn't work when variable MCU includes comment like:
    MCU ?= atmega32u2       # TMK converter
#753

This affects RemoteWakeup on atmega32u2:
#361
tmk added a commit that referenced this issue Feb 27, 2023
@tmk
Copy link
Owner Author

tmk commented Feb 27, 2023

Fixed 1. and 2. by the commit: b3d2f64

As for 1. problem seems to be cured but is not completely tested.

@tmk tmk closed this as completed Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant