Re: [Openocd-development] My source [find target, interface etc.] lines in my .cfg files don't work with latest build
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 Hutchinsonb.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
[Openocd-development] My source [find target, interface etc.] lines in my .cfg files don't work with latest build
I searched and saw the thread on find tcl/target etc. from a week ago but can't figure out what is going on. Do we not use source [find interface/jtagkey.cfg] type lines in our configs anymore? I guess I've missed something ... tough to be on vacation and come back to a full inbox :) Regards, Brian ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] My source [find target, interface etc.] lines in my .cfg files don't work with latest build
On Tue, Jun 9, 2009 at 5:26 PM, Brian Hutchinson b.hutch...@gmail.comwrote: I searched and saw the thread on find tcl/target etc. from a week ago but can't figure out what is going on. Do we not use source [find interface/jtagkey.cfg] type lines in our configs anymore? I guess I've missed something ... tough to be on vacation and come back to a full inbox :) Regards, Brian I usually start openocd with a line like: openocd -c fast enable -f board/my_board.cfg -c init With SVN 2177, it complained that it couldn't find my_board.cfg. I took the board out and tried to launch with just: openocd -c fast enable -f my_board.cfg -c init ... and then it complained about my first source [find target/ ... ] line. Searched the list and the only thing that smelled like what I was 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. Hope that sheds more light I what I'm talking about since the first post was knee-jerk. Regards, Brian ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] My source [find target, interface etc.] lines in my .cfg files don't work with latest build
On Tue, 2009-06-09 at 17:52 -0400, Brian Hutchinson wrote: On Tue, Jun 9, 2009 at 5:26 PM, Brian Hutchinson b.hutch...@gmail.com wrote: I searched and saw the thread on find tcl/target etc. from a week ago but can't figure out what is going on. Do we not use source [find interface/jtagkey.cfg] type lines in our configs anymore? I guess I've missed something ... tough to be on vacation and come back to a full inbox :) Regards, Brian I usually start openocd with a line like: openocd -c fast enable -f board/my_board.cfg -c init With SVN 2177, it complained that it couldn't find my_board.cfg. I took the board out and tried to launch with just: openocd -c fast enable -f my_board.cfg -c init ... and then it complained about my first source [find target/ ... ] line. Searched the list and the only thing that smelled like what I was 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 ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] My source [find target, interface etc.] lines in my .cfg files don't work with latest build
On Tue, Jun 9, 2009 at 8:05 PM, Zach Welch z...@superlucidity.net wrote: On Tue, 2009-06-09 at 17:52 -0400, Brian Hutchinson wrote: On Tue, Jun 9, 2009 at 5:26 PM, Brian Hutchinson b.hutch...@gmail.com wrote: I searched and saw the thread on find tcl/target etc. from a week ago but can't figure out what is going on. Do we not use source [find interface/jtagkey.cfg] type lines in our configs anymore? I guess I've missed something ... tough to be on vacation and come back to a full inbox :) Regards, Brian I usually start openocd with a line like: openocd -c fast enable -f board/my_board.cfg -c init With SVN 2177, it complained that it couldn't find my_board.cfg. I took the board out and tried to launch with just: openocd -c fast enable -f my_board.cfg -c init ... and then it complained about my first source [find target/ ... ] line. Searched the list and the only thing that smelled like what I was 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. Regards, Brian ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
