> > I have just tried to change CONTROL[0] using reg 20 
> 0x1000000, it fails.
> > The cause is the array issue i mentioned earlier, this is 
> working in 
> > the previous code.
> > 
> > The read is done in the function 
> cortex_m3_load_core_reg_u32 and num 
> > will only ever be 20.
> > Before it would pass either 19, 20, 21 and 22 depending on 
> what byte 
> > you wanted to read.
> > 
> > I have attached a patch showing some unused code.
> 
> I don't know how I overlooked that.
> 
> I guess I'll have an update coming along in a while ...
> 
> 

I have been thinking about the changes to the cortex reg's.
And do not see any benefit, we were already getting the info from reg20 but
just putting it in 4 virtual regs.

All the user wants to see when running a reg cmd is the important cortex
regs, including primask, basemask etc.
They will have no idea what spec20 is, a search will yield no results.

as discussed we could add a tcl script to output primask etc, but are we not
back where we started?

Cheers
Spen
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to