|
From: Paul F. <fer...@gm...> - 2015-12-30 06:55:19
|
Hey Ron, On Tue, Dec 29, 2015 at 12:24:46PM -0800, Ron Garret wrote: > > On Tue, Dec 29, 2015 at 11:21:01AM -0800, Ron Garret wrote: > >> ron@ubuntu1:~$ /usr/bin/openocd -f stm32f3x.cfg > > > > This is where it's obviously wrong. You need to source adapter config > > before the target config. Or if you have f3 disco, then you can use > > the board config as in: "openocd -f board/stm32f3discovery.cfg". > > > > You seem to be trying to use some out-of-tree config, please do not do > > that, use upstream configs (that come with OpenOCD) instead. > > My ~/interfaces is just a symlink to > openocd-0.9.0-rc1/tcl/interface. Is that not the right thing? Yes, that's not the right thing to do. You're supposed to either install openocd properly (via package manager or with "sudo make install") and then openocd would know the root of the configuration scripts tree and use that automatically. So no explicit patch or symlinks or anything else necessary. > shell). I’ve hired a contractor to build me a USB dongle, and I’m > trying to run his code (which includes the stm32f3x.cfg file that > I’m using) No, you shouldn't be using any external config files. > according to the instructions he provided me. He did his > development on Windows, but I’m allergic to Windows so I’m trying to > run his code on Ubuntu. So despite the fact that I’m using openocd, > I am fairly clueless about how it works. So, for example, I have no > idea what “f3 disco” is (Google is no help here), or what you mean > by “upstream configs”. Upstream of what? By f3 disco I meant "STM32F3 Discovery Board". Upstream configs are the scripts that present in OpenOCD source code and that are installed along with OpenOCD. If you describe in detail what hardware you have and how it is connected, I'll be able to tell you what scripts to source. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fer...@gm... |