On Monday 26 October 2009, Igor Skochinsky wrote: > Hello David, > > Monday, October 26, 2009, 9:08:47 AM, you wrote: > > DB> There'd potentially be a LOT of those autoconf_$IDCODE things. > DB> So it might be important to segment them by vendor ID... that > DB> auto.cfg file looks at the ID and sources "auto/arm.cfg" or > DB> whatever. > > DB> But, I'm not sure I could see them replacing the static configs. > DB> Thing is, IDCODE values aren't especially unique between vendors, > DB> at least for microcontrollers, and there are a lot of important > DB> things they can't expose. > > It might be worth looking at how UrJtag does such things: > http://urjtag.svn.sourceforge.net/viewvc/urjtag/trunk/urjtag/data/ > See MANUFACTURERS file, then PARTS inside each manufacturer directory.
That's what I was thinking about when I mentioned auto/arm.cfg type files, partitioning by vendor ID. An auto/$VENDOR.cfg, with the vendor hex -- or binary! -- from the idcode would slightly reduce the problem; probably better than trying to figure out which vendor name applies today, for example. But it wouldn't get rid of the need for static configs, since they hold information that can't be derived from IDCODE values. - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
