[Openocd-development] Monolithic config files
One thing I see on the net are monolithic config files where the configuration of the interface is mixed into the target configuration. How about making it illegal to have the interface command together with target? This would (strongly) encourage target files to be made independant of interface configuration. Enforcement can be done in various ways... -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Monolithic config files
One thing I see on the net are monolithic config files where the configuration of the interface is mixed into the target configuration. How about making it illegal to have the interface command together with target? This would (strongly) encourage target files to be made independant of interface configuration. Enforcement can be done in various ways... For me, it is a bad idea ! Fro some of our cusotmers, we provide an unique configuration file for their custom board. This unique configuration file include startup : - statup sequence - interface - board - ... Having ONE unique configuration file IS a big advantage making the configuration stronger. Regards, Laurent http://www.amontec.com -- Making JTAG a Snap with JTAGkey full-speed USB JTAG adapter with JTAGkey2 high-speed USB JTAG dongle ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Monolithic config files
Why do you prefer to have the interface definition inside such config files? Why would you *not* want the interface config file to come from OpenOCD's published configuration files for interaces? openocd -f interface/abc.cfg -f customerconfig.cfg -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Monolithic config files
Øyvind Harboe wrote: Why do you prefer to have the interface definition inside such config files? Why would you *not* want the interface config file to come from OpenOCD's published configuration files for interaces? openocd -f interface/abc.cfg -f customerconfig.cfg At the begin of OpenOCD (in 2005 for Amontec), it was very powerful to have the possibility to provide to our customers only one openocd.exe and one openocd.cfg for their specific boards. In this way, Amontec was minimizing the risk regarding file versions ... This was the case for a lot of our customers using OpenOCD in daisy chain (multi TAP/devices in the same chain), ... When your customer ask you for an issue using the OpenOCD for their specific JTAG chain, your first reflex is to ask about what version they use, what configuration files they use, and if possible the shematic of the specific board ... Some mails after, some hours after, you provide one openocd.exe and one openocd.cfg , and you ask your customer to test with these two files as: openocd -f myconfig.cfg The openocd -f interface/abc.cfg -f customerconfig.cfg is better as it split interface and board configuration, but sometimes the ONE configuration file can stay a great advantage. Regards, Laurent http://www.amontec.com -- Making JTAG a Snap with JTAGkey full-speed USB JTAG adapter with JTAGkey2 high-speed USB JTAG dongle ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Monolithic config files
On Monday 08 June 2009, Øyvind Harboe wrote: How about making it illegal to have the interface command together with target? I'd say no, on the general principle that such policy choices should in user hands. This would (strongly) encourage target files to be made independant of interface configuration. I wouldn't object to a warning, if it could be suppressed for the inevitable cases where it's spurious. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Monolithic config files
Ø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
Re: [Openocd-development] Monolithic config files
One thing that I'd like to see are more target config scripts being fed back to the community -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Monolithic config files
oyvind [make monolithic config files illegal] laurent For me, it is a bad idea ! I also dislike it, it is often helpful for debug reasons. -Duane. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
