[RTEMS Project] #4593: Add support for renode.io Simulator
RTEMS trac
trac at rtems.org
Fri Feb 16 23:31:02 UTC 2024
#4593: Add support for renode.io Simulator
-------------------------------------------------+-------------------------
Reporter: Joel Sherrill | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Indefinite
Component: tool | Version:
Severity: normal | Resolution:
Keywords: SoC, testing, BSP, simulator, | Blocked By:
medium, small |
Blocking: |
-------------------------------------------------+-------------------------
Changes (by Gedare Bloom):
* keywords: SoC, testing, BSP, simulator, small, medium => SoC, testing,
BSP, simulator, medium, small
Old description:
> [Renode.io] is a simulator geared toward System on Chips and testing. The
> set of supports boards can be viewed in the source code at
> https://github.com/renode/renode/tree/master/platforms. This ticket can
> turn into multiple projects. The first type of project is testing support
> for existing BSPs which have renode.io hardware support.
>
> * Find a board supported by renode.io that has a corresponding BSP.
> * Develop support for the RTEMS Tester to run RTEMS tests on that.
> - Ensure this simulator can be run without a GUI
> * If needed, provide patches for the RTEMS BSP and/or renode.io.
> - It may be necessary to add a BSP variant for renode.io if there are
> small differences that need to be accounted for at BSP build time.
>
> An alternative project is writing a BSP for a renode.io simulation that
> does not yet have an RTEMS BSP.
>
> In either case, once a specific BSP and simulation configuration has been
> identified, a new ticket for that specific work should be created. The
> size of the project depends on how well the BSP works on the simulator at
> the starting point. For example, leon3 is claimed to work very well so
> the focus would be just on RTEMS Tester configuration and support.
>
> This ticket is a general description of multiple projects related to
> renode.io and RTEMS. The size of any specific project for a BSP would
> vary based on what is required to be done. Scoping the effort for
> renode.io support for a specific BSP/hardware combination should be part
> of the project proposal.
>
> Possible Mentors: Alan Cudmore, Gedare Bloom
> Skills: C
> Difficulty: Medium
New description:
[Renode.io] is a simulator geared toward System on Chips and testing. The
set of supports boards can be viewed in the source code at
https://github.com/renode/renode/tree/master/platforms. This ticket can
turn into multiple projects. The first type of project is testing support
for existing BSPs which have renode.io hardware support.
* Find a board supported by renode.io that has a corresponding BSP.
* Develop support for the RTEMS Tester to run RTEMS tests on that.
- Ensure this simulator can be run without a GUI
* If needed, provide patches for the RTEMS BSP and/or renode.io.
- It may be necessary to add a BSP variant for renode.io if there are
small differences that need to be accounted for at BSP build time.
An alternative project is writing a BSP for a renode.io simulation that
does not yet have an RTEMS BSP.
In either case, once a specific BSP and simulation configuration has been
identified, a new ticket for that specific work should be created. The
size of the project depends on how well the BSP works on the simulator at
the starting point. For example, leon3 is claimed to work very well so the
focus would be just on RTEMS Tester configuration and support.
This ticket is a general description of multiple projects related to
renode.io and RTEMS. The size of any specific project for a BSP would vary
based on what is required to be done. Scoping the effort for renode.io
support for a specific BSP/hardware combination should be part of the
project proposal.
Possible Mentors: Alan Cudmore, Gedare Bloom
Skills: C
Difficulty: Medium
Some work was done on this in GSoC'23. See the student's final report to
see what progress has been made, and what remains to be done.
https://www.mazaya.id/blogs/gsoc-final-blog
--
--
Ticket URL: <http://devel.rtems.org/ticket/4593#comment:5>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list