Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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 availabl

Re: Errors while building USB DWC OTG driver

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:

Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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 n

Re: Errors while building USB DWC OTG driver

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 a

Re: Errors while building USB DWC OTG driver

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 thi

Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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 >

Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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 a

Re: Errors while building USB DWC OTG driver

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 Add

Re: Errors while building USB DWC OTG driver

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

Re: Errors while building USB DWC OTG driver

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,

Errors while building USB DWC OTG driver

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-libbsd and cherry-picked Yurii's commits. While building libbsd using waf, I got the following error. --