On Fri, Oct 21, 2011 at 7:06 PM, Spencer Oliver <s...@spen-soft.co.uk> wrote:
> On 20 October 2011 17:04, Freddie Chopin <freddie_cho...@op.pl> wrote:
>> The only working version that I've found is:
>>> openocd -f ../interface/jtagkey.cfg -f ../target/stm32.cfg
>>
>
> i cannot reproduce this problem, any more details.
>

I can reproduce the issue with the latest git, build under Windows
with MinGW/MSys.

For version 0.5.0, the following two commands work and I use only
either of them.
openocd.exe -f board\ek-lm3s1968.cfg
openocd.exe -f board/ek-lm3s1968.cfg

For latest git, none of the following commands work.
openocd.exe -f board\ek-lm3s1968.cfg
openocd.exe -f board/ek-lm3s1968.cfg
openocd.exe -f board\\ek-lm3s1968.cfg
openocd.exe -f board//ek-lm3s1968.cfg
openocd.exe -f ..\board\ek-lm3s1968.cfg

Example running log.
C:\work\openocd\binary\bin>openocd.exe -f board//ek-lm3s1968.cfg
Open On-Chip Debugger 0.6.0-dev-snapshot (2011-10-21-21:26)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.sourceforge.net/doc/doxygen/bugs.html
Runtime Error: embedded:startup.tcl:58: couldn't read file "C:workopenocinarin..
/board//ek-lm3s1968.cfg": No such file or directory
in procedure 'script'
at file "embedded:startup.tcl", line 58

C:\work\openocd\binary\bin>openocd.exe -f ..\board\ek-lm3s1968.cfg
Open On-Chip Debugger 0.6.0-dev-snapshot (2011-10-21-21:26)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.sourceforge.net/doc/doxygen/bugs.html
Runtime Error: embedded:startup.tcl:58: couldn't read file ".oardek-lm3s1968.cfg
": No such file or directory
in procedure 'script'
at file "embedded:startup.tcl", line 58

> Double backslash seems to fix it.

That helps. The following commands work.
openocd.exe -f ..\\board\\ek-lm3s1968.cfg
openocd.exe -f ..//board//ek-lm3s1968.cfg

The following command also works.
openocd.exe -f ../board/ek-lm3s1968.cfg


-- 
Xiaofan
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to