Fetching latest commit…
Reference System Virtual Platform
Software Interface Standard
Modern configurable System-on-Chip and Field Programmable Gate Array devices, are a blank slate for designers to draw on. However, most systems require several common resources and peripherals in order to present the user with a usable "System Platform" upon which to base an application.
The Reference System Virtual Platforms (RSVPs) are designed to provide useful baseline systems with commonly required resources and peripherals, as well as a vendor neutral, portable API to access and control those resources and peripherals.
While most semiconductor vendors will provide a baseline "driver" library for their parts, or a configuation tool within their IDE (Integrated Development Environment) to select and configure IP blocks, these tend to be unique, vendor specific, and/or proprietary in nature. It can often take a significant amount of work to port an embedded application from one SOC/Microprocessor family to another.
RSVP-SIS is intended to provide a vendor neutral, and device/architecture agnostic set of resources, peripherals, and Application Programming Interfaces (API's) with which to access them. By providing a common set of resources and API's, embedded applications can be ported more rapidly, and with less code modification or if/def configuration.
Supported Boards Library (Current-Beta)
.jpg "Cypress CY8CKIT-049")
Boards in Development (Pre-Alpha)
for detailed information
see the RSVPSIS Website
THIS SOFTWARE IS PROVIDED BY THE CONTRIBUTORS "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.