You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Avoid pulling ztimer and ztimer_msec dependencies by default when using usbdev_fs peripheral driver.
If another module needs ztimer, then we can keep using it but otherwise use busy_wait() to perform the small delay needed by the driver.
My main idea is to avoid pulling ztimer when it is possible, to save ROM for riotboot_dfu bootloader application.
Testing procedure
make BOARD=bluepill-stm32f103c8 -C tests/sys/usbus_cdc_acm_stdio must compile (and ztimer should not appear if you use info-build)
make BOARD=bluepill-stm32f103c8 -C tests/sys/usbus_cdc_ecm must compile (and ztimer should appear if you use info-build because ztimer dependency is pulled by another module
That's weird, I just compile make BOARD=bluepill-stm32f103c8 -C tests/sys/usbus_cdc_ecm from master and from this PR. Both compile flawlessly.
May I ask you your output of dist/tools/ci/print_toolchain_versions.sh ?
@Teufelchen1 It seems you're hitting a toolchain issue w/ Ubuntu default one.
I can reproduce it with an Ubuntu 20.4.6 with Ubuntu default toolchain. But I have no issue using a standalone toolchain from ARM. I guess Ubuntu default toolchain is using newlib instead of newlib-nano...
But anyways, this is not related to this PR. If you want to test this PR, I suggest you to try a standalone toolchain from ARM or to switch to picolibc (if it's installed on your system) by using FEATURES_PROVIDED=picolibc
Thanks for checking up!
I already saw the expected behavior in the build log, even though the build failed. Since it's clear the failure is unrelated and murdock is happy, we can move this forward :)
This file contains hidden or 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
Area: cpuArea: CPU/MCU portsCI: ready for buildIf set, CI server will compile all applications for all available boards for the labeled PRPlatform: ARMPlatform: This PR/issue effects ARM-based platforms
5 participants
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.
Contribution description
Avoid pulling
ztimerandztimer_msecdependencies by default when usingusbdev_fsperipheral driver.If another module needs
ztimer, then we can keep using it but otherwise usebusy_wait()to perform the small delay needed by the driver.My main idea is to avoid pulling
ztimerwhen it is possible, to save ROM forriotboot_dfubootloader application.Testing procedure
make BOARD=bluepill-stm32f103c8 -C tests/sys/usbus_cdc_acm_stdiomust compile (andztimershould not appear if you useinfo-build)make BOARD=bluepill-stm32f103c8 -C tests/sys/usbus_cdc_ecmmust compile (andztimershould appear if you useinfo-buildbecauseztimerdependency is pulled by another moduleIssues/PRs references
None.