00:20 <dirbaio[m]> you need to actually use it https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=a0505869db945ab616a3ddba2938dca8

00:20 <newam[m]> Ahhh, thanks

00:21 <dirbaio[m]> these post-mono errors are super cursed

00:23 <dirbaio[m]> not even Rust devs know when they should trigger yet :D

00:24 <dirbaio[m]> they recently approved an RFC officially allowing these to be caught by `cargo build` but not `cargo check`

00:24 <dirbaio[m]> https://github.com/rust-lang/rfcs/pull/3477

00:25 <dirbaio[m]> yep this particular assert is not caught by cargo check lol

00:25 <dirbaio[m]> only by cargo build

00:36 <newam[m]> Do you know off the top of your head if that will have a runtime cost?

00:36 <newam[m]> Checking for this: https://github.com/rust-embedded/heapless/pull/403

00:37 <newam[m]> O_o...

00:37 <newam[m]> Well miri isn't happy with it, that's not a good start

01:24 <dngrsspookyvisio> <JamesMunns[m]> "https://www.mattkeeter.com/blog/..."; <- oh *god* 💀

02:49 <uep[m]> oh shit.. "or we could have some fun" and I realise exactly what they are going to do to do the thing hinted at from the start

07:14 <thejpster[m]> diondokter: do you hang out with the binary side working group?

07:16 <diondokter[m]> thejpster[m]: I've found them on zulip, but haven't posted anything there yet

07:29 <dav1d> Anyone of a OneWire protocol implementation for esp32 and embassy? I want to read from a DS18B20 temp sensor

11:56 <haobogu[m]> Hi everyone, I'm wondering that is there any solution for Rust embedded to print memory usages after building a firmware? In my C project, I'm using -Wl,--gc-sections,--print-memory-usage flag for gcc and it prints something like the image

11:57 <diondokter[m]> You can install the cargo-binutils crate which will give you the cargo size command

11:58 <haobogu[m]> diondokter[m]: `cargo size` gives me the flash usage, but not ram usage

11:58 <diondokter[m]> It does, just not split out over the different regions

11:58 <diondokter[m]> data is stored in ram

11:59 <diondokter[m]> * data and bss is stored in ram

11:59 <haobogu[m]> Can I print the mem usage of sections defined in linker script?

12:00 <diondokter[m]> I don't know actually

12:00 <thejpster[m]> cargo size -- -A

12:01 <thejpster[m]> You can also pass linker flags to the linker (see .cargo/config.toml) so any linker flags you use with gcc probably work here too.

12:02 <thejpster[m]> (-Wl,xxx is a gcc flag which just passes the 'xxx' flag down to the linker)

12:02 <haobogu[m]> yeah, --print-memory-usage is a gcc ld specific flag, it doesn't work for llvm

12:03 <thejpster[m]> booo. I thought llvm lld did pretty much anything gcc ld did. Why not change the linker to use gcc then?

12:03 <thejpster[m]> Just add linker = "arm-none-eabi-gcc" to [target.thumbv7m-none-eabi]

12:06 <haobogu[m]> I tried but the gcc linker failed with arm-none-eabi/bin/ld: failed to merge target specific data of file error

12:10 <haobogu[m]> haobogu[m]: it says that the compiler uses VFP register arguments, but my project doesn't not. I don't know what's that mean..

12:10 <haobogu[m]> Anyway, `cargo size -- -A` prints what I need, thats bro thejpster

12:10 <haobogu[m]> thanks

12:37 <thejpster[m]> If you use gcc as a linker you possibly also need to give it "-mcpu=cortex-m4f" or something, and maybe "-nostdlib" and "-nostartfiles".

12:38 <thejpster[m]> Otherwise it'll try and link in libc, and if Rust made a bunch of object code that used the floating point unit (and put float arguments in floating point unit registers), but the C library didn't, I could see why it might complain.

13:51 <ryan-summers[m]> Small announcement (now that I'm back from vacation) for anyone interested - we're releasing 0.8.0 of minimq, a MQTTv5 MQTT client. This latest release makes it nearly feature-complete for the MQTTv5 stack, and it only takes up something like 17KB of flash based on my last measurements, so it's a really nice, small footprint solution for IoT projects and data analysis if you ever need it! https://crates.io/crates/minimq

13:51 <ryan-summers[m]> Also thanks Robert Jördens for the release on it :)

13:51 <ryan-summers[m]> s//`/, s/,/`,/, s/analysis/collection/

13:53 <diondokter[m]> Oh cool! Yet have to try it out. Though actually... maybe I've got an opportunity

13:53 <ryan-summers[m]> Just did a rework on memory management on it so that everything uses user-provided buffers like smoltcp, makes it really easy on stack usage for smaller devices.

13:54 <ryan-summers[m]> Although MQTT still needs to use ethernet, so small resource devices are probably still excluded

13:54 <ryan-summers[m]> * use ethernet + TCP stacks, so

14:01 <ryan-summers[m]> dirbaio: / newam re: heapless 0.8 - does it need a tag + changelog bump on Github as well? https://github.com/rust-embedded/heapless I'd PR if I knew which commit it was

14:03 <dav1d> ryan-summers[m], I assume I cant use your lib with async/embassy?

14:05 <ryan-summers[m]> First-class async support is on the horizon, but I don't see why you couldn't.

14:05 <ryan-summers[m]> Right now it has a poll() function similar to smoltcp

14:07 <dav1d> ah cool, Ill have to look into that, thanks!

14:50 <newam[m]> <ryan-summers[m]> "dirbaio: / newam re: heapless 0..." <- 0.8 doesn't exist yet AFAIK, someone just bumped the version in Cargo.toml preemptively after breaking changes were added to the 0.7.x series.

14:51 <ryan-summers[m]> Oh you're right. Now I'm very confused, thanks for the clarification :)

15:36 <firefrommoonligh> <ryan-summers[m]> "Small announcement (now that I'm..." <- V cool. Btw, I now do programming at work and we do a lot of MQTT stuff. I have been looking for excuses to build the projects in Rust! Fail so far as there's nothing on Django's level for web backend, and the Rust bindings for ML/CV are not in a usable state but... someday

15:37 <firefrommoonligh> > <@ryan-summers:matrix.org> Small announcement (now that I'm back from vacation) for anyone interested - we're releasing 0.8.0 of `minimq`, a MQTTv5 MQTT client. This latest release makes it nearly feature-complete for the MQTTv5 stack, and it only takes up something like 17KB of flash based on my last measurements, so it's a really nice, small footprint solution for IoT projects and data collection if you ever need it!

15:37 <firefrommoonligh> https://crates.io/crates/minimq

15:37 <firefrommoonligh> * V cool. Btw, I now do programming at a desk job, and we do a lot of MQTT stuff. I have been looking for excuses to build the projects in Rust! Fail so far as there's nothing on Django's level for web backend, and the Rust bindings for ML/CV are not in a usable state but... someday

15:38 <firefrommoonligh> (There are semi-official Rust OpenVINO and Tensorflow bindings, but they are out of date/high-build-friction)

15:38 <firefrommoonligh> * of date/missing critical features/high-build-friction)

16:02 <ryan-summers[m]> I use minimq a lot for even MQTT clients on host PCs honestly. Not the best API, but it works fine

16:04 <firefrommoonligh> V cool. Of note the [Paho MQTT](https://docs.rs/paho-mqtt/latest/paho_mqtt/) lib is what I was experimenting with; seemed solid, and similar to the C++ and Python ones

16:04 <firefrommoonligh> s/V cool/Nice/

16:05 <ryan-summers[m]> Yeah that's what I'd probably go with if I weren't no_std

22:37 <Danilo[m]> Hi folks! In https://github.com/dbrgn/embedded-hal-mock/pull/86 the maintenance question came up. Would you be interested in moving embedded-hal-mock to the rust-embedded GitHub organization? (I'd continue co-maintaining the library of course, as long as I find time to do it. But it might reduce the bus factor a bit more. ryankurte and newam are already co-maintainers.)