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

need definition of error messages #85

Open
steeley opened this issue Oct 16, 2021 · 3 comments
Open

need definition of error messages #85

steeley opened this issue Oct 16, 2021 · 3 comments

Comments

@steeley
Copy link

steeley commented Oct 16, 2021

I'm using this library with a 4351b, 27Mhz Xtal and it seems to work well.

However I would like to see what LOS and REVID actually mean. in my case they always show 1
'indicating some kind of error"?? as show below. but my device seems to be working....

PLLA: 800000000 PLLB: 800000000 SYS_INIT: 0 LOL_A: 0 LOL_B: 0 LOS: 1 REVID: 1

Thanks

@evg2
Copy link

evg2 commented Jun 22, 2023

I have same issue with Si5351, 25MHz and work well.
I do not know what mean SYS_INIT: 0 LOL_A: 0 LOL_B: 0 LOS: 1 REVID: 1.
I know that must be SYS_INIT: 0 LOL_A: 0 LOL_B: 0 LOS: 0 REVID: 3.

Thanks

@tcarney57
Copy link

LOL means "loss of lock" (of the PLL), and LOS means "loss of signal" of the crystal or external clock. There's a few registers for these per generated clock. One set is "sticky" (meaning they have to be deliberately cleared), and the other is transient. These can be read from the device and used as desired. The library example sketch <si5351_example.ino> shows their use. In this case, just to confirm the device is working properly.

For detailed information on these and other registers, see Silicon Labs/Skyworks "AN619: Manually Generating an Si5351 Register Map."

@evg2
Copy link

evg2 commented Jun 22, 2023

What is REVID doing. Why changes from 1 to 3 if status is normal?

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

3 participants