Can we think through use cases and debugging tools better?
Think like users, think about how to present diagnostic data that can convey useful information. Use the tools as if you were a User, test basic functionality and interaction so you KNOW it works properly.
Here trying to understand interactions with an External Loader in STM32 Cube Programmer.
I'm fine with one line of information, but put some actual information in that line, ie for a Read the Address and Size would be a MINIMUM.
I'd use Level 3, but the method used for the Logging Window CHOKES when doing a million SMALL reads on a 32MB SPI device when verifying. What controls the size, the H7 has loads of RAM it uses on Writes?
Sorry if I sound frustrated, but I've tried to use these tools for years, they aren't getting markedly better and seem to lack any Quality Assurance or any desire to address basic issues over the span of multiple years.
@brk

