Contact Support
If you have any questions related to the LAA usage or issues you may be having with the device please don’t hesitate to reach out!
Support can be reached two ways:
For general enquiries about ONELab or other Linaro products, you can reach us at support@linaro.org.
If your question is associated with an active Linaro product subscription, we recommend you file a support ticket from within the Linaro Solutions Hub. Note this requires the user to be logged into the Linaro Solutions Hub.
Supporting Docs
This section provides pointers to useful reference documentation specific to ONELab.
SystemReady Docs
v3.0 or later of the Arm SystemReady Compliance System Requirements Specification.
Outlines the requirements a platform must adhere to to be SystemReady Compliant.
The ACS is used to test these requirements.
Chapter 3 is focused on the SystemReady DT band requirements
UEFI Specs
This section provides pointers to relevant UEFI specs v2.11 or later.
Local ACS Testing
How to independently run payload tests
Linux OS Distribution Installation Test Guide covers what should be captured from the OS installations.
How to independently run the SystemReady DT ACS Test suite
Github DT ACS repo with more details
SystemReady Scripts: https://gitlab.arm.com/systemready/systemready-scripts
Contains the capsule-tool.py which should be used to generate tampered and de-authenticated capsules.
Also contains the eth-tool.py which can be curl’d and ran from the OS Distro shell to generate the ethtool_test.log
Locally Running ACS
Before adding a platform to ONELab, it is beneficial to run the SystemReady DT ACS tests locally. Doing so helps identify and resolve issues early in the enablement process. This section outlines the steps to locally run ACS v3.0 to verify compliance before ONELab LAA integration. Running these tests in advance can reduce integration time when the platform is installed in ONELab.
Alternatively, you can skip this section and let ONELab handle the testing for you. In this case, ONELab will run the test suites on your platform and provide result logs for analysis. You can then review the results and make any necessary firmware adjustments. However, this approach has a drawback, as firmware issues uncovered during ACS testing will only emerge at the final stage of the enablement process, potentially causing delays by making this step a critical dependency.
Run ACS Tests
As noted above, independently verifying your platform’s readiness for SystemReady DT compliance before integration can be beneficial. Refer to the Local ACS Testing section for guidance on running these tests.
Attain SystemReady DT Compliance
To attain ONELab SystemReady DT compliance, users can now “self-comply” through the ACS Results Processing page. Once Self-Compliance is attained, the ONELab Explore Boards page will show you platform passing and you will be able to use the SystemReady logo for marketing purposes as you wish.
For more information, please see the SytemReady ACS Results Processing section of this document.
FAQs
Category |
Question |
Answer |
|---|---|---|
Getting Started |
How do I register for a ONELab account? |
Go to the ONELab Account Registration / Subscription Enablement chapter |
Is my platform compatible with ONELab? |
Review the ONELab Comprehensive Assessment Review in the ONELab Users Guide to better understand how to validate whethe your platform will be compatible with use in Linaro Products that use the LAA. |
|
How do I set up the LAA? |
Please visit the Quickstart section of the LAA User’s Guide. |
|
User Interface |
How do I build the file to input into ONELab? |
This can be found in the ONELab Firmware Packaging & Upload chapter. |
Question |
Answer |
|
SystemReady Compliance |
How do I get permission to use the SystemReady Logo and where can I find the logo? |
This information can be found in the following chapter of this User’s Guide. Understanding the ACS Results Processing Page |