Re: Errors while building USB DWC OTG driver

[Jan Sommer]

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  
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

Re: Errors while building USB DWC OTG driver

[Sebastian Huber]

Hello Deval,

sorry, I don't have time to look at this at the moment.

--
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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

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: 
#

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 0018 bcm283x_dwcotg_res
002ecc44 l O .rtemsroset 0014 __set_nexus_sym_bcm283x_dwcotg0
 ldf *ABS*  bcm283x_dwc_fdt.c
001013a5 l F .text 0028 bcm283x_dwc_otg_attach
001013cd l F .text 0034 bcm283x_dwc_otg_probe
0030dc64 l O .bss 0004 bcm283x_dwc_otg_devclass
003014c8 l O .data 000c _bcm283x_dwcotg_depend_on_usb
003014d4 l O .data 000c _bcm283x_dwcotg_nexus_depend_on_kernel
00301570 l O .data 000c bcm283x_dwcotg_nexus_mod
003014f0 l O .data 0010 _mod_metadata_md_bcm283x_dwcotg_nexus
00301500 l O .data 0010
_mod_metadata_md_bcm283x_dwcotg_nexus_on_kernel
00301510 l O .data 0010 _mod_metadata_md_bcm283x_dwcotg_on_usb
00301538 l O .data 0018 bcm283x_dwc_otg_methods
00301550 l O .data 0008 bcm283x_dwcotg_baseclasses
00301558 l O .data 0018 bcm283x_dwcotg_nexus_driver_mod
002ecb2c l O .rtemsroset 0004
__set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_on_usb
002ecb30 l O .rtemsroset 0004
__set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_nexus
002ecb34 l O .rtemsroset 0004
__set_modmetadata_set_sym__mod_metadata_md_bcm283x_dwcotg_nexus_on_kernel
0030c320 l O .rtemsrwset 0004
__set_sysinit_set_sym__bsd_bcm283x_dwcotg_nexusmodule_sys_init
 ldf *ABS*  bcm2835_mbox.c
001189f9 l F .text 000c bcm2835_mbox_dma_cb
00118a05 l F .text 007a bcm_mbox_write
00118a81 l F .text 008c bcm_mbox_read
00118b0d l F .text 0060 bcm_mbox_intr
00118b6d l F .text 0142 bcm_mbox_attach
00118cb1 l F .text 0034 bcm_mbox_probe
0030ee2c l O .bss 0004 bcm_mbox_devclass
00305c38 l O .data 0018 bcm_mbox_driver
00305c50 l O .data 0028 bcm_mbox_methods
 ldf *ABS*  bcmp.c
001ab165 g F .text 0004 bcmp
00118f31 g F .text 004a bcm2835_mbox_set_power_state
00118ce5 g F .text 024c bcm2835_mbox_property
00301520 g O .data 0018 bcm283x_dwc_otg_driver
003014e0 g O .data 0010 _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  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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

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

Re: Errors while building USB DWC OTG driver

[Sebastian Huber]

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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

I reverted back to the latest commit of RTEMS. I am getting the same
errors.

On Sun, May 29, 2016 at 11:23 AM, Deval Shah  wrote:

> I followed the libbsd.txt and added bcm 283x driver from freebsd source.
> Now I am getting new errors. This time drivers got compiled which was
> verified using this command.
> > nm `find build -name '*bcm283x_dwc_fdt*.o'`
>
> The error log is as follows.
>
> In file included from ../../rtemsbsd/rtems/rtems-kernel-muteximpl.c:41:0:
> /home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:69:5:
> error: unknown type name 'Thread_queue_Context'
>  Thread_queue_Context *queue_context);
>  ^~~~
> /home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:
> In function 'rtems_bsd_mutex_lock':
> /home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:74:2:
> error: unknown type name 'Thread_queue_Context'
>   Thread_queue_Context queue_context;
>   ^~~~
> /home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:79:49:
> error: request for member 'Lock_context' in something not a structure or
> union
>   _Thread_queue_Acquire(>queue, _context.Lock_context);
>  ^
> /home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:88:50:
> error: request for member 'Lock_context' in something not a structure or
> union
>_Thread_queue_Release(>queue, _context.Lock_context);
>   ^
>
> The log is very big and it is showing that many structures are missing. I
> am unable to figure out why this happened. Because I didn't edit any file
> related to rtems-bsd. Any pointers ?
> Commit for above code changes.
> https://github.com/deval-maker/rtems-libbsd/commit/d90e11ec8e775eed9580e17a6ecaff11fac39931
>
> Thanks,
> Deval Shah
>
>
>
> On Wed, May 25, 2016 7:24 PM, Deval Shah deval.ma...@gmail.com wrote:
>
>>
>> On Wed, May 25, 2016 at 7:12 PM, Sebastian Huber <
>> sebastian.hu...@embedded-brains.de> wrote:
>>
>> On 25/05/16 14:59, Deval Shah wrote:
>>
>>
>> On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber <
>> sebastian.hu...@embedded-brains.de > sebastian.hu...@embedded-brains.de>> wrote:
>>
>> If you get
>>
>> On 25/05/16 10:19, Deval Shah wrote:
>>
>>
>> I got the following result.
>>
>> nm: 'a.out': No such file
>>
>>
>>
>> from
>>
>> nm `find build -name '*bcm283x_dwc_fdt*.o`
>>
>> the this is the first issue you have to resolve. Read the man
>> pages of nm and find to figure out what these commands do.
>>
>> You must have object files for all your driver modules.
>>
>>
>> I understood the problem. Driver for bcm283x is no getting built. Is
>> there any documentation availible for porting a driver to rtems-libbsd ? So
>> that I can verify necessary steps for the code I cherry-picked or if
>> required do the process from scratch.
>>
>>
>> See "How to import code from FreeBSD" in libbsd.txt.
>>
>> Great ! Thanks a lot.
>>
>> Please improve the documentation while you work on this.
>>
>> Surely I will.
>>
>>
>> --
>> 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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

I followed the libbsd.txt and added bcm 283x driver from freebsd source. Now I 
am getting new errors. This time drivers got compiled which was verified
using this command. > nm `find build -name '*bcm283x_dwc_fdt*.o'`
The error log is as follows.
In file included from ../../rtemsbsd/rtems/rtems-kernel-muteximpl.c:41:0: 
/home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:69:5:
error: unknown type name 'Thread_queue_Context' Thread_queue_Context 
*queue_context); ^~~~ 
/home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:
In function 'rtems_bsd_mutex_lock': 
/home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:74:2:
error: unknown type name 'Thread_queue_Context' Thread_queue_Context 
queue_context; ^~~~ 
/home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:79:49:
error: request for member 'Lock_context' in something not a structure or union 
_Thread_queue_Acquire(>queue,  ^ 
/home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/machine/rtems-bsd-muteximpl.h:88:50:
error: request for member 'Lock_context' in something not a structure or union 
_Thread_queue_Release(>queue,  ^
The log is very big and it is showing that many structures are missing. I am
unable to figure out why this happened. Because I didn't edit any file related
to rtems-bsd. Any pointers ? Commit for above code changes.
https://github.com/deval-maker/rtems-libbsd/commit/d90e11ec8e775eed9580e17a6ecaff11fac39931
Thanks, Deval Shah





On Wed, May 25, 2016 7:24 PM, Deval Shah deval.ma...@gmail.com wrote:

On Wed, May 25, 2016 at 7:12 PM, Sebastian Huber < 
sebastian.hu...@embedded-brains.de > wrote:
On 25/05/16 14:59, Deval Shah wrote:

On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber < 
sebastian.hu...@embedded-brains.de > wrote:

If you get

On 25/05/16 10:19, Deval Shah wrote:


I got the following result.

nm: 'a.out': No such file



from

nm `find build -name '*bcm283x_dwc_fdt*.o`

the this is the first issue you have to resolve. Read the man
pages of nm and find to figure out what these commands do.

You must have object files for all your driver modules.


I understood the problem. Driver for bcm283x is no getting built. Is there any
documentation availible for porting a driver to rtems-libbsd ? So that I can
verify necessary steps for the code I cherry-picked or if required do the
process from scratch.

See "How to import code from FreeBSD" in libbsd.txt. Great ! Thanks a lot. 
Please improve the documentation while you work on this. Surely I will.
--
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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

On Wed, May 25, 2016 at 7:12 PM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 25/05/16 14:59, Deval Shah wrote:
>
>>
>> On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber <
>> sebastian.hu...@embedded-brains.de > sebastian.hu...@embedded-brains.de>> wrote:
>>
>> If you get
>>
>> On 25/05/16 10:19, Deval Shah wrote:
>>
>>
>> I got the following result.
>>
>> nm: 'a.out': No such file
>>
>>
>>
>> from
>>
>> nm `find build -name '*bcm283x_dwc_fdt*.o`
>>
>> the this is the first issue you have to resolve. Read the man
>> pages of nm and find to figure out what these commands do.
>>
>> You must have object files for all your driver modules.
>>
>>
>> I understood the problem. Driver for bcm283x is no getting built. Is
>> there any documentation availible for porting a driver to rtems-libbsd ? So
>> that I can verify necessary steps for the code I cherry-picked or if
>> required do the process from scratch.
>>
>
> See "How to import code from FreeBSD" in libbsd.txt.

Great ! Thanks a lot.

> Please improve the documentation while you work on this.

Surely I will.

>
> --
> 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

Re: Errors while building USB DWC OTG driver

[Sebastian Huber]

On 25/05/16 14:59, Deval Shah wrote:


On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber 
> wrote:


If you get

On 25/05/16 10:19, Deval Shah wrote:


I got the following result.

nm: 'a.out': No such file



from

nm `find build -name '*bcm283x_dwc_fdt*.o`

the this is the first issue you have to resolve. Read the man
pages of nm and find to figure out what these commands do.

You must have object files for all your driver modules.


I understood the problem. Driver for bcm283x is no getting built. Is 
there any documentation availible for porting a driver to rtems-libbsd 
? So that I can verify necessary steps for the code I cherry-picked or 
if required do the process from scratch.


See "How to import code from FreeBSD" in libbsd.txt. Please improve the 
documentation while you work on this.


--
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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

On Wed, May 25, 2016 at 3:07 PM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> If you get
>
> On 25/05/16 10:19, Deval Shah wrote:
>
>>
>> I got the following result.
>>
>> nm: 'a.out': No such file
>>
>>
>>
> from
>
> nm `find build -name '*bcm283x_dwc_fdt*.o`
>
> the this is the first issue you have to resolve. Read the man pages of nm
> and find to figure out what these commands do.
>
> You must have object files for all your driver modules.
>
>
I understood the problem. Driver for bcm283x is no getting built. Is there
any documentation availible for porting a driver to rtems-libbsd ? So that
I can verify necessary steps for the code I cherry-picked or if required do
the process from scratch.


> --
> 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

Re: Errors while building USB DWC OTG driver

[Sebastian Huber]

If you get

On 25/05/16 10:19, Deval Shah wrote:


I got the following result.

nm: 'a.out': No such file




from

nm `find build -name '*bcm283x_dwc_fdt*.o`

the this is the first issue you have to resolve. Read the man pages of 
nm and find to figure out what these commands do.


You must have object files for all your driver modules.

--
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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

This might help for debugging.

1. Code on which I am building raspberrypi BSP
https://github.com/deval-maker/rtems-libbsd
2. Testsuits whcih contains #include
 or #include
 are having this redefination error.

On Wed, May 25, 2016 at 1:49 PM, Deval Shah  wrote:

> I got the following result.
>
> nm: 'a.out': No such file
>
> I searched a bit. And got to know that DWG OTG was already ported to RTEMS
> by this commit
> https://github.com/RTEMS/rtems-libbsd/commit/ba446132d4e9efbc1ffd7f4dc4fbfde7f531b740
> .
>
>
> So when I cherry-picked, somewhere, some devices or resources are getting
> redefined.
>
> Any suggestion on how to proceed ?
>
> On Wed, May 25, 2016 at 1:17 PM, Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
>
>>
>>
>> On 25/05/16 09:12, Deval Shah wrote:
>>
>>> That is here in this commit
>>> https://github.com/gtament/rtems-libbsd/commit/173af003ef084acd2391269e3dcabb0954053289.
>>>
>>>
>>
>>
>> I don't see an obvious error. What gives an
>>
>> nm `find build -name '*bcm283x_dwc_fdt*.o`
>>
>> ?
>>
>>
>> --
>> 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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

I got the following result.

nm: 'a.out': No such file

I searched a bit. And got to know that DWG OTG was already ported to RTEMS
by this commit
https://github.com/RTEMS/rtems-libbsd/commit/ba446132d4e9efbc1ffd7f4dc4fbfde7f531b740
.


So when I cherry-picked, somewhere, some devices or resources are getting
redefined.

Any suggestion on how to proceed ?

On Wed, May 25, 2016 at 1:17 PM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

>
>
> On 25/05/16 09:12, Deval Shah wrote:
>
>> That is here in this commit
>> https://github.com/gtament/rtems-libbsd/commit/173af003ef084acd2391269e3dcabb0954053289.
>>
>>
>
>
> I don't see an obvious error. What gives an
>
> nm `find build -name '*bcm283x_dwc_fdt*.o`
>
> ?
>
>
> --
> 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

Re: Errors while building USB DWC OTG driver

[Sebastian Huber]

On 25/05/16 09:12, Deval Shah wrote:
That is here in this commit 
https://github.com/gtament/rtems-libbsd/commit/173af003ef084acd2391269e3dcabb0954053289. 



I don't see an obvious error. What gives an

nm `find build -name '*bcm283x_dwc_fdt*.o`

?

--
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

Re: Errors while building USB DWC OTG driver

[Deval Shah]

That is here in this commit
https://github.com/gtament/rtems-libbsd/commit/173af003ef084acd2391269e3dcabb0954053289
.

On Wed, May 25, 2016 at 10:58 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> Hello Deval,
>
> where is this DWC OTG driver code? The driver must have the right
> DRIVER_MODULE() and MODULE_DEPEND() definitions.
>
> On 24/05/16 20:04, Deval Shah wrote:
>
>> Hello,
>>
>> Currently, I am working on porting USB DWC OTG driver on Raspberry Pi.
>> Last year Yurii Shevtsov worked on the same. So, I forked the latest
>> rtems-libbsdand cherry-picked Yurii's commits. While building libbsdusing
>> waf, I got the following error.
>>
>>
>>
>> ---
>> testsuite/arphole/test_main.c.17.o:(.rtemsroset.bsd.nexus.content+0x10):
>> undefined reference to `_bsd_bcm283x_dwcotg_nexusmodule_sys_init'
>> collect2: error: ld returned 1 exit status
>> ...
>>
>> ---
>>
>> This error is observed in all the testsuits which are related to
>> networing. Then according to this wiki
>> https://devel.rtems.org/wiki/GSoC/2015/RaspberryPiUSBSupport, I added
>> following lines to those testsuits.
>>
>> -- #include 
>> -- SYSINIT_NEED_USB_CORE;
>> -- SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus);
>>
>> I get the following redefiation error this time.
>>
>> --
>> In file included from
>> /home/gadgetman/development/rtems/rtems-libbsd/testsuite/include/rtems/bsd/test/default-network-init.h:295:0,
>>  from ../../testsuite/arphole/test_main.c:118:
>> /home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/bsp/nexus-devices.h:154:40:
>> error: redefinition of 'bcm283x_dwcotg_res'
>>  static const rtems_bsd_device_resource bcm283x_dwcotg_res[] = {
>>   ^~
>> In file included from ../../testsuite/arphole/test_main.c:57:0:
>> /home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/bsp/nexus-devices.h:154:40:
>> note: previous definition of 'bcm283x_dwcotg_res' was here
>>  static const rtems_bsd_device_resource bcm283x_dwcotg_res[] = {
>>   ^~
>> ...
>>
>> --
>>
>> Also, looks like the error is only in the testsuits. USB drivers are
>> compiled properly. What is another way to test the port ? Is there any
>> other testsuit available ? Are there any other standard methods to evaluate
>> this ?
>>
>> Thanks in advance,
>> Deval Shah
>>
>>
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>
> --
> 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

Re: Errors while building USB DWC OTG driver

[Sebastian Huber]

Hello Deval,

where is this DWC OTG driver code? The driver must have the right 
DRIVER_MODULE() and MODULE_DEPEND() definitions.


On 24/05/16 20:04, Deval Shah wrote:

Hello,

Currently, I am working on porting USB DWC OTG driver on Raspberry Pi. 
Last year Yurii Shevtsov worked on the same. So, I forked the latest 
rtems-libbsdand cherry-picked Yurii's commits. While building 
libbsdusing waf, I got the following error.


---
testsuite/arphole/test_main.c.17.o:(.rtemsroset.bsd.nexus.content+0x10): 
undefined reference to `_bsd_bcm283x_dwcotg_nexusmodule_sys_init'

collect2: error: ld returned 1 exit status
...
---

This error is observed in all the testsuits which are related to 
networing. Then according to this wiki 
https://devel.rtems.org/wiki/GSoC/2015/RaspberryPiUSBSupport, I added 
 following lines to those testsuits.


-- #include 
-- SYSINIT_NEED_USB_CORE;
-- SYSINIT_DRIVER_REFERENCE(bcm283x_dwcotg, nexus);

I get the following redefiation error this time.
--
In file included from 
/home/gadgetman/development/rtems/rtems-libbsd/testsuite/include/rtems/bsd/test/default-network-init.h:295:0,

 from ../../testsuite/arphole/test_main.c:118:
/home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/bsp/nexus-devices.h:154:40: 
error: redefinition of 'bcm283x_dwcotg_res'

 static const rtems_bsd_device_resource bcm283x_dwcotg_res[] = {
  ^~
In file included from ../../testsuite/arphole/test_main.c:57:0:
/home/gadgetman/development/rtems/rtems-libbsd/rtemsbsd/include/bsp/nexus-devices.h:154:40: 
note: previous definition of 'bcm283x_dwcotg_res' was here

 static const rtems_bsd_device_resource bcm283x_dwcotg_res[] = {
  ^~
...
--

Also, looks like the error is only in the testsuits. USB drivers are 
compiled properly. What is another way to test the port ? Is there any 
other testsuit available ? Are there any other standard methods to 
evaluate this ?


Thanks in advance,
Deval Shah



___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


--
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