On May 3, 2014, at 8:42 AM, Paul Fertser <[email protected]> wrote:

> On Sat, May 03, 2014 at 07:03:18AM -0700, Duane Ellis wrote:
>> 
>> On May 3, 2014, at 12:20 AM, Paul Fertser <[email protected]> wrote:
>>> 
>>>> Could write a new function - something like:    
>>>> flash_IsThisAddressInFlash(  target_pointer,   ADDRESS )  this would *NOT* 
>>>> probe anything
>>>> Do you see a problem with assuming the “flash address range” is always 
>>>> valid if not auto-probed?
>>> 
>>> Yes, many flash drivers populate it only during probe time. But,
>>> again, I do not see any issues with requiring auto-probing there.
>> 
>> 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?

*NO* - not always, but YES sometimes

The example would be to “connect” and see where the program counter is,  or 
maybe there is a RAM log buffer (think ascii text ring buffer) after inspecting 
and modifying I might want to click GO.

> You wouldn't try to set a breakpoint on a dead/crashed system, or would you?

*YES* - but that might happen later  (continuing the example above) maybe the 
PC stopped inside of memset(), I might need to step out a few times …. and 
single step may require breakpoints. But - maybe some of the system clocks are 
off and you cannot probe all locations.

It’s messy, very messy and ugly - there is no simple solution here.


> That's why
> I was thinking auto-probing flash as part of breakpoint setting is ok.
> 
> -- 
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:[email protected]

------------------------------------------------------------------------------
"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

Reply via email to