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

set_correction() Doesn't appear to work #7

Closed
pwarren opened this issue Mar 13, 2015 · 1 comment
Closed

set_correction() Doesn't appear to work #7

pwarren opened this issue Mar 13, 2015 · 1 comment

Comments

@pwarren
Copy link
Contributor

pwarren commented Mar 13, 2015

From the 'jason' branch, I run the calibration example, with a correction of 22, and my board output's 10MHz, to the limit of my counter (1Hz).

Then if I run, a simple sketch that sets the clock as per the calibration example, with no set_correction() call. get_correction() returns -1, and the output is 22 Hz above 10MHz

Am I doing it wrong, or not understanding how the set_correction() works? Should I do set_correction(22); with each sketch I write?

@NT7S
Copy link
Member

NT7S commented Apr 4, 2015

I believe that's probably a function of the EEPROM routines, which I have removed from the latest commit.

You should do a set_correction() for each sketch. I removed the EEPROM routines to make the code more portable, so that you can write your own calibration logic to read and set the cal constant into NV memory as appropriate for your device and use.

@NT7S NT7S closed this as completed Apr 4, 2015
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