Øyvind Harboe wrote: > Why do you prefer to have the interface definition inside such > config files? > It makes perfect sense if the interface is on the same board as the target, as with many of the USB-dongle style evaluation kits (STR9-comstick etc.). > Why would you *not* want the interface config file to come from > OpenOCD's published configuration files for interaces? > Hm - I found I had to edit the interface configs anyway, so I now have copies sitting in ~/.openocd[1], along with my target config files. Also, by doing so I can omit the interface/ and target/ prefixes on the commandline.
I agree that is makes sense to have target and interface configs separate (I do so, because I tend to switch between FT2232 and parport dongles on the same targets), but I would not forbid single config files - they may be useful for special setups. cu Michael [1] /usr/local/bin/openocd is a wrapper that basically contains exec /opt/openocd-0.1.0/bin/openocd -s ~/.openocd $@ _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
