You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding an AnalogIn object to mbed-os-example-mesh-minimal results in corrupted AnalogIn measurement values.
If the AnalogIn measurement is placed before mesh = MeshInterface::get_default_instance(); (or if that line is commented out), then the correct measurements are printed out.
Expected behavior (with get_default_instance() is commented out).
Full scale uint16 (0 to 65,536) measurements as expected.
61978
61986
61984
61994
Actual behavior (with get_default_instance() called before the measurement)
Results limited to 1 decimal digit. Sometimes in different situations the measurements are 2 or 3 digits consistently but they are always random instead of related to the actual analog value.
0
8
1
3
7
Target(s) affected by this defect ?
K64F
NUCLEO_F429ZI
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM
What version of Mbed-os are you using (tag or sha) ?
Mbed 5.15 (b114a9c)
Mbed OS 6.5 (f227856)
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
N/A
How is this defect reproduced ?
Plug in any analog sensor or voltage value (0-3.3V) to an analog input such as A1.
Add the following code to the mbed-os-example-mesh-minimal main.cpp.
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-3389
Description of defect
Adding an
AnalogIn
object tombed-os-example-mesh-minimal
results in corrupted AnalogIn measurement values.If the AnalogIn measurement is placed before
mesh = MeshInterface::get_default_instance();
(or if that line is commented out), then the correct measurements are printed out.Expected behavior (with get_default_instance() is commented out).
Full scale uint16 (0 to 65,536) measurements as expected.
Actual behavior (with get_default_instance() called before the measurement)
Results limited to 1 decimal digit. Sometimes in different situations the measurements are 2 or 3 digits consistently but they are always random instead of related to the actual analog value.
Target(s) affected by this defect ?
K64F
NUCLEO_F429ZI
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM
What version of Mbed-os are you using (tag or sha) ?
Mbed 5.15 (b114a9c)
Mbed OS 6.5 (f227856)
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
N/A
How is this defect reproduced ?
Plug in any analog sensor or voltage value (0-3.3V) to an analog input such as A1.
Add the following code to the
mbed-os-example-mesh-minimal
main.cpp.First commend out this part:
And then add this part:
Lastly, to recreate the problem, uncomment the section with get_default_instance().
The text was updated successfully, but these errors were encountered: