00:25 <re_irc> <Alex Norman> has anyone here used rust-fatfs (https://github.com/rafalh/rust-fatfs) with SD? I'm curious to try myself if not but figured I'd check first..

00:25 <re_irc> I know that embedded-sdmmc exists but I'm wanting to be able to create directories..

02:17 <re_irc> <riskable> dirbaio: This gives me errors about Deserialize not being implemented for that specific type

02:18 <re_irc> <riskable> ...even though I have "#[derive(Debug, Serialize, Deserialize)]" on everything

05:46 <re_irc> <d3zd3z> Looks like there is no reason for me to actually create my presentation on running Rust code within Zephyr. GPT-3 was able to explain it perfectly: "Zephyr is a real-time operating system (RTOS) designed for use on embedded systems. It is open source and royalty-free.

05:46 <re_irc> To run Rust on Zephyr, you need to first install the Zephyr SDK. You can then use the Zephyr toolchain to compile your Rust code for the Zephyr target."

13:31 <re_irc> <DrRuhe> Hi everyone, I'm trying to compile a rust project for a beagleboard (target: arm-unknown-linux-gnueabihf) that uses a shared library. I want to create bindings using bindgen, but the user guide does not mention what to do when cross-compiling using cross. Does anybody know where I can find documentation on how to do that?

14:00 <re_irc> <Tom> d3zd3z: I'm looking forward to seeing that, you are presenting that in June?

15:02 <re_irc> <Alex Norman> DrRuhe: I haven't done this but there is a tool called "cross" that some people use for cross compilation, it looks like people have had some success with linking their own custom lib: https://github.com/cross-rs/cross/issues/347 so I figure that your situation shouldn't be too different?

15:02 <re_irc> Likely some other solutions too..

18:12 <re_irc> <riskable> Sweet: I got my crazy static "config.rs" generation working with unlimited numbers _and kinds_ of rotary encoders. So the end user can add in a mixture of analog encoders, digital encoders, encoders connected directly to GPIO pins, encoders connected through multiplexers, etc etc

18:13 <re_irc> <riskable> For the directly-attached-to-GPIO pin kind though I need to come up with a way to map pin numbers to actual pin types. I suppose I'll just require a "pin_map.rs" in the board-specific directory.

18:15 <re_irc> <riskable> Now to give displays and lighting (aka RGB) the same treatment so my firmware can support unlimited numbers of displays and lighting control mechanisms! 😄👍

21:18 <re_irc> <dirbaio> has anyone seen/fixed this error before? happens when using "f32" on a non-"hf" target like "thumbv7em-none-eabi"

21:18 <re_irc> = note: rust-lld: error: undefined symbol: core::intrinsics::const_eval_select::h4fee5fc21c0763a9

21:18 <re_irc> >>> referenced by f32.rs:942 (/home/dirbaio/.rustup/toolchains/nightly-2022-04-24-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/num/f32.rs:942)

21:31 <re_irc> <dirbaio> fixed by.. not using f32, easy :D

21:40 <re_irc> <ryankurte> i don't think i've ever managed to use rust-lld with thumb targets 😅

21:41 <re_irc> <dirbaio> it's worked fine for me.. linking to some C code even

21:42 <re_irc> <ryankurte> amazing! i've got layers of hacks and faked-out newlib stubs to get that sort of working

21:42 <re_irc> <dirbaio> O_o

21:42 <re_irc> <ryankurte> to be fair it might be -what- i'm linking more than anything else (wasm3)

21:43 <re_irc> <dirbaio> oh... yeah 😂

21:43 <re_irc> <ryankurte> though libsodium used to be equally awful

21:43 <re_irc> <dirbaio> the C I'm linking doesn't even need libc I think

21:43 <re_irc> <ryankurte> +to convince to link

21:53 <re_irc> <James Munns> dirbaio you seem to have fixed it, but my only guess would have been "link in "libm""

21:54 <re_irc> <dirbaio> f32 add/multiply/divide shouldn't require libm :S

21:54 <re_irc> <dirbaio> also iirc this worked before

21:55 <re_irc> <ryankurte> ahh, bullying things into using the right hard-float was another reason i ended up linking with gcc

21:55 <re_irc> <ryankurte> * gcc, but one assumes that shouldn't be required

21:55 <re_irc> <dirbaio> i'm building without even though my chip has HF

21:56 <re_irc> <dirbaio> because last I checked, building with HF increased code size by +1kb 🤷

21:57 <re_irc> <James Munns> https://github.com/rust-lang/rust/blob/18b53cefdf7456bf68937b08e377b7e622a115c2/library/core/src/num/f32.rs#L894-L943

21:57 <re_irc> <James Munns> > SAFETY: We use internal implementations that either always work or fail at compile time.

21:57 <re_irc> <James Munns> lol

21:59 <re_irc> <James Munns> That is some of the most cursed code I've read in recent history

21:59 <re_irc> <dirbaio> this is no longer the case today thankfully

21:59 <re_irc> thumbv7em-none-eabi: 116628

21:59 <re_irc> thumbv7em-none-eabihf: 116636

22:00 <re_irc> <James Munns> Looks like workingjubilee is the author of that code, might be worth pinging them on twitter

22:00 <re_irc> <newam> James Munns: Wow I love this

22:00 <re_irc> // ...look, just pretend you forgot what you just read.

22:00 <re_irc> // Stability concerns.

22:00 <re_irc> // SAFETY: `u32` is a plain old datatype so we can always... uh...

22:00 <re_irc> let rt_f32_to_u32 = |rt| unsafe { mem::transmute::<f32, u32>(rt) };

22:01 <re_irc> <dirbaio> all the float stuff is so cursed

22:02 <re_irc> <dirbaio> I don't really need floats, it was just for a factory test and I was being lazy

22:02 <re_irc> <James Munns> I wonder how your C code was invoking "f32::to_bits()"

22:02 <re_irc> <dirbaio> no, it was rust

22:03 <re_irc> <dirbaio> // measure_voltage() returns f16

22:03 <re_irc> let v = battery.measure_voltage().await as f32 / 256.0;

22:03 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/45d0f34e4ba5820e8a87be5b69073af6b5a90fa78d7294712a2843ee32a554d7 (7 lines)

22:03 <re_irc> info!("[BAT] {:?} V", v);

22:03 <re_irc> // before

22:03 <re_irc> <James Munns> I'd ask you why you were doing that, but honestly, that's how I serialize floats in postcard :p

22:03 <re_irc> <dirbaio> // measure_voltage() returns f16

22:03 <re_irc> let v = battery.measure_voltage().await as f32 / 256.0;

22:03 <re_irc> // before

22:03 <re_irc> info!("[BAT] {:?} V", v);

22:03 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/60eee0b8e91b3bd976a5f3c02b7ce12bf88d5ce5952db163ec506a3d59aa6382 (7 lines)

22:03 <re_irc> <James Munns> ahhh yeah, defmt does that too.

22:03 <re_irc> <dirbaio> ah, defmt!

22:03 <re_irc> <James Munns> I don't know for sure, but I would bet it does.

23:19 <re_irc> <Lachlan Sneff> Ooops, opamp got zapped

23:28 <re_irc> <yruama_lairba> does somebody knows stm32 nucleo board ? i'd like to know what does the AVDD pin but can't find the information