On Wed, Jun 10, 2009 at 3:38 AM, Kees Jongenburger < kees.jongenbur...@gmail.com> wrote:
> On Wed, Jun 10, 2009 at 4:13 AM, Brian Hutchinson<b.hutch...@gmail.com> > wrote: > >> > seeing was: > >> > > >> > > http://www.mail-archive.com/openocd-development@lists.berlios.de/msg05321.html > >> > > >> > I'm using custom .cfg files that were already in > >> > my /usr/loca/lib/openocd tree. > >> > >> The installed path of these files changed in revision r1920. Its commit > >> comment documents the specific changes, but the gist of it would be that > >> OpenOCD searches for these files in a $(pkgdatadir)/scripts or > >> $(pkgdatadir)/site. Your scripts should live under the later path. > >> > >> Cheers, > >> > >> Zach > >> > > Thanks, > > > > I noticed that if I launched openocd from my /usr/local/lib/openocd > > directory that it worked. I'll check out the comments you mentioned and > > move my scripts to the right place. > > yup apparently the directory where openocd searches is not the one > configured while running configure > it searched /usr/local/... even if you configure using --prefix=/usr > > > > > Regards, > > > > Brian > > > > _______________________________________________ > > Openocd-development mailing list > > Openocd-development@lists.berlios.de > > https://lists.berlios.de/mailman/listinfo/openocd-development > > > > Well, it turns out it didn't work with my new target even after I moved my .cfg files to the right place. I backed off the bleeding edge and used SVN 1940 and it worked better ... at least I could reset my target without it timing out and got less scary messages when it connected. Will try to figure out more today and report back. Thanks! Brian
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
