2009-10-25 12:31, Øyvind Harboe skrev: > You make excellent general points in your post and I agree > to what you are saying, however here I'm discussing mrc/mcr > specifically and how to proceed with that one. > > Did you read up on mrc/mcr in targets and consider > the current patches& changes in detail? > > If you still disagree with my piecemail approach after having read > up on the mcr/mrc details, then I'll be happy to go along with > whatever you propose from a general git/patch/branch > development point of view on the mcr/mrc case. > > If I have to commit to doing *all* the work before I start > any mrc/mcr work at all, then I'm loathe to start at all and > I'd rather just revert the changes I've done so far. > > Again, this was just a next natural step after having done > the memory physical read/write work... > >
Some comments: I prefer read_cp/write_cp to mrc/mcr, since we really want to read/write to the coprocessor registers. The fact that this is implemented using the mrc/mcr instructions is not important here. There are no other arm instructions treated like that, rather we specifiy the registers, memory etc. that we want to access. It is definitely possible that there might be a future coprocessor access debug component that accesses coprocessors using a coresight memory mapped interface. This is pure speculation but is intended to show why read_cp/write_cp better reflects the intended function of this interface. The natural place for this would IHMO be armv4_5, this will include Armv7A targets but not Armv7M targets. Best regards, Magnus _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
