potential GSOC project: Improve the Raspberry Pi BSP

Joel Sherrill joel.sherrill at OARcorp.com
Thu Mar 13 15:26:02 UTC 2014

On 3/13/2014 9:46 AM, Andre Marques wrote:
> Hello,
> I would be very interested in working in this project because I'm
> currently trying to work with Raspberry Pi and RTEMS for my
> undergraduate thesis, so this could be a great followup to that for
> the summer.
> I will need to do some reseach on it before making a proposal (the
> time is also gettting shorter), but will post a proposal draft very soon.

This would be a great area to work. As Alan says, the list is likely too
much for
one student, so it seems likely that the work could be divided for two
working on different parts.

For the Pi Master list, I would like to add the Geert board. That looks
like something
of interest to RTEMS folks.

> --André Marques.
> On 03/13/14 11:23, Alan Cudmore wrote:
>> ( I posted this to the rtems-devel list by mistake, my apologies for
>> the duplicate message )
>> f there are still potential GSOC students out there looking for a
>> project, I would like to offer a potential project to work on:
>> Improving the Raspberry Pi BSP. I would be happy to mentor a student
>> for this project. Below is my description for the task. 
>> Thanks,
>> Alan
>> One of the RTEMS Open Projects is to contribute a BSP or Board
>> Support Package for readily available boards. The Raspberry Pi is
>> probably the most available board at $25 and $35 USD, and there have
>> been over two million of these boards sold. The RTEMS head (4.11)
>> currently has a basic BSP for the Raspberry Pi, supporting the CPU, a
>> single UART, and timer. It is enough to run some basic RTEMS
>> programs, but expanding the BSP to support peripherals will make it
>> much more useful. 
>> For this project, the GSOC student could improve the peripheral
>> support for the Raspberry Pi BSP.
>> The peripherals we need to support (in order of increasing
>> difficulty) include:
>> 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)
>> The entire list is probably too much for a single student to
>> accomplish, so we can adjust the list of work according to what is
>> possible.
>> It may also be a good idea to add support for both models of the
>> Raspberry Pi (256MB and 512MB) and be able to configure the memory
>> map in the BSP to match the boot time split between the CPU and GPU
>> memory. 
>> 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.
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-users

Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20140313/a5c6a113/attachment-0001.html>

More information about the users mailing list