Good point, Martin! “Pull style” and related with TCF Dev should be fine.
I think my discussion with Eugene was fitting into this pattern
J
Regards,
Daniel
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin
Sent: Freitag, 19. Oktober 2012 20:23
To: TCF Development
Subject: Re: [tcf-dev] XILINX TCF Agent (Zynq)
Hi Eugene, Doug –
I’ll state my personal opinion here, but I’ll happy to get input from the Tools PMC (represented by Doug).
Personally, I agree that I find a reasonable amount of commercial talk acceptable on a mailing list
or a newsgroup… as long as it is “pull style” and not “push style”.
“Who uses X already commercially ? Who plans adopting it ?” are among the first questions that I
always hear from interested parties who consider adopting new technology X … so providing that
information in an open and transparent way makes sense to me.
What I wouldn’t want to see is the mailing list (or the newsgroup) degenerate to a medium for announcing
new commercial product releases or advertising for such; mailing lists and newsgroups should be focused
on the (Open) technology and not on the (closed) products on top of it. Companies need to use their own
channels for advertising. Using an Eclipse Channel for that feels like Spam and I haven’t seen that on any Eclipse
list so far.
But answering an interested person’s question should always be OK.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
Why? According to the Eclipse web site, Eclipse Foundation is “commercially-friendly” organization.
Regards,
Eugene
BTW, guys, this is probably an inappropriate use of the eclipse mailing list to discuss commercial products. Please only talk about
what's going into the TCF project, unless you plan on contributing all of this :)
Hi Eugene,
That’s good news for us.
Thanks for sharing the information!
Daniel
Hi Daniel,
We plan to include TCF into 2013.1 release of Xilinx SDK. We will continue to support GDB too.
TCF agent will handle all Zynq JTAG communications for both GDB and TCF debugger, and for other tools.
With TCF, we get true multicore, whole system debugger; we have improved debugger speed more than 10 times, and resolved various
stability and JTAG cable sharing issues.
Regards,
Eugene
Hi Eugene,
We are evaluating using Zynq platform, so would be interesting to know if Xilinx plans to switch from GDB to TCF and/or give an OpenSource
TCF agent that supports e.g. Zynq JTAG.
Do you have a rough estimation if and when this will be available?
Tahnks,
Daniel
Hi Markus,
Yes, we are working on a TCF agent that contain open source code as is, and includes additional proprietary modules to support ARM,
Zynq, Microblaze, JTAG, etc.
Regards,
Eugene
Hi Eugene,
that means if we use ARM platforms from Xilinx (like zync) we would get a different tcf-agent with debugging support?
Best regards,
Markus
Von: Eugene Tarassov <eugene.tarassov@xxxxxxxxxx>
An: TCF Development <tcf-dev@xxxxxxxxxxx>
Datum: 05.10.2012 19:24
Betreff: Re: [tcf-dev] Antwort: Re: Using TCF With Eclipse Debugger
Gesendet von: tcf-dev-bounces@xxxxxxxxxxx
Hi Markus,
> What exactly is the reason that ARM debugging is missing in that agent
Don’t know about others, my company is not willing to put ARM debugging code to open source at this time, because it is considered to be a competitive advantage.
At same time, contributions from the community are welcome
J
> …
and how much effort would it be to implement that?
To support ARM debugging, one needs to implement 3 main components: ARM register descriptors, stack tracing (no symbol info case), and disassembler.
Regards,
Eugene
From:tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of markus.proeller@xxxxxxx
Sent: Thursday, October 04, 2012 10:06 PM
To: TCF Development
Subject: [tcf-dev] Antwort: Re: Using TCF With Eclipse Debugger
Hello Eugene,
we are using the agent from http://git.eclipse.org/c/tcf/org.eclipse.tcf.agent.git/
What exactly is the reason that ARM debugging is missing in that agent and how much effort would it be to implement that?
Best regards,
Markus
Von: Eugene Tarassov <eugene.tarassov@xxxxxxxxxx>
An: TCF Development <tcf-dev@xxxxxxxxxxx>
Datum: 01.10.2012 19:43
Betreff: Re: [tcf-dev] Using TCF With Eclipse Debugger
Gesendet von: tcf-dev-bounces@xxxxxxxxxxx
Hi Markus,
What agent are you using?
ARM debugging support is not available in the open source TCF agent.
Regards,
Eugene
From:
tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]On
Behalf Of markus.proeller@xxxxxxx
Sent: Monday, October 01, 2012 1:49 AM
To: tcf-dev@xxxxxxxxxxx
Subject: [tcf-dev] Using TCF With Eclipse Debugger
Hello,
I have a question regarding TCF and the integrated CDT Debugger.
My Eclipse is running on a Windows 7 (64 bit) machine and I have a tcf-agent running on an ARM with Linux.
I'm trying to debug a remote application on the ARM.
In Eclipse under "Debug Configuration" I added a configuration for "Target Communication Framework". I filled out the project name, local file path and remote file path. On the target page I set up the target manually. When I hit the button "Run Tests" I get
Connection Diagnostics Errors:
java.lang.Exception: Invalid error report text
at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)
at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)
at org.eclipse.tcf.core.Command.result(Command.java:111)
at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)
at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)
at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)
at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)
at java.lang.Thread.run(Unknown Source)
java.lang.Exception: Invalid error report text
at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)
at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)
at org.eclipse.tcf.core.Command.result(Command.java:111)
at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)
at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)
at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)
at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)
at java.lang.Thread.run(Unknown Source)
java.lang.Exception: Invalid error report text
at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)
at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)
at org.eclipse.tcf.core.Command.result(Command.java:111)
at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)
at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)
at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)
at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)
at java.lang.Thread.run(Unknown Source)
java.lang.Exception: Invalid error report text
at org.eclipse.tcf.internal.debug.tests.TestEchoERR.doneEchoERR(TestEchoERR.java:107)
at org.eclipse.tcf.internal.services.remote.DiagnosticsProxy$3.done(DiagnosticsProxy.java:134)
at org.eclipse.tcf.core.Command.result(Command.java:111)
at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:906)
at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:852)
at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:254)
at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)
at java.lang.Thread.run(Unknown Source)
I ignored the errors and hit the Debug button anyway. In the Debug view, I see a new "Debug process" showing up, but nothing else happens. THe name of the Debug process is
remote_debug (imx6: Connecting)
Note: I also used TCF with Remote System Explorer for the same target and I was able to browse the file system and processes.
Best regards,
Markus
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy,
or forward this email message or any attachments. Delete this email message and any attachments immediately.
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/tcf-dev
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy,
or forward this email message or any attachments. Delete this email message and any attachments immediately.
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/tcf-dev
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy,
or forward this email message or any attachments. Delete this email message and any attachments immediately.
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy,
or forward this email message or any attachments. Delete this email message and any attachments immediately.
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy,
or forward this email message or any attachments. Delete this email message and any attachments immediately.
|
