ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
starblue1 has quit [Ping timeout: 246 seconds]
starblue1 has joined #rust-embedded
cinemaSundays has joined #rust-embedded
GuineaWheek[m] has joined #rust-embedded
<GuineaWheek[m]> i like probe-rs on principle but we really do need higher quality gui debuggers for rust
<GuineaWheek[m]> given the previous alternative is $20,000 lauterbach equipment, ozone getting support is still a massive discount and a step in the right direction
<Lumpio-> Is a "gui debugger" one of those standalone things instead of integration with a standard IDE?
AtleoS has quit [Read error: Connection reset by peer]
AtleoS has joined #rust-embedded
cinemaSundays has quit [Quit: Connection closed for inactivity]
<thejpster[m]> Yes
<GuineaWheek[m]> i mean it can be integrated with the standard ide
<GuineaWheek[m]> i'm just not aware of good options for rust though
emerent has quit [Ping timeout: 276 seconds]
emerent has joined #rust-embedded
<Noah[m]> <GuineaWheek[m]> "i'm just not aware of good..." <- Did you try the vscode plugin for probe-rs?
starblue1 has quit [Ping timeout: 265 seconds]
starblue1 has joined #rust-embedded
<thejpster[m]> preview of the next blog post: https://hackmd.io/@thejpster/HJxXTkuRC.
<thejpster[m]> TL;DR: DLSTP/LE rips through loops 16 bytes at a time, with almost zero code overhead, and free handling of the remainder (when it isn't a multiple of 16)
AtleoS has quit [Ping timeout: 255 seconds]
AtleoS has joined #rust-embedded
frostie314159[m] has joined #rust-embedded
<frostie314159[m]> Hi, does anyone know, how I can add a cluster of registers to a patch svd file for svdtools?
AtleoS has quit [Ping timeout: 248 seconds]
AtleoS has joined #rust-embedded
corecode[m] has quit [Quit: Idle timeout reached: 172800s]
<JamesMunns[m]> adamgreig are you still traveling this week?
<Ralph[m]> it'd be great if someone from r-e-c could give this a review if you have some spare time (this is *not* urgent): https://github.com/rust-embedded-community/adafruit-bluefruit-protocol-rs/pull/38
<Ralph[m]> (i tagged eldruin on the PR simply because he's previously reviewed something here - i just didn't want to add everyone and spam all your GH notifications)
diondokter[m] has quit [Quit: Idle timeout reached: 172800s]
adamgreig[m] has joined #rust-embedded
<adamgreig[m]> <JamesMunns[m]> "adamgreig are you still travelin..." <- Yep, last week away
<cr1901> So I'm not quite up-to-date, can someone correct me if I'm wrong: svd2rust uses a Singleton w/ refs to access peripherals. Volatile refs are unsound in Rust and reception for adding them is lukewarm. But the Singleton pattern breaks if not used with Rust. And an alternative aside from "don't use svd2rust if you care about the unsoundness being exploited in the future" hasn't been devised?
<cr1901> if not used w/ refs*
<JamesMunns[m]> chiptool just uses pointers iirc
<dirbaio[m]> yeah you could make a PAC generator that uses pointers like chiptool so it's not affected by the vcell unsoundness, but still uses singletons
<dirbaio[m]> "using singletons or not" and "using pointers or vcell" are orthogonal