04:10 <re_irc> <firefrommoonlight> GrantM11235: Do you have any projects that use SPI?

04:11 <re_irc> <firefrommoonlight> Of note, that sounds ... Not ideal, since SPI generally uses both lines simultaneously

04:14 <re_irc> <GrantM11235> Half duplex devices do exist, for example the TM1638 led/button driver chip

04:34 <re_irc> <9names (@9names:matrix.org)> it's not really a standard though, is it? TM1638 makes no mention of SPI at all in it's datasheet.

04:36 <re_irc> <9names (@9names:matrix.org)> i'm interested since the Pico W has the wifi chip connected with shared CIPO/COPI, but is it common enough that we need a special trait for it?

04:46 <re_irc> <GrantM11235> I think it is fairly common. It is also called three wire spi https://en.wikipedia.org/wiki/Serial_Peripheral_Interface#Three-wire_serial_buses

09:04 <re_irc> <ryan-summers> Yeah, but you could only ever use it in half duplex mode or full duplex mode. There's no real such thing as two half-duplex SPIs, so the only thing you get out of it is no "read()" or "write()" function, which is easy enough to do in a driver

11:02 <re_irc> <Udayakumar Hidakal> Hello all,

11:02 <re_irc> Now i am reading about "async" and "await" pattern, So is there any examples for that please let us know.

11:04 <re_irc> <K900> Specifically for embedded you probably want https://embassy.dev/

11:06 <re_irc> <Udayakumar Hidakal> K900: Thank you, will go through this blog.

11:08 <re_irc> <aktaboot> Blog ? 🤔

11:16 <re_irc> <henrik_alser> Udayakumar Hidakal: https://github.com/embassy-rs/embassy/tree/master/examples

11:56 <re_irc> <matejcik> are cargo examples supposed to work with embedded / nostd?

11:56 <re_irc> i have a staticlib crate and I want to create an example so that I can use "cargo-call-stack" on the library.

11:56 <re_irc> the example is refusing to compile because it doesn't see the main crate -- when I just "use mycrate::something", then "mycrate" is undeclared or unresolved; when I add "extern crate mycrate", which shouldn't be needed since like 2018 ? then I get "can't find crate"

12:17 <re_irc> <matejcik> apparently this feature dislikes "staticlib" build.

12:17 <re_irc> <matejcik> +when I remove that from cargo.toml, the example builds fine

12:51 <re_irc> <chrysn (@chrysn:matrix.org)> Is there any simple way for crates that advertise they're no_std to check whether they actually are?

12:52 <re_irc> <chrysn (@chrysn:matrix.org)> I've time and again seen dependencies (or even badly ifdef'd "extern crate alloc"/"std" conditional code) being pulled in, and it has always only shown once I'm actually building for embedded.

13:03 <re_irc> <chrysn (@chrysn:matrix.org)> (One concrete pitfall I kind of expect to trigger is that all crates used in writing proc macros are not dev dependencies but actual ones, and while all their use of std can be gated to "cfg(proc_macro)", if any of them enabled a std feature of another crate that's also used somewhere else in the tree, then resolver=2 wouldn't save the day because it's all in the same tree.)

15:12 <re_irc> <explodingwaffle101> how are you meant to use delay in a driver?

18:01 <re_irc> <adamgreig> hi room, meeting time again! agenda is https://hackmd.io/jVo9nr5BTEW13iUVT1dRbA, please add anything you'd like to announce or discuss and we'll start in 5 min

18:04 <re_irc> <adamgreig> ugh, it's too hot here, there's been a bunch of rust-embedded github activity this week but I can't remember anything that obviously needs discussing, so please do add anything you can think of

18:06 <re_irc> <therealprof> I have nothing. It's not only hot here but I also managed to pick up the flu, yay!

18:07 <re_irc> <adamgreig> all I have is a quick announcement that svd v0.14 is out

18:07 <re_irc> <adamgreig> ugh, get well soon!

18:09 <re_irc> <therealprof> adamgreig: Almost over, it's a bit sad not being to enjoy a cold brew and instead having to reside to hot tea... 😉

18:11 <re_irc> <adamgreig> there was a new issue on cortex-m-rt about overriding the exception table, which has come up a couple of times for devices with non-standard "write some stuff to flash around/in the vector table" config https://github.com/rust-embedded/cortex-m/issues/445

18:11 <re_irc> <adamgreig> I guess the answer is "use your own linker script" basically

18:11 <re_irc> <adamgreig> it's maybe niche enough that it doesn't make sense to add a hook to c-m-rt for this, though I haven't really thought what such a thing would look like

18:12 <re_irc> <therealprof> Ugh, those Infineon micros pop up now and then, huh? I thought that was addressed already by someone many moons ago...

18:15 <re_irc> <adamgreig> I expect by just using a local link.x

18:15 <re_irc> <therealprof> Maybe, there's even a PAC and HAL for it... https://crates.io/crates/xmc1100-hal

18:15 <re_irc> <therealprof> Worth a closer look?

18:16 <re_irc> <adamgreig> https://github.com/david-sawatzke/xmc1100-hal/blob/master/xmc.x.in

18:17 <re_irc> <adamgreig> nice, I've linked to that in the github issue

18:26 <re_irc> <adamgreig> ok, let's leave it there this week, back to lying in front of a fan and sipping cold water...

18:27 <re_irc> <therealprof> Hot tea for me. 😉