LilyGo T-Impulse Wristband, Dragino LGT92 tracker and AI RHF76-052 support #198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since commit bdd33df (Refresh USB logic; callback for events; hotplug in STOP mode; STOP mode in USB SUSPEND; bunch of race conditions in the USB/CDC code; avoid SOF interrupt; 500mA max power in descriptiors), the USBD code would assume a VBUS pin is available and only initialize the USB stack when a VBUS voltage is present. This commit restores the older behavior of, when `STM32L0_CONFIG_PIN_VBUS` (so indirectly also `usbd_pin_vbus`) is `STM32L0_GPIO_PIN_NONE`, assuming VBUS is always present. USB initialization can still be controlled using `USBDevice.attach()`.
This is already done by usbd_conf.c which is also the place where it is read, so no need to do it again here.
This can be useful to allow measuring the actual USB voltage, rather than just detect presence. Previously the USB code would always enable an internal pulldown on the VBUS, which would skew the reading (and, if the divider is fairly high impedance, can even prevent detecting VBUS presence using a digital read). With this commit, boards can indicate they use an external divider using the STM32L0_CONFIG_PIN_VBUS_HAS_DIVIDER macro in their variant.h. When this is defined, the internal pullup is not enabled to prevent it from causing issues and because it is no longer needed (the external divider functions as a pulldown).
It turns out that stopping the USB peripheral does not automatically reset this pullup, so stopping USB (e.g. through USBDevice.detach()) would let the pullup enabled, making the USB host think the board was still connected (but any subsequent communication would fail). Additionally, this would use around 300μA of current. This is a bug in the USB HAL used. This commit backports a small change from the HAL v1.11.3 to fix this. This fixes GrumpyOldPizza#171
Vbus support
Disable USB pullup when stopping USB
|
@GrumpyOldPizza any chance to have this merged? Thanks! |
No VBUS detection support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just in case somebody else may be interested. T-Impulse WB has no VUSB so SerialUSB does not work. Even with PR#175.