Re: [OpenOCD-devel] TCL open command not working?

[<Mit...@Em...>]

p.s.  The second patch is for the jimtcl "subproject".


From: mrf...@gm... [mailto:mrf...@gm...] On Behalf Of Mark Odell
Sent: Friday, March 24, 2017 6:33 AM
To: Frazier, Mitch [AUTOSOL/FLMC/US]
Cc: ope...@li...
Subject: Re: [OpenOCD-devel] TCL open command not working?

Good to know. Thank you. I thougt I was going crazy. Yes, I'm using git master pulls so v0.10-dev.

On Wed, Mar 22, 2017 at 7:09 PM, <Mit...@em...<mailto:Mit...@em...>> wrote:
Assuming you're using OpenOCD 0.10.0 this looks like the same issue that I ran into that's described in the mailing list exchange with the subject: "[OpenOCD-devel] missing tcl commands in 0.10.0".   There is a patch in Gerrit (http://openocd.zylin.com/4001) that addresses it, but it doesn't quite fix it.   My last email to the mailing list related to the above subject contains a patch which along with the Gerrit patch referenced above fixes the problem.

From: Mark Odell [mailto:ma...@od...<mailto:ma...@od...>]
Sent: Wednesday, March 22, 2017 8:03 AM
To: ope...@li...<mailto:ope...@li...>
Subject: [OpenOCD-devel] TCL open command not working?

I recently noticed that my TCL file is now failing to log my internal debug statements to a file. I tracked it down to this:

    global g_logfh
    set fname "/tmp/usertcl-$BOARD-$DAP_SERNO.log"
    if {[catch {set g_logfh [open $fname w]} errmsg]} {
        set g_logfh -1
    }

I'm catching the error but the open call is failing stating, 'invalid command name "open"'. This used to work and I haven't changed my TCL code in ages. I didn't notice when (OpenOCD version) it started failing but I think that TCL's open command should work.

Thoughts?

- Mark