Great help, thanks for your infomation. I've set up the devel environment , qemu simulation and I'm waiting for a screen or usb-ttl cable for on board testing. I'll soon report what I've got in order to get myself "aboard" :)
> 在 2015年3月10日，11:30，Pavel Pisa <ppisa4li...@pikron.com> 写道： > > Hello all, > > I have put my hands to RPi, due to some consultations/support > contract from other company which used RPi for data acquisition > in industrial application and failed in serious problems > with SD cards reliability. Other reason to invest my time > is that it is common board between students and I want to support > them by some ideas and knowledge for more advanced play with RPi. > > I have presentation at students/Linux enthusiast conference > this weekend and there are my scratchpad like slides (fortunately > in English) > > http://cmp.felk.cvut.cz/~pisa/installfest/rpi_overlay_and_rt.pdf > > The important think is, that U-boot support RPi now and can > load kernel (I expect that RTEMS as well) over PXE/TFTP. > This could simplify development a much. I have even Linux FS > root mounted over NFS from my computer so development is really > easy. > > The boot process description and links to additional information > starts from slide 13. > > The other inspiration is servo control demo application which > does require minimal wirewrapped HW. It suns quite nice > on fully-preemptive Linux but it could work even better on RTEMS > due no system call and memory context switching overhead. > > Best wishes, > > Pavel > > >> On Thursday 05 of March 2015 15:28:50 Gedare Bloom wrote: >> Hello Yang Qiao, >> >> There is the future work listed in that page, and there are some other >> project ideas for raspberry pi. There also could be the opportunity to >> support the raspberry pi 2. >> >> The original list of open Raspberry Pi projects were: >> Peripherals we need to support (in order of increasing difficulty): >> 1. GPIO (This has been done by one user, but is not integrated) >> 2. I2C Bus >> 3. SPI Bus >> 4. Secure Digital card read and write support (using the SPI bus) >> 5. Graphics / RTEMS Framebuffer Support (I have a graphics demo >> working in an RTEMS task) >> 6. USB Device support >> 7. HDMI/Graphics console (Requires framebuffer support and USB or GPIO >> connected keyboard device) >> 8. Ethernet network support (Requires USB support) >> >> Finally, in order to do some of this coding, it may be necessary to >> come up with a more efficient way to load and debug code on the >> Raspberry Pi. Options include using U-boot or connecting a JTAG debug >> device to load code. >> >> I don't know the status of all of the above, but I think there is >> still a lot to do in #5-8. >> >> Gedare >> >>> On Thu, Mar 5, 2015 at 4:28 AM, QIAO YANG <yangqiao0...@me.com> wrote: >>> Hello , >>> >>> I' a 3rd year chinese student studying software engineering (real-time >>> system and embedded system) in France. I've found the GSOC2015 idea >>> 'Raspberry Pi BSP ' very attractive and I would like to know more about >>> it to prepare my proposal. >>> >>> Since the wiki page hasn't a concrete introduction yet, I would like to >>> know a bit more about it in order to make my first step to try out the >>> existing codes and prepare the proposal. >>> >>> After having read the wiki of the same project in GSOC2013, I guess the >>> BSP is a library which contains the apis of communication protocols to >>> manipulate the peripherals. So maybe our goal is completing the "futur >>> works" described on GSOC 2013's wiki >>> https://devel.rtems.org/wiki/GSoC/2013/Raspberry_Pi_BSP_Peripherals, >>> that : add support to different model of RPI etc... or something else? >>> >>> Any references or instructions would be greatly helpful. >>> >>> Looking forward to hearing from you soon :) >>> >>> Best regards >>> >>> ------------------------------------------------------- >>> YANG Qiao >>> >>> Université de Tchnologie de Compiègne >>> >>> Génie Informatique >>> >>> >>> _______________________________________________ >>> 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
