-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Lower power by using the Wait for Interrupt (WFI) instruction #2685
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
Conversation
@jepler Please take a look at this. I've only redone the nRF port so far and would like high level feedback before I do the others. The only remaining work for nRF is to get PulseIn working again which uses the monotonic clock for pulse timing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is going in a good direction. I didn't do a detailed review, but @tannewt let me know in the chat that he's just looking for high level review at this point.
I can take a closer look at this tomorrow morning, but it seems like good progress so far. |
Thanks @jepler and @hierophect for the high level review. I've gotta propagate the changes to other ports and just wanted to make sure I was heading the right direction. |
Thanks @dhalbert. sigh I may wait until next week to tackle M0 flakiness. I'm itching to work on ESP32-S2. Will see how I feel tomorrow. |
@tannewt Yes, this can wait :) |
@dhalbert I can't reproduce this flakiness with a Metro M0. Most of the time it works. Occasionally, I do see the boot hang very early but I think I can get the same behavior on master. I was testing it with an Arch Linux system and a Beagle sniffing the USB traffic. I've merged in latest master which is what I tested with. Please try again and let me know if it's consistently bad for you still. I may need your help debugging it. |
@tannewt It's still failing on Metro M0, somewhat more than half the time. I just press reset and see what happens. Attached is a Beagle trace from a failure. I will not work on it more this evening. |
I'm seeing a lot of assert errors in tinyusb with this patch when running on an nRF52833. For example:
|
Also, rename it so that matches the other board names.
Also, the ASSERT that gets hit is probably due to the tinyusb process not being called often enough, causing the host to send a USB RESET, which hits this bug: hathach/tinyusb#179 |
@xobs Would you mind PRing the '833 board defs? I have a dev kit I can try it on here. |
PR generated at #2828 Note that it requires a bootloader that's smaller (such as https://github.com/simmel-project/bootloader) in order to give more storage on the small internal flash. |
Enable pixelbuf in its place because we'll need it soon.
@dhalbert This is ready for another look and test. Thanks! |
Ok, @dhalbert. This commit should be a winner. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
USB fix works great for me!
@jepler Ok for me to merge? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like my earlier requested changes were resolved. No new testing or review performed.
congrats on the big lift! |
No description provided.