AnsweredAssumed Answered

Debugging Linux application using ZedBoard and FMCOMMS2

Question asked by cpmullins on Oct 21, 2014
Latest reply on Oct 29, 2014 by mhennerich

Hello,

 

I have just started using a ZedBoard + FMCOMMS2 eval kit with Vivado 2013.4 installed.

 

If I use the ZedBoard SD card, I can create a simple Linux application project and debug it as a Remote ARM Linux Application (logged in with user ID: root and Password: root).

 

If I use the Analog Devices SD card (January 2014 build) and try to do the same thing with the password set to 'analog', I see something like:

 

739-gdb-set confirm off

739^done

(gdb)

740-gdb-set width 0

740^done

(gdb)

741-gdb-set height 0

741^done

(gdb)

742-interpreter-exec console echo

742^done

(gdb)

743-gdb-show prompt

743^done,value="(gdb) "

(gdb)

744-gdb-set target-async 0

744^done

(gdb)

745-gdb-set auto-solib-add on

745^done

(gdb)

746-gdb-set stop-on-solib-events 0

746^done

(gdb)

747-gdb-set stop-on-solib-events 1

747^done

(gdb)

748-target-select remote 192.168.1.10:1234

~"Ignoring packet error, continuing...\n"

warning: unrecognized item "timeout" in "qSupported" response

Ignoring packet error, continuing...

&"warning: unrecognized item \"timeout\" in \"qSupported\" response\n"

~"Ignoring packet error, continuing...\n"

Ignoring packet error, continuing...

~"Ignoring packet error, continuing...\n"

Ignoring packet error, continuing...

~"Ignoring packet error, continuing...\n"

Ignoring packet error, continuing...

~"Ignoring packet error, continuing...\n"

Ignoring packet error, continuing...

~"Ignoring packet error, continuing...\n"

Ignoring packet error, continuing...

=thread-group-started,id="i1",pid="42000"

=thread-created,id="1",group-id="i1"

~"Ignoring packet error, continuing...\n"

Ignoring packet error, continuing...

=thread-group-exited,id="i1"

748^error,msg="Malformed response to offset query, timeout"

(gdb)

749-gdb-exit

749^exit

 

Am I missing something really simple or is there a configuration step I need to perform first before I can use the debugger?

 

Regards,

Chris

Outcomes