Dear Deval Shah,
I found email thread(name: GSoC 2015 RPi USB Support) which is related with
my problem.
https://lists.rtems.org/pipermail/devel/2015-August/012218.html
Because rtems and libbsd version is not matched with last year version,
some description is not matched. but, this email
Dear Deval Shah,
I found reason about "why dwcotg probe & attach function is not called".
Even though DRIVER_MODULE is declared in below, _bsd__start_set_nexus &
_bsd__stop_set_nexus is not initialized.
DRIVER_MODULE(bcm283x_dwcotg, nexus, bcm283x_dwc_otg_driver,
bcm283x_dwc_otg_devclass, 0,
Dear Deval Shah,
I found something.
At this time, I am analyzing libbsd subsystem call procedure.
I added additional information on verbose log file for referencing kernel.h
(in rtems-libbsd/freebsd/sys/sys) and symbol file which is generated by
arm-rtems4.12-nm.
I attached this log
Dear Deval Shah,
I checked my rasberry board. my board is rasberry Pi B+. (It is not RPI2 B+)
I am sorry. I returned to rtems, libbsd version for Pi B+.
Anyway, I guess that both bcm283x_dwc_otg_probe() and
bcm283x_dwc_otg_attach() function should be called.
I don't know how to call
Dear Deval Shah,
Thank you very much for finding my fault.
I changed BSP from rasberrypi to rasberrypi2. also, I changed base address
and irq number accroding to your guide.
I will test this tomorrow.
Additionally, I modifed usb-sysinit.h in below;
#ifdef USB_SYSINIT_INIT
#if
I saw the files which you have attached. I found one quick mistake.
In your nexus-devices.h file "RTEMS_BSD_DRIVER_BCM283X_DWCOTG(0x2098,
17);", base and irq used are wrong. I had corrected the irq in my other
commit. They will be 0x3F98 (since you are using Raspberry pi 2) and 9.
It
---
freebsd/sys/arm/broadcom/bcm2835/bcm283x_dwc_fdt.c | 127
freebsd/sys/dev/usb/controller/dwc_otg_fdt.c | 228 +
freebsd/sys/dev/usb/controller/dwc_otg_fdt.h | 39
libbsd.py | 3 +
libbsd_waf.py
