-
Notifications
You must be signed in to change notification settings - Fork 89
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
MAX78000 - Inconsistency between User Guide and SDK #1040
Comments
Hi @alessandro-montanari, I will check with our hardware designers and internal tickets to see if there are any known issues with that bit. At the moment I would say continue to use our existing implementation that writes to the fields directly. This may be a workaround to some issue. I will let you know what I find |
@alessandro-montanari I know it has been some time on this issue... apologies for the delay. I have actually been in the process of transitioning out of ADI and am cleaning up some old tickets. I was not able to find any internal documentation on any known issues. I was also able to lightly test If you can attach any sample code/details for a program that can consistently brick the device on this bit that would be very helpful. |
Thanks for checking this @Jake-Carter. |
Hello,
I'm working on low power modes and wakeup on MAX78000 and I noticed that the user guide says to write 1 to the lpwkst_clr field on register
PWRSEQ_LPCN
to clear the wakeup status flags (PWRSEQ_LPWKST0
,PWRSEQ_LPWKST1
, ...).However, in the SDK (Libraries/PeriphDrivers/Source/LP/lp_ai85.c) the function (
MXC_LP_ClearWakeStatus()
) clears them by writing all 1s into the registers directly.I tried to modify the function with this line
MXC_PWRSEQ->lpcn |= MXC_F_PWRSEQ_LPCN_LPWKST_CLR;
but it seems to have bricked my device. I couldn't reset it or re-flash it. I had to remove power to it and then it came back.What is the best way to clear those registers?
Thanks
The text was updated successfully, but these errors were encountered: