Also, I compiled the same build for arm/realview_pbx_a9_qemu. And when I try this on qemu using this command
#qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M -net none -kernel sleep01.exe pulseaudio: set_sink_input_volume() failed pulseaudio: Reason: Invalid argument pulseaudio: set_sink_input_mute() failed pulseaudio: Reason: Invalid argument nexus0: <RTEMS Nexus device> # 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. Next I did this "objdump -t usb01.exe | grep bcm" and the output is below. 001be620 l O .rodata 00000018 bcm283x_dwcotg_res 002ecc44 l O .rtemsroset 00000014 __set_nexus_sym_bcm283x_dwcotg0 00000000 l df *ABS* 00000000 bcm283x_dwc_fdt.c 001013a5 l F .text 00000028 bcm283x_dwc_otg_attach 001013cd l F .text 00000034 bcm283x_dwc_otg_probe 0030dc64 l O .bss 00000004 bcm283x_dwc_otg_devclass 003014c8 l O .data 0000000c _bcm283x_dwcotg_depend_on_usb 003014d4 l O .data 0000000c _bcm283x_dwcotg_nexus_depend_on_kernel 00301570 l O .data 0000000c bcm283x_dwcotg_nexus_mod 003014f0 l O .data 00000010 _mod_metadata_md_bcm283x_dwcotg_nexus 00301500 l O .data 00000010 _mod_metadata_md_bcm283x_dwcotg_nexus_on_kernel 00301510 l O .data 00000010 _mod_metadata_md_bcm283x_dwcotg_on_usb 00301538 l O .data 00000018 bcm283x_dwc_otg_methods 00301550 l O .data 00000008 bcm283x_dwcotg_baseclasses 00301558 l O .data 00000018 bcm283x_dwcotg_nexus_driver_mod 002ecb2c l O .rtemsroset 00000004 __set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_on_usb 002ecb30 l O .rtemsroset 00000004 __set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_nexus 002ecb34 l O .rtemsroset 00000004 __set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_nexus_on_kernel 0030c320 l O .rtemsrwset 00000004 __set_sysinit_set_sym__bsd_bcm283x_dwcotg_nexusmodule_sys_init 00000000 l df *ABS* 00000000 bcm2835_mbox.c 001189f9 l F .text 0000000c bcm2835_mbox_dma_cb 00118a05 l F .text 0000007a bcm_mbox_write 00118a81 l F .text 0000008c bcm_mbox_read 00118b0d l F .text 00000060 bcm_mbox_intr 00118b6d l F .text 00000142 bcm_mbox_attach 00118cb1 l F .text 00000034 bcm_mbox_probe 0030ee2c l O .bss 00000004 bcm_mbox_devclass 00305c38 l O .data 00000018 bcm_mbox_driver 00305c50 l O .data 00000028 bcm_mbox_methods 00000000 l df *ABS* 00000000 bcmp.c 001ab165 g F .text 00000004 bcmp 00118f31 g F .text 0000004a bcm2835_mbox_set_power_state 00118ce5 g F .text 0000024c bcm2835_mbox_property 00301520 g O .data 00000018 bcm283x_dwc_otg_driver 003014e0 g O .data 00000010 _bsd_bcm283x_dwcotg_nexusmodule_sys_init This shows that my driver is linked properly with the app testsuit right ? Now for the debugging what are the methods with qemu? As in how to get step by step analysis of the running program ? 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
