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

SAMD51 clock system stalls in -O2 and above #52

Open
jnaulet opened this issue Jun 24, 2023 · 1 comment
Open

SAMD51 clock system stalls in -O2 and above #52

jnaulet opened this issue Jun 24, 2023 · 1 comment
Labels
architecture Structural change bug Something isn't working

Comments

@jnaulet
Copy link
Owner

jnaulet commented Jun 24, 2023

This is related to issue #19
We might have to implement some variant of activate wait, like delay_us() or delay_ms() for every arch & every clock speed.

This is not that obvious withotu a massive refactoring, unless maybe arch_counter() might be used differently (as a freerunnning counter, similar to MIPS and RISC-V).

@jnaulet jnaulet added enhancement New feature or request architecture Structural change bug Something isn't working and removed enhancement New feature or request labels Jun 24, 2023
@jnaulet
Copy link
Owner Author

jnaulet commented Jul 9, 2023

Here's a possible workaround: let the clock driver allow to wait for a certain number of cycles / ns.
This won't fix the sync between clock domains that occur on almost any sam related driver, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture Structural change bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant