Skip to content
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.

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

Add CI for ESP #96

Merged
merged 4 commits into from
Jul 13, 2022
Merged

Add CI for ESP #96

merged 4 commits into from
Jul 13, 2022

Conversation

usbalbin
Copy link
Contributor

@usbalbin usbalbin commented Jul 1, 2022

From what I understand CI is currently only run for the ESP32-C3. This PR adds a github workflow for the ESP32. I believe this could be useful since some code is not active when building for the ESP32-C3.

Suggestions are welcome. Here is the result of the run.

src/hall.rs Show resolved Hide resolved
@usbalbin
Copy link
Contributor Author

usbalbin commented Jul 8, 2022

Rebased since #97

- name: Build | RISCV-ULP-HAL feature
run: cargo build --features riscv-ulp-hal --no-default-features --target riscv32imc-unknown-none-elf -Zbuild-std=core,panic_abort -Zbuild-std-features=panic_immediate_abort
run: cargo build --features riscv-ulp-hal --no-default-features --target ${{ matrix.target }} -Zbuild-std=core,panic_abort -Zbuild-std-features=panic_immediate_abort
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am a bit confused. What target is this supposed to have? xtensa-esp32s2-espidf, riscv32imc-esp-espidf, ${{ matrix.target }} or something else?

Also judging from lib.rs:

#[cfg(all(feature = "riscv-ulp-hal", not(esp32s2)))]
compile_error!("Feature `ulp` is currently only supported on esp32s2");

we are supposed to be targeting the esp32s2 device, but compiling for its riscv-coprocessor? What flags should we use to tell cargo this?


Also, perhaps semi unrelated, looking at IDF-doc both S2 and S3 have this thing? Would it be as trivial as simply enable it for the S3 aswell?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can just remove this part I think. The RISC-V ulp hal has to be compiled with riscv32imc-unknown-none-elf so no point adding this test to the xtensa target matrix.

@usbalbin
Copy link
Contributor Author

usbalbin commented Jul 13, 2022

Rebased and cleaned up

@usbalbin usbalbin marked this pull request as ready for review July 13, 2022 18:29
@MabezDev
Copy link
Member

Perfect, thanks @usbalbin!

@MabezDev MabezDev merged commit b0e243e into esp-rs:master Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants