Riscv zephyr support

[trigpolynom]

Adds riscv32 support to the zephyr-rtos module.

This addresses Issue #1416.

[baentsch]

Thanks for the additional platform support. Please also document it in "PLATFORMS.md". I'd suggest adding it as Tier 2, unless someone disagrees.

[trigpolynom]

thanks for the prompt review @baentsch, added the else clauses and added to PLATFORMS.md

[baentsch]

Thanks for the updates, @trigpolynom ! Now LGTM. 2nd review, please @SWilson4 @dstebila .

[SWilson4]

Thanks for the additional platform support. Please also document it in "PLATFORMS.md". I'd suggest adding it as Tier 2, unless someone disagrees.

This is probably out of scope for this PR, but glancing at PLATFORMS.md, it looks like the only entry for Zephyr is the (proposed) one for RISCV. Do you know if this is intentional @baentsch, or should it be updated?

[baentsch]

Thanks for the additional platform support. Please also document it in "PLATFORMS.md". I'd suggest adding it as Tier 2, unless someone disagrees.

This is probably out of scope for this PR, but glancing at PLATFORMS.md, it looks like the only entry for Zephyr is the (proposed) one for RISCV. Do you know if this is intentional @baentsch, or should it be updated?

How would you suggest updating it? Zephyr is the only runtime where we have tests for that HW, so listing something different (Linux?) or generic might set wrong expectations.

[SWilson4]

Thanks for the additional platform support. Please also document it in "PLATFORMS.md". I'd suggest adding it as Tier 2, unless someone disagrees.

This is probably out of scope for this PR, but glancing at PLATFORMS.md, it looks like the only entry for Zephyr is the (proposed) one for RISCV. Do you know if this is intentional @baentsch, or should it be updated?

How would you suggest updating it? Zephyr is the only runtime where we have tests for that HW, so listing something different (Linux?) or generic might set wrong expectations.

Ah, I meant documenting support for Zephyr on other architectures, not other OSes for RISCV. It looks to me like we have CI for Zephyr on x86 and support building Zephyr on Arm.

[Frauschi]

Hi there,

nice to see new platforms added to the Zephyr port so quickly 😄 I left a single comment regarding the general CMakeLists.txt change, otherwise, this looks very good.

Ah, I meant documenting support for Zephyr on other architectures, not other OSes for RISCV. It looks to me like we have CI for Zephyr on x86 and support building Zephyr on Arm.

I think this should have happened within my initial Zephyr port PR. I can add this next week once I‘m back in the office.

[baentsch]

Ah, I meant documenting support for Zephyr on other architectures, not other OSes for RISCV. It looks to me like we have CI for Zephyr on x86 and support building Zephyr on Arm.

Good point(s). @trigpolynom : (How) would you want to add these HW platforms to "PLATFORMS.md"?

[trigpolynom]

Good point(s). @trigpolynom : (How) would you want to add these HW platforms to "PLATFORMS.md"?

I'm not partial to any particular representation! I'd best defer to you and your colleagues' preferences!

Waiting for platform update

[Frauschi]

@trigpolynom as #1658 with my fixes is merged now, you can rebase to finalize this PR. 😄

[trigpolynom]

@Frauschi thank you! Rebased and merged and should be good to go @baentsch

[baentsch]

Thanks for the update(s) @trigpolynom @Frauschi !