-
Notifications
You must be signed in to change notification settings - Fork 870
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
Feature Request: using another timer but 0 for "time-driver" #3766
Comments
As a first step I tried to use timer 1 instead of timer 0. |
edit:
(don't know if that is the correct way. ) |
edit:
but I of course should use the clk_ref_freq defined in |
Once done, I may be able contribute an update to time-driver.rs that adheres to a feature defining which timer to use, |
proceeding, I did find |
I started a project using an RP2350 chip based on embassy-rp.
I found that when specifying the
embassy-rp
feature"time-driver"
my tests work just fine. Here embassy usesTIMER0
(as defined inrp235x/mod.rs
.Now the RP2350 features multiple timers. In fact I would like to use the "Always on" Timer for this battery powered project.
Feature request : It would be great if in the features a timer hardware could be selected.
For now I dropped the re-used the feature
"time-driver"
and created my own driver essentially by copying the code from embassy-rp/time_driver_rs. That works fine. Now researching on how to make it use TIMER1 and then the "Always On" timer.Thanks for listening !
BTW.: Seemingly the AON Timer (denoted as
TIMER
in the RP2350 documentation seems not top be included inrp235x/mod.rs
. ?!? (butPOWMAN_IRQ_TIMER
= 45 already is defined.) Supposedly the definitions in powman.rs should be used here. but how to decently usepac::POWMAN::inte(
) or similar for the AON Timer ?The text was updated successfully, but these errors were encountered: