- Tue Jan 18, 2022 10:03 am
#230825
The Ambiq website indicates that there is a new version of the Apollo3 Blue data sheet. Sadly, you now have to fill out a form to download it. Even more sadly, when I fill out the form the site won't let me click on 'submit'.
Has anyone been able to download it?
There is also a new SDK version. I have not checked that out yet - I'll have to get psyched up to do that.
Finally, there is a new errata document (V3.0), which is directly downloadable. The big change I see is that the I2S functionality appears to be so completely broken that Ambiq now says "just don't use it". Fortunately, I don't need I2S.
The other interesting errata (for me) is that they have elevated the fact that the timer can double-count to an official errata now instead of just being mentioned in passing in a support article on their website. What they still don't mention is that the XTAL glitches they refer to can be randomly caused by simply reading any of the S/CTIMERs current value registers. In addition, it is left as an exercise for the user to figure out that the double-count in the STIMER current value means that STIMER has been silently and permanently corrupted. This has major consequences if you are trying to use the STIMER to accurately track the passage of time, as documented here viewtopic.php?f=170&t=55246.
Has anyone been able to download it?
There is also a new SDK version. I have not checked that out yet - I'll have to get psyched up to do that.
Finally, there is a new errata document (V3.0), which is directly downloadable. The big change I see is that the I2S functionality appears to be so completely broken that Ambiq now says "just don't use it". Fortunately, I don't need I2S.
The other interesting errata (for me) is that they have elevated the fact that the timer can double-count to an official errata now instead of just being mentioned in passing in a support article on their website. What they still don't mention is that the XTAL glitches they refer to can be randomly caused by simply reading any of the S/CTIMERs current value registers. In addition, it is left as an exercise for the user to figure out that the double-count in the STIMER current value means that STIMER has been silently and permanently corrupted. This has major consequences if you are trying to use the STIMER to accurately track the passage of time, as documented here viewtopic.php?f=170&t=55246.