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

Clock Speed Change - Possible Issues #21

Open
cescalemodels opened this issue Apr 12, 2017 · 1 comment
Open

Clock Speed Change - Possible Issues #21

cescalemodels opened this issue Apr 12, 2017 · 1 comment

Comments

@cescalemodels
Copy link

cescalemodels commented Apr 12, 2017

For the DCC++ Raspberry Pi HAT I'm developing I opted to use an ATmega328P clocked at 8MHz because I wouldn't have to use any level shifters.

I forked the repository and made the required changes to the timer setups and board definitions for the new clock speeds, but my question is this: with half the amount of time to execute all of the required commands of the original software, will it still be able to keep up with all of the commands, or will it get bogged down into endless ISR's, leaving no time at all for the code to run?

If I won't be able to make the code work with the slower speed, then I will modify my design. I'm considering the possibility of overclocking as well, but it would be so much nicer if the code would just work as is.

Thanks!

@VassilyDev
Copy link

Do you have tested it? It might be useful for me too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants