Posted on October 04, 2016 at 22:24Agreed, but my point more generally is that the core STM32 IC/SW Engineers are not going to participate mano-a-mano here. In my observations the FAE's don't participate here either, but they are known to lurk.
Farnell presumably has their own FAEs, and ST has FAEs assigned to distributors and customers.
On forum's everyone has a problem, and there are a lot of those that can't even formulate a technical presentation of their problem but insist it is some kind of silicon bug. There may be an issue here, multiple similar report helps that case. A robust and repeatable demonstration would make a better one. ST has indicated they are looking into it, so assume they are, expect it might take a few weeks to propagate and advanced to the people with skill and design involvement to validate and address it.
If code works on a debugger but not without, I wouldn't start by looking at component issues, and I wouldn't assume the debugger is non-invasive. I'd start with code assumptions and initial conditions and work inward from there.
