General: Hardware CI #10

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.

Sign up for GitHub

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

Jump to bottom

Open

3 of 7 tasks

xarantolus opened this issue Feb 15, 2025 · 0 comments · May be fixed by #12

Open

3 of 7 tasks

General: Hardware CI #10

xarantolus opened this issue Feb 15, 2025 · 0 comments · May be fixed by #12

Assignees

Labels

Contributor

xarantolus commented Feb 15, 2025 •

edited

Loading

#8 adds a lot of things we want for CI, including tests, formatting, and model checking.

However, it would also be nice to create test applications that can run on Hardware (e.g. Nucleo L4R5ZI) and then test their results.

That would require from an operational point of view:

Some hardware we test on (e.g. my Nucleo)
Self-hosted runner that has the Nucleo connected via USB
A way to get output (e.g. USB-TTL thingy for UART?)
Some test framework we use to flash code to the Nucleo (e.g. something python-based that makes it easy)
- This could include utility functions like waiting for a specific line to be printed by an application

From a software point of view we need:

Some way to actually create test applications (and many of them), similar to how typical Rust projects can have example binaries
A testing framework

xarantolus self-assigned this

xarantolus linked a pull request

that will close this issue

Draft: Hardware Tests in CI #12

Open

thomasw04 changed the title ~~Hardware CI~~ General: Hardware CI

thomasw04 added the enhancement label

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