Mads,
Here I am not talking about merits/demerits of using libraries for normal firmware, but about producing a minimal, easily and surely reproducible example exhibiting he problem, for purposes of problem analysis.
But whatever; the key point is in providing a minimal but complete compilable example exhibiting the problem, together with concise description of used hardware (e.g. VDDA voltages may matter very much in this case). With libraries or without them. Even better in this case would be *both* source and binary.
> first step is for ST to acknowledge that there is a problem
Witnessed by Amel's posts above, they did acknowledge that, and performed an experiment at their side, concluding that there is no problem.
However, we don't know, what experiment did they perform, under what circumstances, etc. Would they publish a reproducible example code as I've wrote above, together with what was the hardware used - unfortunately in this case a standard Nucleo is not an option - you and Tomas could then try to reproduce that code at their side, and would that result in working case, you/he could then investigate and try to find differences between working and non-working cases. And the same applies to you and Tomas, would you/he provide that minimal but complete code/binary, then you could mutually verify your findings and potentially come to some conclusions.
That's because the details usually do matter.
JW
[EDIT]
> Main coincidence is the matching date and revision code
Any photo?
