Re: [OpenOCD-user] results of commands given with -c no longer printed to stdout/stderr

[Tommy M. <tom...@ho...>]

I wonder if this commit changed the behaviour and, if so, if it was intentional?

https://repo.or.cz/openocd.git/commit/c826746068d46099eb787c403a240b4afff37c0a

If not the maybe something else here?

https://repo.or.cz/openocd.git/history/HEAD:/src/helper/command.c

________________________________
From: matthew venn <ma...@ma...>
Sent: Thursday 12 March 2020 14:14
To: ope...@li... <ope...@li...>
Subject: [OpenOCD-user] results of commands given with -c no longer printed to stdout/stderr

Hi all,
I just compiled from source openocd. I checked it out from: https://github.com/ntfreak/openocd
The ubuntu install doesn't support nvmuserrow subcommand.

I'm scripting openocd with Python and giving it commands with -c, for example:

/usr/local/bin/openocd -f arduino_zero.cfg --command "telnet_port disabled; init; halt; at91samd nvmuserrow; shutdown"

This used to (in previous versions) print out the fuses set on an atmel samd21 device.

Now, it prints nothing. If I enabled debug level 3 with -d3, I can see the command sent ok, but no results are printed.

Same thing with with

/usr/local/bin/openocd -f arduino_zero.cfg -c 'init;  mdw 0x0080A00C;mdw 0x0080A040;mdw 0x0080A044;mdw 0x0080A048;shutdown'

Previously this would print out the contents of those registers, now it prints nothing.

Any way of getting this information? I'd rather not start openocd as a separate process and interact via socket (which does print the results)

Thanks,
Matt

--
Matthew Venn
web mattvenn.net<http://mattvenn.net> twitter @matthewvenn<https://twitter.com/matthewvenn>