Am 2016-06-03 11:37, schrieb Deval Shah:
[...]
Now for the debugging what are the methods with qemu? As in how to get
step
by step analysis of the running program ?
If you run qemu with the options -s -S it will break at the beginning of
the program and allow a gdb connection.
You can then connect to qemu from within gdb with "target remote :1234"
and debug the programm as usual.
Best regards,
Jan
Thank you,
Deval Shah
On Fri, Jun 3, 2016 at 1:50 PM, Deval Shah <deval.ma...@gmail.com>
wrote:
Hello,
I was going through last years mailing list for debugging the issue. I
found this
https://lists.rtems.org/pipermail/devel/2015-June/011741.html.
Can someone explain how to get the linker map file ?
On Wed, Jun 1, 2016 at 11:01 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
Hello Deval,
I would use a hardware debugger or Qemu to tackle this problem.
On 31/05/16 19:32, Deval Shah wrote:
Hello,
I have managed to resolve previous errors and the driver is finally
building. I want to test this on hardware now. I tried running
"USB01"
testsuit for this. But I could not see any output on minicom.
Is there any debug flag/macro which I can turn on in order to get
all
the error log? Or any other debug method for raspberry pi hardware ?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
