Øyvind> regression testing.
Yes. I'm not setup to do much of that :-(
Øyvind> - I'd like to see the these sort of scripts tied into the target
library
Øyvind> using polymorphism. That is we define a few proc's in
commands.tcl that
A simple approach is this:
Step 1: Define a set of commands we expect to be uniform for all platforms.
And document their expected interface.
For example - a standardized set of GPIO or ADC - what every the may be.
And - "VENDOR SPECIFIC" rules.
Step 2: We create a small TCL script - that is always loaded - which
does nothing more then throw errors
This is an example of the GPIO command.
proc gpio { HELP } {
error { "No GPIO command defined for this chip\n"
"Or the chip specific TCL file has not been loaded or
does not exist\n"
"Try looking in in \${src}/chips/MAKER/FAMILY/NAME.tcl\n"
"If you want to create one - see the docs file <SOMEHWHERE>"
}
}
Step 3: When the <CHIPFILE> is loaded the above "dummy-gpio command" is
quietly released by Jim.
=======
Øyvind> Once there are some polymorph proc's defined, I'd like to
update the Zylin
Øyvind> Embedded CDT to support them. This will allow showing and even
modifying
Øyvind> peripherals from a GDB GUI frontend.
This should use the interface Charles is creating.
-Duane.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
