Simulate SD card in software
a project by algraf
Updated almost 5 years ago. 14 hacker ♥️.

To make OpenQA work with real ARM devices, we need to control

  • Reset
  • HDMI
  • USB keyboard / tablet
  • SD card

Reset can be done using GPIO. HDMI can be done with a USB HDMI grabber. USB keyboard/tablet can be emulated via USB OTG.

That leaves only SD card simulation to be implemented to automatically verify whether our current openSUSE images still work on ARM development systems.

Join this project

Looking for hackers with the skills:

arm qemu arm64 aarch64 sd openqa raspberrypi

This project is part of:

Hack Week 14 Hack Week 16

Activity

  • over 6 years ago: ptesarik liked this project.
  • about 7 years ago: ldevulder liked this project.
  • about 7 years ago: bfilho liked this project.
  • about 7 years ago: oholecek liked this project.
  • about 7 years ago: osukup liked this project.
  • about 7 years ago: lnussel liked this project.
  • over 8 years ago: michal-m liked this project.
  • over 8 years ago: xbem joined this project.
  • over 8 years ago: adamm liked this project.
  • over 8 years ago: mvidner liked this project.
  • over 8 years ago: mbrugger liked this project.
  • over 8 years ago: evshmarnev liked this project.
  • over 8 years ago: vimacs liked this project.
  • over 8 years ago: vimacs liked this project.
  • over 8 years ago: algraf started this project.
  • over 8 years ago: algraf added keyword "raspberrypi" to this project.
  • over 8 years ago: algraf added keyword "openqa" to this project.
  • over 8 years ago: a_faerber liked this project.
  • over 8 years ago: algraf added keyword "arm" to this project.
  • over 8 years ago: algraf added keyword "qemu" to this project.
  • over 8 years ago: algraf added keyword "arm64" to this project.
  • over 8 years ago: algraf added keyword "aarch64" to this project.
  • over 8 years ago: algraf added keyword "sd" to this project.
  • over 8 years ago: algraf originated this project.


    • Comments

    • algraf
      about 7 years ago by algraf | Reply

      For Hackweek 16, let's make the FPGA+Verilog iteration of it work for real ;)

    • lnussel
      about 7 years ago by lnussel | Reply

      do you know an affordable, lossless USB HDMI grabber?

    Similar Projects

    Create openSUSE images for Arm/RISC-V boards by avicenzi

    Project Description

    Create openSUSE images (or test generic EFI images) for Arm and/or RISC-V boards that are not yet supported.

    Goal for this Hackweek

    Create bootable images of Tumbleweed for SBCs that currently have no images available or are untested.

    Consider generic EFI images where possible, as some boards can hold a bootloader.

    Document in the openSUSE Wiki how to flash and use the image for a given board.

    Boards that I have around and there are no images:

    • Rock 3B
    • Nano PC T3 Plus
    • Lichee RV D1
    • StartFive VisionFive (has some image needs testing)

    Hack Week 22

    Hack Week 21

    Resources

    OpenQA Golang api client by hilchev

    Description

    I would like to make a simple cli tool to communicate with the OpenQA API

    Goals

    • OpenQA has a ton of information that is hard to get via the UI. A tool like this would make my life easier :)
    • Would potentially make it easier in the future to make UI changes without Perl.
    • Improve my Golang skills

    Resources

    • https://go.dev/doc/
    • https://openqa.opensuse.org/api

    New features in openqa-trigger-from-obs for openQA by jlausuch

    Description

    Implement new features in openqa-trigger-from-obs to make xml more flexible.

    Goals

    One of the features to be implemented: - Possibility to define "VERSION" and "ARCH" variables per flavor instead of global.

    Resources

    https://github.com/os-autoinst/openqa-trigger-from-obs

    Enhance UV openQA helper script by mdonis

    Description

    A couple months ago an UV openQA helper script was created to help/automate the searching phase inside openQA for a given MU to test. The script searches inside all our openQA job groups (qam-sle) related with a given MU and generates an output suitable to add (copy & paste) inside the update log.

    This is still a WIP and could use some enhancements.

    Goals

    • Move script from bash to python: this would be useful in case we want to include this into MTUI in the future. The script will be separate from MTUI for now. The idea is to have this as a CLI tool using the click library or something similar.
    • Add option to look for jobs in other sections inside aggregated updates: right now, when looking for regression tests under aggregated updates for a given MU, the script only looks inside the Core MU job group. This is where most of the regression tests we need are located, but some MUs have their regression tests under the YaST/Containers/Security MU job groups. We should keep the Core MU group as a default, but add an option to be able to look into other job groups under aggregated updates.
    • Remove the -a option: this option is used to indicate the update ID and is mandatory right now. This is a bit weird and goes against posix stardards. It was developed this way in order to avoid using positional parameters. This problem should be fixed if we move the script to python.

    Some other ideas to consider:

    • Look into the QAM dashboard API. This has more info on each MU, could use this to link general openQA build results, whether the related RR is approved or not, etc
    • Make it easier to see if there's regression tests for a package in an openQA test build. Check if there's a possibility to search for tests that have the package name in them inside each testsuite.
    • Unit testing?

    More ideas TBD

    Resources

    https://github.com/os-autoinst/scripts/blob/master/openqa-search-maintenance-core-jobs

    https://confluence.suse.com/display/maintenanceqa/Guide+on+how+to+test+Updates

    Learn obs/ibs sync tool by xlai

    Description

    Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.

    Goals

    Check how the tool is implemented, and be capable to add/modify our needed images/repo in future by ourselves.

    Resources

    • https://github.com/os-autoinst/openqa-trigger-from-obs
    • https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/tree/master?ref_type=heads

    Make more sense of openQA test results using AI by livdywan

    Description

    AI has the potential to help with something many of us spend a lot of time doing which is making sense of openQA logs when a job fails.

    User Story

    Allison Average has a puzzled look on their face while staring at log files that seem to make little sense. Is this a known issue, something completely new or maybe related to infrastructure changes?

    Goals

    • Leverage a chat interface to help Allison
    • Create a model from scratch based on data from openQA
    • Proof of concept for automated analysis of openQA test results

    Bonus

    • Use AI to suggest solutions to merge conflicts
      • This would need a merge conflict editor that can suggest solving the conflict
    • Use image recognition for needles

    Resources

    Timeline

    Day 1

    • Conversing with open-webui to teach me how to create a model based on openQA test results

    Day 2

    Highlights

    • I briefly tested compared models to see if they would make me more productive. Between llama, gemma and mistral there was no amazing difference in the results for my case.
    • Convincing the chat interface to produce code specific to my use case required very explicit instructions.
    • Asking for advice on how to use open-webui itself better was frustratingly unfruitful both in trivial and more advanced regards.
    • Documentation on source materials used by LLM's and tools for this purpose seems virtually non-existent - specifically if a logo can be generated based on particular licenses

    Outcomes