[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [dsdp-tcf-dev] Porting TCF agent
|
Hi,
I've succeeded connecting to the agent through the RSE, but I now have a new issue with the file subsystem : when I try to explore the Home and Root folders, I don't have anything under it (no file or directory). On the other hand, the creation of a new file or folder with the RSE works fine, so there's no problem with the subsytem in general, just with the fetching of the tree structure. Could it be related to a bad implementation of the "canonicalize_file_name" function (ugly copy/paste in my case) ?
Regards,
Florian
2009/7/3 Florian Guillochon
<florian.guillochon@xxxxxxxxx>
Thank you for answering that fast. I should have spent more time reading the specs.
Anyway, thank you for that useful information ;).
Regards,
Florian
2009/7/2 Tarassov, Eugene
<eugene.tarassov@xxxxxxxxxxxxx>
Hi Florian,
List of available services is sent to a client when it
connect to a target. This is part of TCF communication protocol, and TCF
Discovery is not needed for that. Discovery is used to find out available
targets and connection info, like target IP addresses and port numbers. At
this time, RSE integration does not use that data
anyway.
Regards,
Eugene.
Sent: Thursday, July 02, 2009 2:31 AM
To: DSDP
TCF dev list
Subject: Re: [dsdp-tcf-dev] Porting TCF
agent
Hi, i've been trying to port the TCF agent on our OS, and I finally
got it running on the target.
As I would like to use it for the RemoteCDT
functionnality, I only need the filesystem service (shell service already
available).
Logically, my config.h only contains the filesystem related
API.
UDP broadcast is not available on the target, so I can't use the UDP
Discovery functionnality.
My question is how can the filesystem service
be discovered by the RSE client when I connect to my target ? The only info I
can enter is the IP address of the target.
Florian
2009/6/24 Tarassov, Eugene
<eugene.tarassov@xxxxxxxxxxxxx>
Hi
Florian,
No, it has
not yet. The bug is still open.
It is
probably not enough, but it is pretty much all that is available at the
moment. So, reading the source code is the best source of information about
porting the agent at the moment. More docs are expected to be available
later.
> More generally, what can I expect
from the 1.0 version of TCF ?
In
general, no major changes are planned. Version 1.0 would mean formal
commitment to maintain backward compatibility of all public APIs and protocol
specs. They are very stable already, so I don't expect any big
surprises.
Regards,
Eugene
Hello everybody,
I'm a french student, currently in
placement, and I intend to port the TCF agent to a proprietary real-time OS,
to be able to use the remote debug functionality in CDT.
I have a shell
subsystem working but no file subsystem. I decided to port the TCF agent
because it could result in more future oportunities than porting a simple FTP
server.
I'm a total newcomer concerning TCF so I have read some entries on
the mailing list and on bugzilla, but I'd like to ask you a few questions
:
Thank you for the
support,
Florian
_______________________________________________
dsdp-tcf-dev
mailing list
dsdp-tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev
_______________________________________________
dsdp-tcf-dev mailing list
dsdp-tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tcf-dev