GSOC2015 idea Raspberry Pi BSP

Joel Sherrill joel.sherrill at oarcorp.com
Thu Mar 5 17:19:31 UTC 2015



On 3/5/2015 10:55 AM, Alan Cudmore wrote:
> On 3/5/2015 11:46 AM, Joel Sherrill wrote:
>> On 3/5/2015 10:40 AM, Alan Cudmore wrote:
>>> The list below is still pretty good.
>>> Items 1 - 3 were done by Andre last summer, but we still don't have them
>>> in the git repository. The RTEMS I2C API has changed and we were going
>>> to try to move the I2C implementation to the new Linux based API.
>> So the API needs to change on I2C. What else remains to do to merge Andre's
>> work? Is this the first step of a 2015 project?
>>
>> I am guessing that USB and then the NIC are high on the list. Does FreeBSD
>> support the Pi? That would make it easier. This assumes the new TCP/IP
>> stack.
> FreeBSD does support the Pi. I was thinking that the FreeBSD USB and 
> network stack may be the way to accomplish this.
Then I see the first two items on a Pi V1 Project are:

(1) update/merge GSOC 2014 code
(2) USB support
(3) Network support
(4) ?

Does that sound right?
>> FWIW we need to make sure Andre's final write up is linked to from GSOC 2014
>> and the next Pi activities get their own project page for 2015.
>>> I still think that having complete Raspberry Pi support would be great
>>> for RTEMS, and RTOS education in general.  The Pi has worldwide
>>> availability, and is probably the least expensive target board that can
>>> run RTEMS.
>>> Having a non-simulated RTEMS board that has network, file system, and
>>> now even SMP support for $35 USD would be amazing.
>> +1
>>
>> I haven't looked much. Does it have JTAG support even via soldering?
> It is possible to get JTAG support through the GPIO pins. I started down 
> this path, but did not have the time to complete it.
OK.
>>> Now the new Pi2 with a Quad Core ARM7 and the HAT add on board standard,
>>> the Pi is even better for real applications such as this Navigation board:
>>> http://www.emlid.com/
>>>
>> Is the SoC documentation available?
> I don't think the SoC documentation is available yet. From what I 
> understand, some people are getting bare metal code running on the Pi2 
> by changing the base address of the peripheral registers.
> It may be as simple as the new peripheral register address and 
> optimization flags for the ARM7.
If the documentation is not available, then it isn't a GSoC project. I
put the Edison
in this category for GSoC because docs are NDA and JTAG is only available
with an expensive device.

If the docs become available, then maybe it is (4). You (or someone) may be
able to tinker with Internet notes like I did with the Edison and see
how far
you can get. But it wasn't enough to get a real BSP completed.
>> Would it be better to complete the Pi or start a Pi v2 BSP? The last I
>> knew the
>> Pi V2 SoC documentation wasn't public yet so it isn't an option yet.
>>
>> On general principle, I like the idea of finishing the Pi V1 BSP. If info is
>> available and we can support it, a project to complete V1 and start V2
>> BSP is a good one.
> I think finishing the Pi 1 BSP is a good idea as well. They will 
> continue to sell the Pi 1 ( Model B+ and A+ ) as long as there is 
> demand. But hopefully, the Pi2 will just be a BSP configuration variant.
Yep. :)
> Alan
>
>>> Alan
>>>
>>> On 3/5/2015 9:28 AM, 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 <yangqiao0505 at 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 at rtems.org
>>>>> http://lists.rtems.org/mailman/listinfo/devel
>>> _______________________________________________
>>> devel mailing list
>>> devel at rtems.org
>>> http://lists.rtems.org/mailman/listinfo/devel

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



More information about the devel mailing list