Sent from the wrong address the first time...
Den 4 maj 2014 08:09 skrev "Paul Fertser" <[email protected]>:
>
>
> Hardware (FPB) breakpoints work everywhere but there're few of them, I
> understand. So you say you'd like to be able to tell exactly when you
> can place a software breakpoint and when you have to resort to FPB,
> and for that you're proposing to introduce additional config file
> command to specify all the RAM sections (actually not all but only
> those that we can directly modify via DAP), do I understand it right?
>
> So how about this simple solution: if the address is in target
> working-area, use sw breakpoint, otherwise hw? I understand that's not
> exactly what you want but is it a good enough approximation? BTW, most
> OpenOCD upstream configs for microcontrollers specify the whole SRAM
> region as working area.
>
Well, actually I think that it's common to put the minimum sram size for
the family in the config file. Look at the stm32 configs for example.
The flash needs to probed before connecting gdb, to provide the memory map.
I don't know if it is a good idea but one might attempt a sw breakpoint
first and if the write fails, try a hw breakpoint.
/Andreas
------------------------------------------------------------------------------
"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
