04:19 <M762spr[m]> Have you looked at embedded HAL?

04:19 <M762spr[m]> <fuse117[m]> "i am working with an i2c..." <- Have you looked at embedded HAL?

04:32 <M762spr[m]> https://docs.rs/embedded-hal/latest/embedded_hal/i2c/index.html

04:33 <M762spr[m]> theres also async flavor

04:33 <M762spr[m]> https://docs.rs/embedded-hal-async/latest/embedded_hal_async/i2c/index.html

06:37 <Lumpio-> I'm not sure if it's feasible to try to get the async version to work with a C library that probably expects a blocking read/write function

07:30 <owlfed[m]> Hello, sorry I think this is a common question, I will do some things with rust and microcontroller, I will buy them maybe next Monday.

07:30 <owlfed[m]> ESP32 vs STM32

07:30 <owlfed[m]> I will sense things like electrical signal, WiFi things, flow, etc… but I do not know what micro do I need to buy?

07:33 <AlexandervanSaas> ESP32 has wifi so that would be convenient.

07:34 <owlfed[m]> I will use some 4g too

07:34 <owlfed[m]> AlexandervanSaas: Wifi and BT

10:08 <pkoevesdi[m]> Hey everybody. I thought I try it here, I'm a rust embedded beginner and have hard times getting Octospi on a STM32H730BV working. I posted it here: https://users.rust-lang.org/t/problem-with-embassy-stm32-new/111166/3. Shall I repost my question here or is it better to just point to there? Thanks!

10:31 <M9names[m]> dirbaio is everywhere so it probably doesn't matter too much where you post it :)

10:31 <M9names[m]> but #embassy-rs:matrix.org is where i would recommend you ask about embassy-related things

10:31 <pkoevesdi[m]> M9names[m]: Ok, thank, then I try it there.

11:20 <AdamHott[m]> <owlfed[m]> "Hello, sorry I think this is a..." <- > <@owlfed:matrix.org> Hello, sorry I think this is a common question, I will do some things with rust and microcontroller, I will buy them maybe next Monday.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/kHqBXFlMCoBMMHMsmUCaZjAS>)

11:21 <AdamHott[m]> That's like the intro to embedded rust, it's what I followed about 6 months ago and I had success with that

11:22 <AdamHott[m]> But it doesn't have Wifi

11:58 <wassasin[m]> Got an gpio expander with interrupts on input pins, and configuring/de-configuring the interrupts is an interesting issue as it is all async and dropping the pin leaves an interrupt register still configured. Talk by @dirbaio @ RustNL inspired me to panic in the drop function to disallow it.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/ojGCfOeRIJStTZNEZoxzajKH>)

11:59 <wassasin[m]> As he said you can still core::mem::forget the pin, but don't do that

12:18 <Lumpio-> I get the feeling getting an actual async drop trait is years out, I wonder if it'd be possible to add some kind of compile time workaround at least

12:19 <Lumpio-> Some kind of CannotAutoDrop type that is a compile time error to drop automatically, and has to be done through a std::mem::yes_i_really_want_to_drop

12:19 <wassasin[m]> Yes this

12:21 <wassasin[m]> https://github.com/rust-lang/rfcs/issues/814

12:31 <Lumpio-> Oh no it's almost 10 years old too...

13:33 <explodingwaffle1> is there a risc-v room or is this the place to ask questions about those crates?

13:56 <thejpster[m]> link for later: https://godbolt.org/z/PhxGabqW7

15:21 <TrevorRHClarke[m> I'm having some trouble with the embedded hal on a stm32f103...using the latest versions of the crates. Here's an example to create the issue.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/OxirpJpZdxdVBObPnPBFbDbu>)

15:22 <TrevorRHClarke[m> * I'm having some trouble with the embedded hal on a stm32f103...using the latest versions of the crates. Here's an example to create the issue.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/KsvUAKnaMgIYjDNUaVrENxNA>)

15:39 <burrbull[m]> different `embedded-hal` versions?

15:39 <burrbull[m]> incomplete `1.0` support is here: https://github.com/stm32-rs/stm32f1xx-hal/pull/416

17:50 <ragarnoy[m]> Is there an UART trait somewhere or is the general idea to require a generic such as `UART: Read<u8, Error = E> + Write<u8, Error = E>` ?

17:52 <JamesMunns[m]> ragarnoy[m]: Check out "embedded-io"

17:52 <JamesMunns[m]> JamesMunns[m]: https://docs.rs/embedded-io/latest/embedded_io/

17:59 <henrik_alser[m]> And https://crates.io/crates/embedded-io-async

19:06 <ragarnoy[m]> <JamesMunns[m]> "Check out "embedded-io"" <- yeah I know about it but io, it gives the Read and Write io but there are no equivalent of SpiDevice definitions for uart is kind of what I meant

19:08 <dirbaio[m]> I'd you mean the SpiBus/SpiDevice split: there is no need, there's no equivalent of CS pins or bus sharing in uart. 

19:09 <dirbaio[m]> If you mean why there's no uart traits: the io traits *are* the uart traits. Uart is a byte stream, the io traits are a byte stream. 

19:46 <avery71[m]> `embedded-io` seems cool, are there any crates that utilize the traits from it?

19:46 <JamesMunns[m]> https://crates.io/crates/embedded-io/reverse_dependencies some!

19:48 <avery71[m]> oh shoot, I never realized the crates site had list of reverse dependencies. I normally just skip to the docs or directly to the repo