I can now see that I left off a critical detail! :) Yes, you most certainly can use a TCL set command to accomplish this. The only issue is you have to spend an inordinate amount of time entering the values by hand. That in itself is another source for errors -- especially on processors with large configuration register sets.
Most processor manufacturers typically provide a standard C include file with their reference projects that have all the configuration registers and their relevant addresses pre-defined. What I was thinking was something that allows a person to capitalize off existing C header files directly in the form of a special TCL include statement. I am not too familiar with how the existing TCL parser works, so this idea may be impractical, however. Gary On 9/1/09 12:12 AM, "Magnus Lundin" <[email protected]> wrote: > >>> 3) One feature that I think may make sense to add at some point in the >>> future to the main software is support for label/value associations that >>> allow hexadecimal register values to be associated with more legible and >>> understandable names. Looking at "mww 0xffff3ec2 0x2" in a configuration >>> script is more likely to introduce mistakes during reuse, then say "mww >>> some_xyz_register 0x2" where the name of the register clues you into what it >>> does or at least where to find it in the datasheet. >>> >>> >> Agreed. I wonder if this is already possible now? >> > > set xyz_register 0xffff3ec2 > set abc_magic_value 0x12341234 > ... > > mww $xyz_register $abc_magic_value > #or > mww $xyz_register 0x02 > > Best regards, > Magnus > > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
