ALTracer has quit [Read error: Connection reset by peer]
ALTracer has joined #openocd
ALTracer has quit [Read error: Connection reset by peer]
ALTracer has joined #openocd
ALTracer has quit [Quit: Quit]
Hawk777 has joined #openocd
Hawk777 has quit [Quit: Leaving.]
WeaselSoup has quit [Quit: Q]
WeaselSoup has joined #openocd
d_olex has joined #openocd
nerozero has joined #openocd
alkane has quit [Quit: WeeChat 4.6.0]
shibboleth has joined #openocd
Hawk777 has joined #openocd
shibboleth has quit [Quit: shibboleth]
nerozero has quit [Ping timeout: 276 seconds]
mouseghost has joined #openocd
<mouseghost>
hi. i need to interface with openocd to, for example, perform some automated breakpoint setting etc., should i use the tcl interface at the port 6666 or just straight up make openocd execute my tcl script in the built-in interpreter?
<mouseghost>
I also wonder if openocd 0x1A as a "command end" character can be somehow automated into regular Tcl...
<PaulFertser>
mouseghost: hm, depends on whether you need some operations that you're not comfortable doing in Tcl the second way.
<PaulFertser>
mouseghost: please clarify the second question, what regular Tcl and why it needs that character?
<mouseghost>
i suppose if i did the "direct to jimtcl script" then i still would need to shuffle the scripts around, generate them or something... that seems suboptimal eh
<PaulFertser>
I'm not sure why you would need to generate, again, depends on how you want to decide what breakpoints to set etc.
<mouseghost>
but i wonder if 0x1a was chosen, because, for example, tcl (normal tcl from https://www.tcl-lang.org/) has some rpc facility that uses 0x1a?
<mouseghost>
im not sure if i can explain my question better hm
<PaulFertser>
mouseghost: it's just SUB/EOF symbol from ASCII, so it's not part of what can be normally in Tcl source line.
<PaulFertser>
I do not think it's anything special beyond that.
<mouseghost>
aight
<mouseghost>
thanks
<PaulFertser>
mouseghost: the interface should be easy to use with any language of your choice
<mouseghost>
initially i wanted to use tcl (because tcl is cool) to comm with openocd's jimtcl :P
<PaulFertser>
That's fine too, shouldn't be problematic.
mouseghost_ has joined #openocd
mouseghost has quit [Ping timeout: 265 seconds]
mouseghost_ is now known as mouseghost
<mouseghost>
meh ill probably go with python, since i need something portable that most people can use z___z
<PaulFertser>
jimtcl should be available on a system running OpenOCD
wingsorc has quit [Remote host closed the connection]