GSOC2015 idea Raspberry Pi BSP

Fri Mar 6 01:08:34 UTC 2015

On March 5, 2015 3:18:11 PM CST, "桥 杨" <yangqiao0505 at me.com> wrote:
>With official documents and elinux wiki , we can find lots of details
>of different RPI model. Including chip datasheets , layout, and pin
>definitions etc...

I think we can probe and dynamically adjust for many differences. This happens on the Motorola/Emerson VMRLE and CompactPCI cards.

>
>For the moment, I've got a B and B+. So I think maybe I can start by
>building RTEMS and load it with uboot, check out the code for gpio and
>i2c , and maybe adapt the i2c driver with the new library.

That's great. 

>I'll keep you updated if I've got stucked or made any progress :) .
>
>Thanks for all helps!!
>
>> 在 2015年3月5日，18:36，André Marques <andre.lousa.marques at gmail.com> 写道：
>> 
>>> On 05-03-2015 16:46, 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 have been working on and off Pavel's interrupt handling suggestions
>(https://lists.rtems.org/pipermail/devel/2014-October/008911.html) for
>the GPIO code, and soon enough will post a patch with those.
>> 
>> I2C support is done but the end of GSOC coincided with the release of
>the new I2C API, so it is on hold until it is ported to the new API.
>> 
>> As far as SPI is concerned it was not merged because we were trying
>to merge the three at the same time.
>> 
>>> 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.
>>> 
>>> 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?
>>>> 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?
>> 
>> As far as peripherals go there should not be a difference between the
>Pi 1 and 2 (from what I could understand). It may be just a matter of
>changing register addresses, but I have no Pi 2 to check that yet.
>> 
>>> 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.
>>> 
>>>> 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