Re: [tcf-dev] Question about debugging a embedded device using TCF

[Didier Brachet <didier.brachet@xxxxxxxxxxxxx>]

To build with SSL, you must define ENABLE_SSL to 0 in tcf/config.h file and you should remove libssl from the LIBS variable in Makefile.inc.

If you do not have debug services enabled; you can still use TCF agent to enumerate processes, access target file system, spawn a process and redirect its input/output... but you cannot do any debugging. Some people are using this to just spawn their program and start a remote gdbserver to attach to this process; I think Eclipse has a configuration to support this.

Of course, you are welcome if you want to add MIPS debug support to TCF Agent.

Didier

SHREYAS JOSHI wrote:

Hi Didier,

Thank you very much!

The build goes well, but fails at the linking part.

Is there any way to build without ssl?

Also, what I can do without debug services enabled?

What will be the use case of TCF for me?

Thanks  & regards,
Shreyas Joshi

 make CC=/export/home/joshis1/D183_Alignment_Head/tools/toolchains/i386/Linux/broadcom/7231/stbgcc-4.5.3-1.3/bin/mipsel-uclibc-gcc MACHINE=mipsel
/export/home/joshis1/D183_Alignment_Head/tools/toolchains/i386/Linux/broadcom/7231/stbgcc-4.5.3-1.3/bin/mipsel-uclibc-gcc -g -D_FILE_OFFSET_BITS=64 -Wall -Wmissing-prototypes -I./. -I./system/GNU/Linux -I./machine/mipsel  -o obj/GNU/Linux/mipsel/Debug/agent obj/GNU/Linux/mipsel/Debug/tcf/main/main.o \
        obj/GNU/Linux/mipsel/Debug/libtcf.a -lpthread -lssl -lcrypto -lrt -luuid
/export/home/joshis1/D183_Alignment_Head/tools/toolchains/i386/Linux/broadcom/7231/stbgcc-4.5.3-1.3/bin/../lib/gcc/mipsel-linux-uclibc/4.5.3/../../../../mipsel-linux-uclibc/bin/ld: cannot find -lssl
collect2: ld returned 1 exit status
make: *** [obj/GNU/Linux/mipsel/Debug/agent] Error 1

---

From: Didier Brachet <didier.brachet@xxxxxxxxxxxxx>
To: tcf-dev@xxxxxxxxxxx
Sent: Wednesday, July 24, 2013 2:06 PM
Subject: Re: [tcf-dev] Question about debugging a embedded device using TCF

Hello,

First of all, MIPS is currently not a supported architecture for debug with TCF agent; debug is supported for Intel (x86 and x86-64) and arm architectures. It would still be possible to build and use TCF agent for MIPS but debug related services must be disabled (by editing config.h).

If you want to build the TCF agent for your embedded box; the easiest solution is to build it natively on this box. Of course, this can be done only if you have all the pieces (GNU compiler, make utility...) available on it. If you absolutely need to cross compile, then it will not work out of the box but this is achievable. You will certainly have to update the Makefile.inc file to provide the correct include path (point to header files of your embedded box file system) and then you should be able to run the build with a command like this one:

make CC=<path to MIPS gcc cross-compiler> MACHINE=mipsle

Regards,
Didier Brachet

SHREYAS JOSHI wrote:

Hi,

I have an embedded box. This runs linux on it. It is based on MIPS architecture.
To be more specific it is mipsel. I want to debug my application using TCF.

I understand in order to first connect to the remote target. I need to have a agent running on it.
I downloaded the agent code.
git clone git://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git
 
 How can I cross-compile with my toolchain to generate agent binary?

My first way to check the agent is by doing a telnet into the box via TCF.

The steps I do follow are

1) Windows-> OpenPerspective->others -> Remote System Explorer.

2) Right click -> new connection-> Telnet ( experimental) only.

3) HostName IP address; this is my target device IP address.

4) After all these steps it doesn't connect. I believe the reason is that the agent is not running in the box.

Please correct me if I am wrong here.

Then the entire problem boils down to "How can I cross compile the agent for my mipsel toolchain".

I already have a toolchain with me.

Thanks & regards,

Shreyas Joshi

_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tcf-dev

_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tcf-dev

_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tcf-dev