5 years, 4 months ago.

AnalogIn Problem in NUCLEO L433 and L432 (again)

Please excuse me that I'm still here with my AnalogIn Problem.

I've tried for some time now to fix it by myself but with no success.

Here is my first description of what happend: https://os.mbed.com/questions/83632/AnalogIn-First-declared-AnalogIn-not-wor/

TLDR: When using multiple AnalogIns (or just one) on these devices the first one used doesn't produce correct values. (In my first question I incorrectly assumed it was the first one declared) Connecting it to GND/3V3 results in values 0.45/0.96 while the other ones work correctly (0.000x/0.999x).

When compiled with the online compile my test-code works. But this is not an option in my workflow.

I'm using Platformio and mbed 5.10.1.

I would appreciate it very much if someone could give me a hint on what to do to fix this or how to find the cause myself.

Did you manage to find a fix for this?

posted by Nicolaus Starke 25 Feb 2019

1 Answer

5 years, 4 months ago.

Hi,

The mbed online compiler uses mbed-os 5.10.3 and the problem on AnalogIn has surely been corrected in this version.

I think the best would be to update the mbed version that is used in Platformio. Note that a new mbed-os version 5.11.0 is coming...