02:19 <re_irc> <bradleyharden> Not sure if people have seen this, but I came across the "coca" (https://docs.rs/coca/0.3.0/coca/index.html) crate today, which seems to be a really interesting alternative to "heapless".

05:44 <re_irc> <korken89> Nice, finally someone made a vec that is not const generic

07:50 <re_irc> <luojia65> How to add +v,+k features for risc-v targets? Should I modify compiler code and recompile rustc?

07:50 <re_irc> <luojia65> They are disabled and we can't use intrinsics in them by now

13:22 <re_irc> <firefrommoonlight> dirbaio: I'm working on a Rust non-embeddes project using Hyper (Http lib). There's a small risk I'll end up liking async

13:22 <re_irc> <firefrommoonlight> We'll see

13:22 <re_irc> <firefrommoonlight> dirbaio: I'm working on a Rust non-embedded project using Hyper (Http lib). There's a small risk I'll end up liking async

13:22 <re_irc> <firefrommoonlight> dirbaio: I'm working on a Rust non-embedded project using Hyper (Http lib). There's a small risk I'll end up liking async

13:54 <re_irc> <justinrestivo> luojia65: v and k are riscv extensions right? You can dump the json spec with "rustc +nightly -Z unstable-options --print target-spec-json --target riscv64gc-unknown-none-elf", then add the "+k" and "+v" extensions to that json file. Then to run you can use "cargo build --target $path_to_modified_json_file". That might work _if_ rustc supports those extensions...

17:18 <re_irc> <chmanie> I'm using embedded_hal_mock for my tests but it's no_std and requires a Vec in its API. I must be missing something but how can I get a Vec in my no_std tests?

17:21 <re_irc> <GrantM11235> Replace "#[no_std]" with "#![cfg_attr(not(test), no_std)]"

17:27 <re_irc> <chmanie> GrantM11235: that makes sense, thanks a lot!

21:36 <Lewis[m]> Good evening folks, I don't suppose anyone has one of these lying around -- STM32F303VC (a.k.a. the STM32F3DISCOVERY devboard used in the rust-embedded book) that they'd be willing to part with and/or ship to Berlin, Germany?

21:38 <re_irc> <henrik_alser> Lewis[m]: Btw, the most recent version of the book uses the microbit instead, which should be easy to source?

21:38 <re_irc> <henrik_alser> +v2

21:39 <re_irc> <Lewis> I wasn't sure whether I'd benefit from using that STM32 board as my planned board of attack uses an M3 (I think) Cortex processor on it, so I guess that might be more similar? But I can also look for micro:bits

21:45 <re_irc> <henrik_alser> I haven’t checked out the books really so don’t know how specific they are to a particular chip or if it’s more about the concepts..

21:47 <re_irc> <henrik_alser> What family of the M3 were you looking at? stm32? Stm has a couple of different lines of that flavour like the f1 etc

21:47 <re_irc> <henrik_alser> You can check out the nucleo boards aswell

21:48 <re_irc> <Lewis> it's very possible that it's conceptual and I'd be fine with either. I'm still very much a newb to the whole thing, so I'm taking things slowly and just trying to make sure I don't go too far down the wrong rabbitholes

21:49 <re_irc> <Lewis> I _believe_ it's the STM32F103

21:50 <re_irc> <Lewis> (it's the new-ish default 32 bit board shipped on an ender 3)

21:51 <re_irc> <henrik_alser> I believe there’s a nucleo for that one

21:52 <re_irc> <henrik_alser> That one is also on the venerable ”blue pill” breakout boards, but then you’d need to get yourself an external debug probe aswell

21:57 <re_irc> <Lewis> external debug probe being like a multimeter, or a USB <> TTL probe? Or something else entirely?

21:57 <re_irc> <henrik_alser> https://www.digikey.com/en/products/detail/stmicroelectronics/NUCLEO-F103RB/4695527

21:59 <re_irc> <henrik_alser> Lewis: Something USB > SWD so you can flash the chip and do logging / debugging

22:00 <re_irc> <henrik_alser> Could be for example a cheap stlink v2 clone or you could get something like an rp pico (rp2040) and flash it with a probe firmware

22:01 <re_irc> <Lewis> ah okay, but with the nucleo I wouldn't need to worry about that? Only when transferring to try and run on the printer board itself?

22:02 <re_irc> <Lewis> (because from the looks of things the nucleo has a USB input for that?

22:02 <re_irc> <Lewis> )

22:02 <re_irc> <henrik_alser> Lewis: The nucleo has an onboard stlink so just plug and play

22:03 <re_irc> <henrik_alser> This onboard debug probe can also be used with external boards

22:06 <re_irc> <henrik_alser> (Just remove a two jumpers and connect the external board to the swd pin header)

22:06 <re_irc> <Lewis> oh great, that'll save me a job later :)

22:06 <re_irc> <Lewis> thank you for all your help

22:07 <re_irc> <henrik_alser> Good luck! We’re here whenever you need help :)

22:07 <re_irc> <Lewis> I'll be quiet for a bit no doubt, but will pop up with questions that I'm struggling to find answers to :) There are a whole lot of acronyms to get used to as well

22:09 <re_irc> <henrik_alser> Haha yes 😅 But you’ll be fine :)

22:14 <re_irc> <Lewis> also hoo boy "A delivery charge of 18 EUR will be billed on orders less than 50 EUR." Will find an alternate supplier for that nucleo :D

22:17 <re_irc> <Lewis> (I've thankfully found one)

22:19 <re_irc> <henrik_alser> Lol, yes although i usually have no problem reaching 50eur (and beyond) for various stuff always needed in the lab every time i go there…

22:21 <re_irc> <Lewis> oh yeah, I can definitely imagine stocking up becomes much easier once you have stuff set up :)