<div dir="ltr">Also, <div><br></div><div>I compiled the same build for arm/realview_pbx_a9_qemu. And when I try this on qemu using this command </div><div><br></div><div>#qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M -net none -kernel sleep01.exe</div><div><div>pulseaudio: set_sink_input_volume() failed</div><div>pulseaudio: Reason: Invalid argument</div><div>pulseaudio: set_sink_input_mute() failed</div><div>pulseaudio: Reason: Invalid argument</div><div>nexus0: <RTEMS Nexus device></div></div><div>#</div><div><br></div><div>The test comes out (of the loop ?) abruptly without performing its task. i.e. sleep01 comes out without starting the slave threads or usb01 comes out without opening the shell. </div><div><br></div><div>Next I did this "objdump -t usb01.exe | grep bcm" and the output is below. </div><div><br></div><div>001be620 l O .rodata<span class="" style="white-space:pre"> </span>00000018 bcm283x_dwcotg_res</div><div>002ecc44 l O .rtemsroset<span class="" style="white-space:pre"> </span>00000014 __set_nexus_sym_bcm283x_dwcotg0</div><div>00000000 l df *ABS*<span class="" style="white-space:pre"> </span>00000000 bcm283x_dwc_fdt.c</div><div>001013a5 l F .text<span class="" style="white-space:pre"> </span>00000028 bcm283x_dwc_otg_attach</div><div>001013cd l F .text<span class="" style="white-space:pre"> </span>00000034 bcm283x_dwc_otg_probe</div><div>0030dc64 l O .bss<span class="" style="white-space:pre"> </span>00000004 bcm283x_dwc_otg_devclass</div><div>003014c8 l O .data<span class="" style="white-space:pre"> </span>0000000c _bcm283x_dwcotg_depend_on_usb</div><div>003014d4 l O .data<span class="" style="white-space:pre"> </span>0000000c _bcm283x_dwcotg_nexus_depend_on_kernel</div><div>00301570 l O .data<span class="" style="white-space:pre"> </span>0000000c bcm283x_dwcotg_nexus_mod</div><div>003014f0 l O .data<span class="" style="white-space:pre"> </span>00000010 _mod_metadata_md_bcm283x_dwcotg_nexus</div><div>00301500 l O .data<span class="" style="white-space:pre"> </span>00000010 _mod_metadata_md_bcm283x_dwcotg_nexus_on_kernel</div><div>00301510 l O .data<span class="" style="white-space:pre"> </span>00000010 _mod_metadata_md_bcm283x_dwcotg_on_usb</div><div>00301538 l O .data<span class="" style="white-space:pre"> </span>00000018 bcm283x_dwc_otg_methods</div><div>00301550 l O .data<span class="" style="white-space:pre"> </span>00000008 bcm283x_dwcotg_baseclasses</div><div>00301558 l O .data<span class="" style="white-space:pre"> </span>00000018 bcm283x_dwcotg_nexus_driver_mod</div><div>002ecb2c l O .rtemsroset<span class="" style="white-space:pre"> </span>00000004 __set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_on_usb</div><div>002ecb30 l O .rtemsroset<span class="" style="white-space:pre"> </span>00000004 __set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_nexus</div><div>002ecb34 l O .rtemsroset<span class="" style="white-space:pre"> </span>00000004 __set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_nexus_on_kernel</div><div>0030c320 l O .rtemsrwset<span class="" style="white-space:pre"> </span>00000004 __set_sysinit_set_sym__bsd_bcm283x_dwcotg_nexusmodule_sys_init</div><div>00000000 l df *ABS*<span class="" style="white-space:pre"> </span>00000000 bcm2835_mbox.c</div><div>001189f9 l F .text<span class="" style="white-space:pre"> </span>0000000c bcm2835_mbox_dma_cb</div><div>00118a05 l F .text<span class="" style="white-space:pre"> </span>0000007a bcm_mbox_write</div><div>00118a81 l F .text<span class="" style="white-space:pre"> </span>0000008c bcm_mbox_read</div><div>00118b0d l F .text<span class="" style="white-space:pre"> </span>00000060 bcm_mbox_intr</div><div>00118b6d l F .text<span class="" style="white-space:pre"> </span>00000142 bcm_mbox_attach</div><div>00118cb1 l F .text<span class="" style="white-space:pre"> </span>00000034 bcm_mbox_probe</div><div>0030ee2c l O .bss<span class="" style="white-space:pre"> </span>00000004 bcm_mbox_devclass</div><div>00305c38 l O .data<span class="" style="white-space:pre"> </span>00000018 bcm_mbox_driver</div><div>00305c50 l O .data<span class="" style="white-space:pre"> </span>00000028 bcm_mbox_methods</div><div>00000000 l df *ABS*<span class="" style="white-space:pre"> </span>00000000 bcmp.c</div><div>001ab165 g F .text<span class="" style="white-space:pre"> </span>00000004 bcmp</div><div>00118f31 g F .text<span class="" style="white-space:pre"> </span>0000004a bcm2835_mbox_set_power_state</div><div>00118ce5 g F .text<span class="" style="white-space:pre"> </span>0000024c bcm2835_mbox_property</div><div>00301520 g O .data<span class="" style="white-space:pre"> </span>00000018 bcm283x_dwc_otg_driver</div><div>003014e0 g O .data<span class="" style="white-space:pre"> </span>00000010 _bsd_bcm283x_dwcotg_nexusmodule_sys_init</div><div><br></div><div>This shows that my driver is linked properly with the app testsuit right ?</div><div><br></div><div>Now for the debugging what are the methods with qemu? As in how to get step by step analysis of the running program ? </div><div><br></div><div>Thank you, </div><div>Deval Shah</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 3, 2016 at 1:50 PM, Deval Shah <span dir="ltr"><<a href="mailto:deval.maker@gmail.com" target="_blank">deval.maker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello, <div><br></div><div>I was going through last years mailing list for debugging the issue. I found this <a href="https://lists.rtems.org/pipermail/devel/2015-June/011741.html" target="_blank">https://lists.rtems.org/pipermail/devel/2015-June/011741.html</a>. Can someone explain how to get the linker map file ? </div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 1, 2016 at 11:01 AM, Sebastian Huber <span dir="ltr"><<a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Deval,<br>
<br>
I would use a hardware debugger or Qemu to tackle this problem.<span><br>
<br>
On 31/05/16 19:32, Deval Shah wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
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.<br>
<br>
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 ?<br>
</blockquote>
<br></span><div><div>
-- <br>
Sebastian Huber, embedded brains GmbH<br>
<br>
Address : Dornierstr. 4, D-82178 Puchheim, Germany<br>
Phone : +49 89 189 47 41-16<br>
Fax : +49 89 189 47 41-09<br>
E-Mail : <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a><br>
PGP : Public key available on request.<br>
<br>
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>