On 03.05.2014 17:42, Paul Fertser wrote: > On Sat, May 03, 2014 at 07:03:18AM -0700, Duane Ellis wrote: >> I do - need to attach to a dead/crashed system without reset, aka: “a >> soft attach” - no reset. Because you need to figure out why things >> have crashed, various bus clocks may be disabled in parts of the >> chip, the debugger should not make things worse by probing hardware >> that is currently disabled due to a power down setting. Meaning: You >> might be debugging a power down/power up problem. > We're talking about setting breakpoints there, right? You wouldn't try > to set a breakpoint on a dead/crashed system, or would you? That's why > I was thinking auto-probing flash as part of breakpoint setting is ok. As an alternative, you might return an error when trying to set a breakpoint with un-probed memory areas.
Also, flash drivers might provide a default value without probing - in most cases, it should be possible to determine an upper bound of how much area the flash might take without probing the exact details - for the purpose of determining breakpoint type, this should be enough. cu Michael ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
