If the file is present on your computer, make sure OpenOCD can find it from one of its default search paths. Make sure the config file exists and the path you specified is correct. For example, suppose you ran OpenOCD as above and saw the following error: You run OpenOCD with the -f switch and OpenOCD can't find the file. See the links at the bottom of this page for more information on config files. If you know how to write your own config files you can also write your own openocd.cfg and place it in the same directory as the OpenOCD binary, but this is not necessary. Openocd -f interface/flyswatter2.cfg -f board/hammer.cfg Run OpenOCD again, using the -f switch to specify the path to each config file. If you have compiled OpenOCD from source, they are most likely located in your OpenOCD directory, at tcl/interface, tcl/board, or tcl/target. Even if it did, it wouldn't do any good because it wouldn't be tailored to any particular hardware.įind the config files with your hardware. However, OpenOCD doesn't provide openocd.cfg by default. If you don't specify any, it searches for openocd.cfg. OpenOCD requires at least one config file to tell it how to communicate with your hardware. If you see this message, you have likely run OpenOCD with no command line arguments.
0 kommentar(er)
