Changes between Version 1 and Version 2 of Developer/Projects/Open/ImproveBeagleBSP


Ignore:
Timestamp:
Mar 4, 2015, 2:59:47 PM (5 years ago)
Author:
Ben Gras
Comment:

full GSOC getting started instructions, better hierarchy, fix TOC

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Open/ImproveBeagleBSP

    v1 v2  
    33
    44
    5 [[TOC(Projects/GSoC/Beagle, depth=2)]]
     5[[TOC(Developer/Projects/Open/ImproveBeagleBSP, depth=2)]]
    66
    77
     
    1212= Introduction =
    1313
    14 RTEMS has a BSP that supports beagleboard, beagleboard xm, beaglebone (original, white) and beaglebone black targets. The BSP is in RTEMS mainline. The hardware support is rudimentary. This page lists ideas for improvement of that BSP.
     14RTEMS has a BSP that supports beagleboard, beagleboard xm, beaglebone (original, white) and beaglebone black targets. The BSP is in RTEMS mainline.
    1515
    16 They are listed in no particular order.
    1716
    18 = Booting without uboot =
     17= Getting started as a GSOC student =
     18
     19If you are interested in working on this BSP as a GSOC project, there are a few basics you should do immediately, if possible before even asking about the project, to show that you are up to speed with the basics of running RTEMS and this BSP in particular.
     20
     21== You'll need the hardware ==
     22
     23To test your changes, you will need the relevant hardware. You will also need a way to see the RTEMS serial console i/o. So, you will need one of the following, in descending order of advisability if you have the freedom to choose a model:
     24
     25  * Beaglebone ("white") - this board has everything self-contained (power, jtag and serial over a single usb cable) so is the ideal board to buy if you have to choose
     26  * Beaglebone black - this will need a TTL-serial to USB converter cable, e.g. [https://www.tigal.com/product/3466 USB-TTL FTDI Cable 3.3V], and jtag is harder to access so quite limiting compared to the white.
     27  * Beagleboard XM + serial cable (serial to usb is most convenient - the ones with the FTDI chip work well)
     28  * Beagleboard + serial cable
     29
     30== Also build the emulator ==
     31
     32There is a Beagleboard XM emulator. Run the BSP in that for
     33
     34   * fast iteration, convenient debugging
     35   * testing whether your changes might break the xm and/or the emulator
     36
     37== Build & run the BSP ==
     38
     39Build & run the BSP (e.g. using the test set) on whatever you hardware you have and on the bbxm emulator.
     40
     41See [http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html this blog post] for full instructions in building & running the bsp on hardware and in the emulator.
     42
     43== Make a change in RTEMS ==
     44
     45To show that you're up to speed with rebuilding RTEMS, make a change. One valuable suggestion is to run the test set and debug any of the failing tests, either on the emulator or on real hardware. One thing to keep in mind is that a failing test on the emualtor could be an imperfection of the emulator.
     46
     47= Ideas to Improve the BSP =
     48
     49The hardware support is rudimentary. This section lists ideas for improvement of that BSP.
     50
     51They are listed in no particular order. The biggest factor is motivation - are you excited to take on the task?
     52
     53== Booting without uboot ==
    1954
    2055The BSP needs some sort of bootloader to get the app loaded. Currently the system to do all the work for the user uses uboot. GPL3 is a problem and so a BSD-licensed alternative to do the same thing would be better.
    2156
    22 = Upstreaming RSB & rtems-tools changes =
     57== Upstreaming RSB & rtems-tools changes ==
    2358
    2459The BSP itself is neatly upstreamed to mainline. There are some changes in rtems-tools and the RSB that are not neatly in mainline and that is needed. Coordination with Chris Johns is needed here.
    2560
    26 = Peripheral support =
     61== Peripheral support ==
    2762
    2863There are quite a few missing peripherals. In no particular order
     
    3671  * CAN
    3772
    38 = Fix failing tests & automatically run tests on future commits =
     73== Fix failing tests & automatically run tests on future commits ==
    3974
    4075On Qemu, most tests pass but not all. On the hardware (running using JTAG), most tests pass but not all. The reason for them to fail should be figured out (might be a qemu limitation in the 1st case). Once the tests are nailed down, coordination with Amar would be good to run these tests automatically in the qemu linaro so future commits won't break the BSP (or at least, it will be flagged immediately).