03:08 <leonardvdj[m]> Out of curiosity, which mcu's do y'all use?

04:58 <djdisodo[m]> atmega328p coz it's the only one i have for now

05:12 <hadez[m]> wch ch32v20x and ch32v30x also stms and newer avr DX series. Have some pi 2040 dev boards sitting around too but they were never interesting enough or had enough of a product lineup to pull me in.

07:16 <timokrgr[m]> nrf52 is my go to for quick projects (becaues of good embassy support)

09:42 <sample-user-just> <sample-user-just> "Hello everyone!..." <- > <@sample-user-just-testing:matrix.org> Hello everyone!... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/eYNOKSgafndQRBrqkLvTPUiG>)

09:43 <TristramGrbener[> <leonardvdj[m]> "Out of curiosity, which mcu's do..." <- nrf52 because I got a microbit to discover the embed world

11:09 <M9names[m]> Sorry, what exactly are you trying to do? If it's enabling/disabling specific interrupts that's not the register you're looking for.

11:10 <M9names[m]> Also please tell us which riscv target you're talking about so we can provide targeted advice

11:54 <sample-user-just> <M9names[m]> "Sorry, what exactly are you..." <- I am trying to delegate every interrupt to supervisor mode, but the crate does not provide a way to do so. I am targeting riscv64.

11:58 <sample-user-just> Mistakenly used 'enable' when I meant 'delegate' in the previous post, sorry for the confusion.

13:52 <TristramGrbener[> <bartmassey[m]> "Yeah my thing is from a long..." <- thank you for that initial work, that was motivating me.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/JpOHmtaYoiUQLhvunngBogtr>)

14:21 <dirbaio[m]> > I’m confused that in embassy the pin is never configured (OpenDrainConfig). Does all the magic happen in saadc::ChannelConfig::single_ended(p.P0_05) ?... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/EvsQpizkuQnUvqVOOtdeGNoy>)

14:22 <dirbaio[m]> saadc::ChannelConfig::single_ended(p.P0_05) does magic to set P0_05 in analog mode

14:22 <dirbaio[m]> but you still have to set P0_20 as high yourself.

14:23 <dirbaio[m]> let mic_run = Output::new(p.P0_20, Level::High, OutputDrive::High); should do it

14:24 <dirbaio[m]> s//`/, s/High/HighDrive/, s/;/;`/

14:31 <TristramGrbener[> <dirbaio[m]> "let mic_run = Output::new(p.P0_..." <- aha, things are happening. Thank you! What would is the best way to discover those things?

14:31 <TristramGrbener[> I suppose this is very microbit-v2 specific. After you pointed it, I found a RUN_MIC on https://tech.microbit.org/hardware/schematic/ but without a explaination on how to run it

14:32 <dirbaio[m]> TristramGrbener[: I "discovered" it by reading the other example you linked https://github.com/BartMassey/microbit-spectrum/blob/main/src/main.rs#L87-L90

14:32 <dirbaio[m]> * I "discovered" it by reading the other example you linked

14:32 <dirbaio[m]> dirbaio[m]: this is where it sets MIC_RUN to high https://github.com/BartMassey/microbit-spectrum/blob/main/src/main.rs#L87-L90

14:33 <dirbaio[m]> dirbaio[m]: and if you read into the `microbit-v2` source

14:33 <dirbaio[m]> dirbaio[m]: (a few layers deep! it goes down to `microbit-common` crate...)

14:33 <TristramGrbener[> dirbaio[m]: Oh! I see, it’s hidden in behind the board abstraction. I though it was some weird mode that has to be set to get analog data

14:34 <dirbaio[m]> TristramGrbener[: you can see what `microphone_pins.mic_run` is

14:34 <dirbaio[m]> TristramGrbener[: https://github.com/nrf-rs/microbit/blob/main/microbit-common/src/v2/gpio.rs#L42-L43

14:34 <dirbaio[m]> dirbaio[m]: yeah the `microbit-v2` crate is a BSP (board support package)

14:34 <dirbaio[m]> dirbaio[m]: essentially all it does is rename pins

14:35 <dirbaio[m]> dirbaio[m]: so you can refer to it with a nice name like `board.microphone_pins.mic_run` instead of `p.P0_20`

14:36 <TristramGrbener[> dirbaio[m]: 👍️ I still need some practice to find on my own, but I start to understand a few parts

14:36 <dirbaio[m]> TristramGrbener[: (I personally don't like BSPs much, IMO it adds too much indirection, which hurts discoverability/learnability, but that's a whole other story... 🥲)

14:37 <TristramGrbener[> dirbaio[m]: As a beginer, it’s also quite confusing to never really be sure what level of abstraction I’m currently using

14:37 <dirbaio[m]> TristramGrbener[: (I don't think the Rust Discovery book should not use a BSP)

14:37 <dirbaio[m]> s/don't//

14:37 <dirbaio[m]> * (I think the Rust Embedded Discovery book should not use a BSP)

14:38 <TristramGrbener[> dirbaio[m]: at least your work on embassy and using async make a lot of sense to me and is relatable to daytime work

14:59 <firefrommoonligh> <dirbaio[m]> "(I don't think the Rust Discover..." <- Of note, this (The F3 one) induced considerable confusion as it complicated transitioning from the tutorial to an isolated project

17:24 <sethiam[m]> I'm working on developing an ADC v2 task that does scan & continuous modes, much like what I saw in what I think was a G4 PR. I was wondering if y'all would accept a PR if I developed the same on the v2 ADC API. I know there's some question about extensibility/uniformity across the various ADC versions, so if no, I'll just use the pac.

17:24 <sethiam[m]> s/no/not/

17:47 <sethiam[m]> * Wrong chat

22:48 <holo[m]> Hello. Im trying to start with Embeded Rust (and rust at all for some long time) on RP5. I wanted to start with DHT22 sensor and try just to use example from here: https://github.com/michaelfletchercgy/dht22_pi/blob/master/examples/display.rs

22:48 <holo[m]> What i understand this crate is using rppal (https://github.com/golemparts/rppal) which according to description on readme mentionning its supporting RP5 too. But when i will compile this example im getting: ```Err(Gpio(UnknownModel))```

22:49 <holo[m]> s/dht22_pi/dht22\_pi/, s/```/`/, s/```/`. Any advices what im doing wrong or maybe there is some better RP for starting with learning embeded rust (RP Zero 2?)/

22:49 <holo[m]> s/dht22_pi/dht22\_pi/, s/```/`/, s/```/`. Any advices what im doing wrong or maybe there is some better RP for starting with learning embeded rust (RP Zero 2? i see its supproted by rppal too)/

22:51 <holo[m]> * Hello. Im trying to start with Embeded Rust (and rust at all for some long time) on RP5. I wanted to start with DHT22 sensor and try just to use example from here: https://github.com/michaelfletchercgy/dht22\_pi/blob/master/examples/display.rs

22:51 <holo[m]> What i understand this crate is using rppal (https://github.com/golemparts/rppal) which according to description on readme mentionning its supporting RP5 too. But when i will compile this example and try to start it im getting: `Err(Gpio(UnknownModel))`. Any advices what im doing wrong or maybe there is some better RP for starting with learning embeded rust (RP Zero 2? i see its supproted by rppal too)

22:59 <holo[m]> * Hello. Im trying to start with Embeded Rust (and rust at all again from some long time) on RP5. I wanted to start with DHT22 sensor and try just to use example from here: https://github.com/michaelfletchercgy/dht22\_pi/blob/master/examples/display.rs

22:59 <holo[m]> What i understand this crate is using rppal (https://github.com/golemparts/rppal) which according to description on readme mentionning its supporting RP5 too. But when i will compile this example and try to start it im getting: `Err(Gpio(UnknownModel))`. Any advices what im doing wrong or maybe there is some better RP for starting with learning embeded rust (RP Zero 2? i see its supproted by rppal too)

23:08 <AdamHott[m]> <holo[m]> "Hello. Im trying to start with..." <- > <@holo:matrix.org> Hello. Im trying to start with Embeded Rust (and rust at all again from some long time) on RP5. I wanted to start with DHT22 sensor and try just to use example from here: https://github.com/michaelfletchercgy/dht22\_pi/blob/master/examples/display.rs... (full message at

23:08 <AdamHott[m]> <https://catircservices.org/_matrix/media/v3/download/catircservices.org/lQDBSXBdBYjGAyHKnTZIdDfA>)

23:08 <AdamHott[m]> The crates here:

23:08 <AdamHott[m]> https://crates.io/crates/rp2040-hal

23:08 <AdamHott[m]> https://crates.io/crates/rp2040

23:09 <AdamHott[m]> They support the rp2040 chip found in microcontrollers like the Raspberry Pi Pico

23:09 <holo[m]> AdamHott[m]: But what you putted is for rasberry pico (for which according to my review should be used with embassy-rs but im trying to use rppal which they mentioning its supporting all linux PIs excluding Pico

23:10 <holo[m]> > <@greengenie:matrix.org> Hi there! So from my understanding the Raspberry Pi 5's chip is different than what the embedded rust crate's support.

23:10 <holo[m]> * But what you putted is for rasberry pico (for which according to my review should be used with embassy-rs) and im trying to use rppal which they mentioning its supporting all linux PIs excluding Pico

23:10 <holo[m]> sudo apt-get update

23:10 <holo[m]> sudo apt-get install build-essential python-dev

23:10 <holo[m]> https://github.com/golemparts/rppal

23:10 <holo[m]> this and they mentioning RP 5 there (dht22_pi is using this crate)

23:11 <holo[m]> * this, and they mentioning RP 5 there (dht22_pi is using this crate)

23:11 <AdamHott[m]> This is interesting, I'm fairly new on my embedded rust journey as well

23:11 <dngrsspookyvisio> holo: most conversation in this room happens around "no OS" embedded Rust (aka e.g. rp2040), so you might not get a lot of support here. Not saying it's wrong to try though 🙃

23:12 <dngrsspookyvisio> * "no OS/bare metal" embedded

23:13 <holo[m]> dngrsspookyvisio: Yep i know my is based on OS based but its simplest way to start i think. Do you thing general rust channel will be better?

23:13 <AdamHott[m]> dngrsspookyvisio: This is what I've found as well, when I started learning about embedded rust, I discovered it's pretty cool to work with the mainstream microcontrollers that the embedded rust group supports, rather than a full blow mini-computer like the Rapsberry Pi

23:13 <holo[m]> * i know, my

23:14 <dngrsspookyvisio> holo[m]: you can try #rust:matrix.org, I can't guarantee you'll have more success there though

23:14 <holo[m]> dngrsspookyvisio: thank you

23:14 <holo[m]> holo[m]: willt try there too

23:14 <dngrsspookyvisio> holo[m]: maybe the easiest way forward is to try and contact the author(s) of the crate you're having trouble with

23:16 <holo[m]> dngrsspookyvisio: will crate issue in that case on github thank you

23:54 <holo[m]> <AdamHott[m]> "This is what I've found as well,..." <- I have ordered Pico W too and waiting for delivery so will be testing with it soon, just wanted to start on what i allredy had. Will try to ask carate owner on gihub