Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pc-rtems BSP to OSAL #52

Closed
skliper opened this issue Sep 30, 2019 · 11 comments
Closed

Add pc-rtems BSP to OSAL #52

skliper opened this issue Sep 30, 2019 · 11 comments
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Sep 30, 2019

For development under RTEMS it is helpful to have a basic BSP that does not require any special development boards.

The RTEMS project provides this via the "pc686" BSP. This makes it possible to boot and run an RTEMS application on ordinary commodity PC hardware.

This also boots and runs in virtual machines i.e. QEMU which is very desirable for testing.

This ticket will add a "pc-rtems" BSP to OSAL that can be used for this purpose.

@skliper skliper added this to the osal-4.2 milestone Sep 30, 2019
@skliper skliper self-assigned this Sep 30, 2019
@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Imported from trac issue 29. Created by jphickey on 2015-03-18T14:31:39, last modified: 2015-11-20T16:22:16

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jphickey on 2015-03-18 23:01:18:

Pushed branch "trac-29-pc-rtems", commit [changeset:eec4f2f]

This adds a simple RTEMS BSP that runs using the "pc686" BSP from the upstream RTEMS.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jphickey on 2015-04-14 13:11:37:

This changeset has been rebased to the (unapproved) 2015-04-14 baseline

This is due to a dependency on files added/changed as part of that baseline. Attempting to base this change on the official 2015-02-26 OSAL is potentially possible but will result in merge conflicts when putting these back together again.

The new commit is [changeset:22da0be]

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2015-05-18 20:24:10:

Accept, based on the [changeset:cb82d8f] commit. I'm not an RTEMS
expert and can't test it -- but presuming it works, it seems like
a slam-dunk to include it.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jphickey on 2015-07-09 14:41:26:

== REBASED AND UPDATED ==

For the 2015-07-14 CCB review/discussion

This has been rebased to the current OSAL development baseline, commit [changeset:c50630e] reflects the current proposed modifications.

In addition to adding the pc-rtems BSP, this also integrates with the unit testing framework that was approved at the 2015-06-30 CCB so that the unit tests can be executed on RTEMS using this BSP.

This has been tested by running the a pc686 RTEMS build in QEMU and confirmed that all unit tests are passing in this environment.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by acudmore on 2015-07-10 15:14:12:

This will be good, recommend accept

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2015-07-13 13:17:21:

accept

(with the caveat that I'm not an RTEMS expert,
and do not currently have an RTEMS build environment)

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2015-07-13 18:58:39:

accept

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sduran on 2015-07-14 11:51:30:

accept

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jwilmot on 2015-07-14 12:37:39:

Recommend accept.

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by glimes on 2015-07-16 10:23:12:

Included in [changeset:ec67bd4 2015-07-14 development merge],
now present on Babelfish and IPAS-LIB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant