There are a number of wrong assumptions in the CortexM3 code that I am 
proposing to fix.
This is one of them - there are others - I’m keeping them in separate emails so 
that they can be discussed separately.

Corex_m.c - line 59 - Assumes that any address < 0x20000000  => Flash memory 
and is hardware breakpoint

That is not always the case
        Proposal:  Create (N=4) ranges address ranges where the breakpoint type 
can be defined by config file.
        The default would be - 1 range,  from 0..0x20000000 - of type hardware 
breakpoint

I do not propose to allocate this space, command:

        $_TARGET  cortex_m  bkptregion clear            <= sets all breakpoints 
to SW breakpoints
        $_TARGET  cortex_m  bkptregion list              <= presents table of 
regions
        $_TARGET  cortex_m  bkptregion set  TYPE  NUMBER START  LENGTH

The set command sets region (x) to something as specified.

Where:   
        TYPE = soft | hard
        NUMBER = 0..3
        START = start address
        LENGTH = memory length

Note:
        Conflicting/overlapping regions are just too bad 
        The first one that matches wins

ok with that?
------------------------------------------------------------------------------
"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