On Jan 19, 2009, at 2:20 PM, Steve Franks wrote:
This is because you have to tell openocd about your config. take for the docsopenocd -f interface/parport.cfg -f target/at91r40008.cfg -c init - c "resethalt"Oh, dumb me. The wording made me think we were now installing the cfg's in /usr/share/openocd or something like that (which would be an ideal case from my point of view)....thought there was some discussion about a set of 'standard' cfg files the last couple months - the board is often unique, but the part and the dongle are usually the same, and could come right out of /usr/local/share/openocd/cfg/ Steve
We do install them in a common location, but you still need to tell us which files to load. The standard configs are just installed in the standard search path. So, '-f target/at91r40008.cfg' looks for target/ at91r40008.cfg in the current directory and then in the search paths. We split the configs into interfaces, targets, and boards to make it clear which is which.
-- Rick Altherr kc8...@kc8apf.net"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
