I started looking into the code.
I can now issue commands through the interface (turns out the
delimiter was 0x1A <-- why?! - is there a reason for this? At first
glance I'd say something like a semicolon would be much more
"normal").
When I issue a read command though, the read is executed, the result
is printed to stdout, but the tcl client never gets any response other
than command was executed successfully. Tomorrow I'll look into it a
little bit more, however I suspect that the communication is
incomplete, and this part has not yet been written.

I would write the interface if I'll have the time for it, but we'll
have to come up with some nice protocol to communicate the data in a
manner that will be easy for a machine to interpret, but still
flexible so that arrays and such can also be returned. I'm thinking
something like JSON. Not XML. Maybe it's not needed, and a raw
protocol is enough.
Any ideas?

Lastly why is the socket echoing? A machine does not need that, and it
complicates interpretation somewhat.

Regards,
  Ákos Vandra



On 22 May 2012 22:30, Andreas Fritiofson <[email protected]> wrote:
> On Tue, May 22, 2012 at 7:58 PM, Akos Vandra <[email protected]> wrote:
>> Hi!
>>
>> Sorry for spamming the list with so many threads in the last few days.
>>
>> Is there any documentation on how the TCL server (port 6666) works? Or
>> can someone give me a headstart on this?
>> I tried connecting to it with telnet, but whatever I write there,
>> nothing happens.
>
> I don't think it echoes. As for documentation, I don't know. Use the
> source, Luke!
>
> /Andreas

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to