RIOLAB

RIOLAB tests address the graduated levels of interoperability that align with the increasing complexity of both the RapidIO specification and the needs of silicon vendors and OEMs. RIOLABs interoperability testing is based on the RapidIO Trade Associations RapidIO Device Interoperability and Specification Compliance Checklists, 1.3 Spec which was developed for RapidIO eco-system members as a guide in product development.

Essentially, there are two levels of tests defined by the RIOLAB. The first is essentially Device Interoperability (DI) tests where Device A is proven to pass a given test with Device B. The second is aligned with RapidIO Specification Compliance (SC), and involve specialized hardware and software. Both the DI and SC tests are separated into three levels.

Device Interoperability Tests

DIL-1 is the lowest level of interoperability testing. Proof of meeting this level is a requirement for entering RIOLAB for more advanced testing. RIOLAB will conduct DIL-1 tests to formally validate vendor results. This consists of support for initialization and enumeration and basic read and write packet transactions.
DIL-2 tests provide further evidence of device interoperability and require protocol validations with off-the-shelf test equipment. The prerequisite for DIL-2 testing is proof of successfully completing DIL-1.
DIL-3 is the final level of interoperability testing and, with DIL-1 and DIL-2, addresses virtually all of the Interop items on the RapidIO Trade Association checklist. DIL-3 tests interoperability between specific endpoints and may include a basic level of protocol violation testing. Successful completion of DIL-3 can only be claimed by parts successfully completing DIL-2. To undergo DIL-3 testing, devices must have secured DIL-1 validation through RIOLAB.

Specification Compliance Tests

SC level tests involve a level of scrutiny that surpases Interoperabiltiy level testing. Testing is no longer done against other devices specifically but instead different aspects of a devices implementation of the RapidIO protocol is tested against the RapidIO specification. SC level testing makes extensive use of mid-bus probing to validate various aspects of the RapidIO Protocol and introduces the use of RapidIO bus analyzers (mutant endpoints) to create protocol violations and monitor how devices recover (i.e. detection, and correction).

SCL-1 represents the first level where a PE is tested against protocol violations. The tests involve a significant use of test equipment to analyze adherence to the RapidIO protocol. The pre-requisite for SCL-1 is successful completion of DIL-3 with the minimum hardware PE configuration.
SCL-2 the second level of specification compliance testing explores device interoperability in greater depth. Only devices that have successfully completed SCL-1 can pass the SCL-2 tests. RIOLAB requires a successful completion of DIL-3 prior to testing any device for SCL-1.
SCL-3 Consists of most of the remaining RapidIO Trade Associations checklist items not covered in previous SCL or DIL testing. SCL-3 represents the final level of specification compliance testing, but does not represent Certification. To participate in SCL-3, devices must have received SCL-1 validation through RIOLAB.

At this time, RIOLAB does not offer Certification testing.

The following documents are currently available for download in pdf format:

Test Level Definitions

Test Descriptions

Test Procedures

Test Setup

Test Scripts

Example Scripts