cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
fernandovives
Adventurer
Adventurer
1,332 Views
Registered: ‎12-16-2018

How to link the xilinx SDK 2017.4 with QEMU?

Jump to solution

Hi all,

I'M trying to use the QEMU emulator for ZYNQ devices from the XILINX SDK to debug my application, but the client connection never respond. Is there any other way to do that?  What's wrong with my configuration. This how look my desktop. Thanks

xilinx_screenshot_3_QEMU.png
0 Kudos
1 Solution

Accepted Solutions
ibaie
Xilinx Employee
Xilinx Employee
1,225 Views
Registered: ‎10-06-2016

Hi @fernandovives,

First of all the QEMU integration within SDK is not supported for Windows SDK yet, so it will not work properly even solving the issue with the target connection as explained bellow.

The QEMU target connection is not used to to connect the System Debugger to the GDB server running on the QEMU machine, as you can see in the type field is used to connect to an bridge application called TcfGdbClient. This software components bridges between the TCF connection to GDB server, so can be used to connect the System Debugger with the QEMU machine.

So the idea would be launch QEMU on one terminal, launch TcfGdbClient on a different one that connects to the QEMU GDB server, once done you should be able to perform the "Test Connection" properly. You could also check that the targets running on QEMU can be found as well from XSCT.

xsct% connect -url tcp:localhost:1145
tcfchan#2
xsct% ta
xsct% gdbremote connect tcp::1144
xsct% Info: CPU#0 /machine/unattached/device[0] (target 3) Stopped at 0xeb8cbc (Suspended)
xsct% 

The main problem is that the SDK Debugger is intended to launch both the QEMU machine and the TcfGdbClient, and connect the debugger to it. If you test it in Linux you can see that is working fine but in windows it is not still implemented properly.

Regards


Ibai
Don’t forget to reply, kudo, and accept as solution.

View solution in original post

0 Kudos
2 Replies
ibaie
Xilinx Employee
Xilinx Employee
1,226 Views
Registered: ‎10-06-2016

Hi @fernandovives,

First of all the QEMU integration within SDK is not supported for Windows SDK yet, so it will not work properly even solving the issue with the target connection as explained bellow.

The QEMU target connection is not used to to connect the System Debugger to the GDB server running on the QEMU machine, as you can see in the type field is used to connect to an bridge application called TcfGdbClient. This software components bridges between the TCF connection to GDB server, so can be used to connect the System Debugger with the QEMU machine.

So the idea would be launch QEMU on one terminal, launch TcfGdbClient on a different one that connects to the QEMU GDB server, once done you should be able to perform the "Test Connection" properly. You could also check that the targets running on QEMU can be found as well from XSCT.

xsct% connect -url tcp:localhost:1145
tcfchan#2
xsct% ta
xsct% gdbremote connect tcp::1144
xsct% Info: CPU#0 /machine/unattached/device[0] (target 3) Stopped at 0xeb8cbc (Suspended)
xsct% 

The main problem is that the SDK Debugger is intended to launch both the QEMU machine and the TcfGdbClient, and connect the debugger to it. If you test it in Linux you can see that is working fine but in windows it is not still implemented properly.

Regards


Ibai
Don’t forget to reply, kudo, and accept as solution.

View solution in original post

0 Kudos
fernandovives
Adventurer
Adventurer
1,182 Views
Registered: ‎12-16-2018

Hi

thanks for reply.

0 Kudos