The Pi 1/B+ would be a good model to start the USB development with. I have actually not built the BSD lib myself. But I think this is the place to start: https://git.rtems.org/rtems-libbsd/tree/libbsd.txt https://git.rtems.org/rtems-libbsd/tree/README.waf Looks like the arm/realview_pbx_a9_qemu BSP is the one use.
I have run some of the SMP examples on qemu with the arm/realview_pbx_a9_qemu_smp BSP and it worked well for me. Alan On Wed, Mar 23, 2016 at 9:03 AM, Deval Shah <deval.ma...@gmail.com> wrote: > On Tue, Mar 22, 2016 at 10:04 PM, Alan Cudmore <alan.cudm...@gmail.com> > wrote: > > Hi Deval, > > Your proposal looks good. I would suggest adding a step where you build a > > known BSP with BSD lib support. It will help you become familiar with the > > development process. > > Thanks for the suggestion, Alan. I will be adding this to my proposal. > Also, which BSP would you recommend that I pick up ? Is there any list > of currently added BSPs from which I can choose? > > > You should also address which Raspberry Pi model you will support. Now > that > > there are so many Raspberry Pi models, it might make the project more > > complicated: > > Original raspberry Pi Model A & A+: a single built in USB port in the > > BCM2835 CPU. No ethernet or USB hub. > > Raspberry Pi Model B & B+: USB hub and Ethernet in LAN9512 chip. > > Raspberry Pi 2 Model B: USB hub and Ethernet in LAN9514 chip. > > Raspberry Pi 3 Model B: I would not worry about this one yet. > > Raspberry Pi Zero: A single USB OTG port , no ethernet or USB hub. > > > > I would pick one of them and get it working before seeing if another > model > > could be supported. > > > > If the Raspberry Pi 1/B+ and 2/B Hubs are functionally the same ( LAN9512 > > vs. LAN9514 ), this would support the widest range of devices out there. > > > I was also thinking for that. I have a Raspberry PI 1/B+ and a > majority of users have either 1/B+ or 2/B. Probably we can start with > 1/B+ and then enable the other models. > > > If you have time, I would love to see USB support for the BCM2835 on the > Pi > > Model A+ and especially the Pi Zero. > > Sure, I had left some buffer time in my proposal, probably if things > goes as per plan that time can be used for USB support for the > BCM2835. > > > > > Thanks, > > Alan > > > > > > On Tue, Mar 22, 2016 at 8:52 AM, Deval Shah <deval.ma...@gmail.com> > wrote: > >> > >> Hello, > >> > >> I have updated my draft proposal and shared on the tracking page. I'm > >> sharing it here as well. https://goo.gl/QQiAf6 > >> > >> Sorry, I was busy with my Mid-Semester exams, could not update earlier. > >> > >> Since this is a draft proposal, it may not be completely polished yet. > >> I'd appreciate any comments on it, especially regarding the project > >> description > >> and timeline. > >> > >> Thank you. > >> > >> Regards, > >> Deval Shah > >> > >> On Fri, Mar 11, 2016 at 11:02 PM, Deval Shah <deval.ma...@gmail.com> > >> wrote: > >> > On Fri, Mar 11, 2016 at 8:33 PM, Gedare Bloom <ged...@gwu.edu> wrote: > >> >> On Fri, Mar 11, 2016 at 8:19 AM, Deval Shah <deval.ma...@gmail.com> > >> >> wrote: > >> >>> Hello everyone! > >> >>> > >> >>> I went through the links and blogs of the SD card and USB/Ethernet > >> >>> project for Raspberry PI. I would like to work for the USB/Ethernet > >> >>> support project. > >> >>> > >> >>> I have prepared a draft of the timeline as follows: > >> >>> > >> >>> Acceptance Waiting Period: > >> >>> Understanding previous year's GSOC work > >> >>> > >> >>> First Half: > >> >>> completing USB support for RPI > >> >>> Testing USB and add drivers for HIDs like Mouse and Keyboard > >> >>> > >> >>> Second Half: > >> >>> Adding Ethernet Support > >> >>> Testing (ARP, PING, DHCP, FTP, TFTP) > >> >>> Adding support for lwIP (since it is already ported to BBB, this > >> >>> should not take more time) > >> >>> > >> >> Timeline seems good. Is the USB support available from freebsd for > the > >> >> libbsd codebase? > >> > > >> > Yes. libbsd has support for USB. > >> > Last year issues were in porting the driver ( > >> > http://gtament-rtems.blogspot.in/2015/06/my-progress-report.html ). > >> > > >> >>> If we have wifi support in RTEMS, can support of a USB wifi module > be > >> >>> added to the project? > >> >>> > >> >> I haven't seen any one using wifi yet. > >> >> > >> >>> I'd really appreciate any feedback on my deliverables, especially > >> >>> regarding the feasibility of doing it in this time frame. If there > is > >> >>> anything I may have missed out or anything else I should consider > as a > >> >>> part of this, I'd be really glad if someone could point that out, so > >> >>> as to increase my chances of selection. > >> >>> > >> >>> A quick question: How can I add my name to the tracking list @ > >> >>> https://devel.rtems.org/wiki/GSoC/2016 ? > >> >>> > >> >> You need to register an account to edit the page through link at the > >> >> bottom. > >> >> Okay, Thank you. > >> >>> Deval Shah > >> >>> > >> >>> On Tue, Mar 1, 2016 at 3:07 AM, André Marques > >> >>> <andre.lousa.marq...@gmail.com> wrote: > >> >>>> Hello Jan and Deval, > >> >>>> > >> >>>> Às 20:24 de 29-02-2016, Jan Sommer escreveu: > >> >>>>> > >> >>>>> Hi, > >> >>>>> > >> >>>>> If you take a look here: > >> >>>>> > >> >>>>> > https://devel.rtems.org/wiki/GSoC/2015#StudentsSummerofCodeTrackingTable > you > >> >>>>> can find the links to the reports and repositories of the previous > >> >>>>> GSoC. > >> >>>>> Yurii Shevtsov was doing the work on the Ethernet/USB part for the > >> >>>>> pi. > >> >>>>> Andre Marques worked on the SPI and SD-Card driver. > >> >>>> > >> >>>> > >> >>>> I have updated a bit the Raspberry Open Projects page with the > state > >> >>>> of the > >> >>>> low level peripherals project, and provided links to the state of > >> >>>> each of > >> >>>> the other projects (the wiki pages of the students working on them > >> >>>> last > >> >>>> year, which also include their blogs and githubs). > >> >>>> > >> >>>> > >> >>>> > https://devel.rtems.org/wiki/Developer/Projects/Open/ImproveRaspberryPiBSP > >> >>>> > >> >>>> The other 3 raspberry projects I do not know exactly their current > >> >>>> state, > >> >>>> but they already have some work done (just not in the RTEMS tree > >> >>>> yet). > >> >>>> > >> >>>> It seems that only GPIO, I2C and SPI were merged last year. > >> >>>> > >> >>>>> Cheers, > >> >>>>> > >> >>>>> Jan > >> >>>>> > >> >>>>> Am Tuesday 01 March 2016, 01:15:24 schrieb Deval Shah: > >> >>>>>> > >> >>>>>> It looks like there are more useful things in pipeline before > >> >>>>>> raspberry > >> >>>>>> pi > >> >>>>>> cam support. > >> >>>>>> > >> >>>>>> Can anybody give me pointers/links to refer for porting ethernet > >> >>>>>> support > >> >>>>>> and SD card support? > >> >>>> > >> >>>> > >> >>>> For the last year efforts on the SD card support you can refer to: > >> >>>> > >> >>>> > >> >>>> > https://devel.rtems.org/wiki/GSoC/2015/RaspberryPi_peripherals_and_SD_card#SDcardsupport > >> >>>> > >> >>>> > >> >>>>>> > >> >>>>>> On Thursday 18 February 2016, soja-li...@aries.uberspace.de < > >> >>>>>> soja-li...@aries.uberspace.de> wrote: > >> >>>>>> > >> >>>>>>> Am 2016-02-18 01:26, schrieb Joel Sherrill: > >> >>>>>>> > >> >>>>>>>> On Feb 17, 2016 6:17 PM, "André Marques" > >> >>>>>>>> <andre.lousa.marq...@gmail.com> > >> >>>>>>>> wrote: > >> >>>>>>>> > >> >>>>>>> [...] > >> >>>>>>> > >> >>>>>>>> Was i2c fully delivered for the new driver framework? I don't > >> >>>>>>>> recall > >> >>>>>>>>> > >> >>>>>>>>> off-hand. > >> >>>>>>>>> > >> >>>>>>>>> Yes the i2c driver for the Pi uses the new (linux-based) i2c > >> >>>>>>>>> framework. > >> >>>>>>>>> > >> >>>>>>>> 10-bit addressing is untested because I had no compatible slave > >> >>>>>>>> device. > >> >>>>>>>> > >> >>>>>>>>> A detailed report of my last GSOC can be found here: > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> > https://devel.rtems.org/wiki/GSoC/2015/RaspberryPi_peripherals_and_SD_card > >> >>>>>>>>> > >> >>>>>>>>> SD card support was started but not completed last year, so it > >> >>>>>>>>> may be > >> >>>>>>>>> > >> >>>>>>>> included on a potential Raspberry project. I can help with that > >> >>>>>>>> if > >> >>>>>>>> needed. > >> >>>>>>>> > >> >>>>>>>> Andres.. Thanks for speaking up. Can you update the project > page > >> >>>>>>>> and > >> >>>>>>>> link > >> >>>>>>>> to your blog? > >> >>>>>>>> > >> >>>>>>>> What else do you think needs find on the Pi and Pi2? > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>> Last year there was a GSoC to add ethernet support for the > >> >>>>>>> raspberry pi > >> >>>>>>> via rtems-libbsd, but I think it was never finished. > >> >>>>>>> Maybe that could be started again? > >> >>>>>>> > >> >>>>>>> I haven't researched it yet to know if it is feasible but I am > >> >>>>>>> curious > >> >>>>>>> if > >> >>>>>>>> > >> >>>>>>>> the Arduino HW libraries have a clean porting layer which could > >> >>>>>>>> provide > >> >>>>>>>> support for a lot of i2c devices. Is this a wikd goose chase or > >> >>>>>>>> of > >> >>>>>>>> potential value? > >> >>>>>>>> > >> >>>>>>>> > >> >>>>>>> Sounds like an interesting idea, but isn't Arduino written in > C++? > >> >>>>>>> > >> >>>>>>> Best regards, > >> >>>>>>> > >> >>>>>>> Jan > >> >>>>>>> > >> >>>>>>> > >> >>>>>>>>> I very much look forward for any pointers on this. > >> >>>>>>>>>>> > >> >>>>>>>>>>> I am eager to work for RTEMS organization because I believe > my > >> >>>>>>>>>>> skill > >> >>>>>>>>>>> set is best suited for this. > >> >>>>>>>>>>> > >> >>>>>>>>>>> Thanking you, > >> >>>>>>>>>>> Deval Shah > >> >>>>>>>>>>> > >> >>>>>>>>>>> _______________________________________________ > >> >>>>>>>>>>> devel mailing list > >> >>>>>>>>>>> devel@rtems.org > >> >>>>>>>>>>> http://lists.rtems.org/mailman/listinfo/devel > >> >>>>>>>>>>> > >> >>>>>>>>> --André Marques > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> _______________________________________________ > >> >>>>>>>>> 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 > >> >>>>>>>> > >> >>>>>>> _______________________________________________ > >> >>>>>>> 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 > >> >>>> > >> >>>> > >> >>>> --André Marques > >> >>>> > >> _______________________________________________ > >> 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