Remote Debugging on Zynq Boards

[Vishav.Vishav at dlr.de]

Hi Chris,

Thanks for the suggestion. I followed the same procedure and now I can debug my application.

Regards
Vishav

-----Original Message-----
From: Chris Johns [mailto:chrisj at rtems.org] 
Sent: Dienstag, 21. Januar 2020 02:22
To: Vishav, Vishav; users at rtems.org
Subject: Re: Remote Debugging on Zynq Boards

On 7/1/20 9:58 pm, Vishav.Vishav at dlr.de wrote:
> I want to remotely debug an RTEMS application on Zynq based board. I have been
> following link:
> 
> https://docs.rtems.org/branches/master/user/exe/debugging.html
> 
> I am particularly interested in Libdebugger Executable Debugging. I built the
> rtems-libbsd and found the debugger01 application. I am able to boot this
> application on the target board using tftpboot. This results in gdb server on
> the board. From the host computer, I run *arm-rtems-5-gdb  **myapp*. I am able
> to connect to server using *target remote 192.168.178.1:1122. *I set the
> breakpoint using *break Init *and then *c* to continue. The host machine
> displays *continuing *but never breaks at breakpoint.

If Init is the RTEMS entry point it will have run before you connect because it
is used to start libdebugger. Setting a break point there will not work because
that code is not executabled again.

> Can someone help me know if this is correct way to debug an RTEMS application?

If I need to debug an initialisation issue start libbsd and libdebugger than I
loop checking a volatile int variable looping while it is 0. When the debugger
connects I set a break point where I wish to debug, the volatile int variable to
1 and then hit continue.

A warning, the elf image on the host (myapp) that gdb loads needs to match the
image loaded onto the target. If it does not breakpoints will not work because
GDB is using the wrong address.

Chris