wiki:Developer/Projects/Open/SimulatorBSPs

BSPs for Simulators

Mentors: Past, Present, and Potential Mentors

Students: Past, Present, and Potential Students

Status: Never-ending.

Introduction: RTEMS can always use more BSPs for simulators.

WARNING: Please ask for detailed information on the particular BSP/simulator combination you are interested in. There are lots of combinations available and the status changes frequently.

See the GNU Tools Testing? project for information on which targets need simulator BSPs to aid in tool testing.

There are a variety of potential projects listed on the Emulator? and SkyEye pages. Some of these involve addressing issues in the simulator itself. Others involve developing BSPs for specific simulators. This is an important area of work since any target that can be tested easily and in an automated fashion on a simulator is always in better shape. Here is a list of BSPs on simulators that are currently thought to be of high interest because they would add significantly to our testing infrastructure:

  • a BSP for the ARM Beagle Board as simulated by QEMU (cheap board)
  • a BSP for a QEMU SuperH target
  • a BSP for a QEMU Coldfire target
    • uc5282 support exists but needs to be merged into QEMU main source
    • make a mc5206 configuration work with our BSP
  • a BSP for SkyEye edp9312 target configured to match the < USD200 Olimex board.

The SkyEye project emulates a number of ARM-, PPC-, MIPS-, and SH4- based platforms, including "test-machines" SkyEye which may be good targets for RTEMS.

Where available please include support for networking and graphics. The RTEMS Project uses simulators for automated testing as well as for manual testing of features like graphics and network application behavior. Full featured simulator BSPs make this much easier. It also provides more BSPs which anyone on the project has access to free with no need for special hardware to be purchased.

JoelSherrill hopes someone will tackle RTEMS support for the ARM A8 and A9 CPU models and the edp9312 as supported by SkyEye. This would benefit RTEMS testing a lot.

Goal: Concise statement of the overall goal of the project. Refine this initial statement to include: project deliverables (code, docs, testing), required/suggested methodology, standards of quality, possible goal extensions beyond the main objective.

Requirements: List the requirements and level of expertise you estimate are required by the developer tackling this project will have to have: Required level of programming language(s), specific areas of RTEMS or tools, level of familiarity with RTEMS, cross-development, GNU/Linux, etx., development/documentation/testing tools, mathematical/algorithmic background, other desirable skills.

Resources: Current RTEMS developers, papers, etc that may help you in this project.

Acknowledgements

  • who helped and did work

Miscellaneous Sections

As the project progresses, you will need to add build instructions, etc and this page will evolve from a project description into a HOWTO.

References

  • TBD

Other sections: If you have more to say about the project that doesn't fit in the proposed sections of this template, feel free to add other sections at will.

Last modified on Feb 17, 2015 at 12:42:58 PM Last modified on Feb 17, 2015, 12:42:58 PM