Errors while building USB DWC OTG driver
Deval Shah
deval.maker at gmail.com
Tue May 31 17:32:30 UTC 2016
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 ?
Thanks,
Deval Shah
On Sun, May 29, 2016 at 12:00 PM, Deval Shah <deval.maker at gmail.com> wrote:
> 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 <deval.maker at gmail.com>
> 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(&m->queue, &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(&m->queue, &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.maker at gmail.com wrote:
>>
>>>
>>> On Wed, May 25, 2016 at 7:12 PM, Sebastian Huber <
>>> sebastian.huber at 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.huber at embedded-brains.de <mailto:
>>> sebastian.huber at 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.huber at embedded-brains.de
>>> PGP : Public key available on request.
>>>
>>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>>>
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160531/48ed68e6/attachment-0002.html>
More information about the devel
mailing list