-
Notifications
You must be signed in to change notification settings - Fork 3k
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
AnalogOut does not work for K64F #3999
Comments
@BlackstoneEngineering @senthilr @sg- |
We don't have example apps in OOB to catch these issues. |
+1 |
@0xc0170 Is this a bug related to the NXP port? Description states this was working before. |
@mmahadevan108 I believe so. |
@MarceloSalazar In the medium to long term we should have the shield on the CI Infrstructure. In the short term we should do this as part of OOB on the relevant platforms as we do not yet have it integrated onto the CI farm. |
@mmahadevan108 - DAC output is not enabled in source code. If I un-comment the below line in
Since the comment says it should be enabled when data is set, can you please fix it at write place and enable DAC. |
@deepikabhavnani Thank you. I have submitted a PR to fix this issue. |
Fixes Issue ARMmbed#3999 Signed-off-by: Mahadevan Mahesh <[email protected]>
Fixes Issue #3999 Signed-off-by: Mahadevan Mahesh <[email protected]>
Description
AnalogOut does not work for the K64F from mbed-os version 5.2.3 to 5.4.1.
mbed-os version 5.2.2 has a working AnalogOut api.
AnalogOut constructor works, and no errors occur during runtime. But regardless of what value gets set to the AnalogOut pin, the value floats at 0.03V.
Example code
Image below shows no output waveform:

Bug
Target
K64F
Toolchain:
GCC_ARM
Toolchain version:
gcc version 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
mbed-cli version:
1.0.0
meed-os sha:
cc58a7f
The text was updated successfully, but these errors were encountered: