01:47 <i509vcb[m]> Wow the SiLabs SVD is awful

11:04 <tiwalun[m]> I'm trying to compile for riscv32emc, should I be able to do this using the stable release now? The release notes for 1.83 mention that riscv32emc is now a tier 3 target.

11:04 <tiwalun[m]> But when I try to add it using `rustup target add riscv32emc-unknown-none-elf`, I only get an error that it's not available.

11:05 <vollbrecht[m]> tiwalun[m]: Tier3 targets are not part of rust stable releases, e.g you need to have a nightly compiler.

11:06 <ivmarkov[m]> vollbrecht[m]: `riscv32emc-unknown-none-elf` is Tier 2 in the meantime, no?

11:06 <tiwalun[m]> Also nightly doesn't seem to have it:

11:06 <tiwalun[m]> `error: toolchain 'nightly-aarch64-apple-darwin' does not support target 'riscv32emc-unknown-none-elf'; did you mean 'riscv32imc-unknown-none-elf'?`

11:06 <ivmarkov[m]> https://doc.rust-lang.org/rustc/platform-support/riscv32-unknown-none-elf.html

11:06 <ivmarkov[m]> what is riscv32Emc? First time hearing about it?

11:07 <ivmarkov[m]> s/riscv32emc/riscv32imc/

11:09 <M9names[m]> it's an rv32e with the m and c extensions

11:09 <tiwalun[m]> https://doc.rust-lang.org/nightly/rustc/platform-support/riscv32e-unknown-none-elf.html

11:09 <M9names[m]> rv32e is rv32i, but with only half the number of registers

11:10 <ivmarkov[m]> OK, then my bad, this is as vollbrecht either Tier 3 or not available in your nightly at all. So you neded to use -Zbuild-std, if it is even available in your nightly

11:10 <ivmarkov[m]> * as vollbrecht says either Tier

11:10 <ivmarkov[m]> * OK, then my bad, this is as vollbrecht says either Tier 3 or not available in your nightly at all. So you need to use -Zbuild-std, if it is even available in your nightly

11:12 <M9names[m]> i recommend using a ch32v003 project as a starting point, it's rv32ec so what works for that should work for you too.

11:12 <M9names[m]> https://github.com/ch32-rs/ch32-hal/tree/main/examples/ch32v003

11:19 <tiwalun[m]> I have a working setup with a custom target json, I was hoping that I could get it of it :(

11:21 <tiwalun[m]> s/it/rid/

11:23 <JamesMunns[m]> tiwalun[m]: if you (and maybe a +1) are willing to be a target maintainer, you can likely propose to promote the rv32emc target to tier 2.

11:23 <JamesMunns[m]> * [tier 2 policy](https://doc.rust-lang.org/nightly/rustc/target-tier-policy.html#tier-2-target-policy)

11:23 <JamesMunns[m]> * [current target page + maintainers](https://doc.rust-lang.org/nightly/rustc/platform-support/riscv32e-unknown-none-elf.html)

11:25 <M9names[m]> You could start with tier 3, so you don't need the custom target yaml.

11:25 <M9names[m]> Nightly + build_std isn't too painful, the target file is the most annoying part IMO.

11:26 <JamesMunns[m]> Or, join the RISC-V team: https://github.com/rust-embedded/wg#the-risc-v-team, and propose adding it to a list of supported targets, like the other riscv32i* targets: https://doc.rust-lang.org/nightly/rustc/platform-support/riscv32-unknown-none-elf.html

11:45 <tiwalun[m]> I think I didn't really understand the tier 3 part, but it seems that at least now I don't need my json file anymore, but I can just use build-core and specify the target, and it works. So at least the target definition is now part of the compiler.

14:42 <davidmpye[m]> Is there a way for an embassy task to self terminate? I've got one which tries to initialise an i2c peripheral, and it it is there it continues to work with it. But if the peripheral isn't present, I'd like the task to self terminate

14:43 <davidmpye[m]> I appreciate I could try to initialise the peripheral in main and only spawn the task after it has been proven to exist

14:45 <dirbaio[m]> davidmpye[m]: to self-terminate the task can simply return. when it returns it'll stop doing things.

14:48 <davidmpye[m]> I'd defined all my tasks to not return ie ! . I'd assumed that was required but I'm guessing not! Simpler than I'd thought....