troth has quit [Ping timeout: 264 seconds]
<re_irc> <> something wrong with `tinybmp`/its dependencies?
<re_irc> <> Checking memchr v2.3.4
<re_irc> <> error[E0463]: can't find crate for `std`
<re_irc> <> ❯ cargo check
<re_irc> <> are you using edition=2021?
<re_irc> <> or resolver=2? (needed if you're using a workspace even if you're on rust2021...)
troth has joined #rust-embedded
<re_irc> <> a-ha! Yes, I am.
<re_irc> <> you need resolver=2 in the [workspace] cargo.toml
<re_irc> <> can you paste the output of `cargo tree --format '{p} {f}'`?
<re_irc> <> `resolver = "2"` fixed it, thx!
<re_irc> <> ah :D
<re_irc> <> I keep forgetting this has changed, this is the first time I'm running into actual problems
troth has quit [Ping timeout: 256 seconds]
troth has joined #rust-embedded
fabic has joined #rust-embedded
troth has quit [Ping timeout: 268 seconds]
troth has joined #rust-embedded
PyroPeter has quit [Ping timeout: 250 seconds]
starblue has quit [Ping timeout: 265 seconds]
PyroPeter has joined #rust-embedded
starblue has joined #rust-embedded
emerent has quit [Ping timeout: 250 seconds]
emerent has joined #rust-embedded
jackneilll has joined #rust-embedded
jackneill has quit [Ping timeout: 240 seconds]
PyroPeter has quit [Ping timeout: 268 seconds]
PyroPeter has joined #rust-embedded
troth has quit [Ping timeout: 256 seconds]
troth has joined #rust-embedded
fabic has quit [Ping timeout: 268 seconds]
<re_irc> <> Thankfully resolver="2" is default for the 2021 edition
_whitelogger has quit [Ping timeout: 264 seconds]
_whitelogger has joined #rust-embedded
<re_irc> <> I have a driver where there can be an SPI error or a GPIO error. How do I consolidate the 2 errors? On hosted I would just use thiserror. How to do this on no_std?
<re_irc> <> Just create an enum and do the From<T> for the error types yourself
<re_irc> <> ok, was hoping not to do that but i guess it's fine
<re_irc> <> With only 2 variants, it's probably fine ;)
<re_irc> <> would you mind pointing me to an example of this? I get a feeling 4 generic parameters are not required here
<re_irc> <> Well... It depends. Maybe you need it?
<re_irc> <> that looks pretty spot on like what I need :D down to the type names
<re_irc> <> Yeah, they're all usually pretty similar :P
fabic has joined #rust-embedded
<re_irc> <> PSA: A new alpha release of `embedded-hal` 1.0.0 is out: [1.0.0-alpha.6]( 🎉
<re_irc> <> Really cool to see that the CAN traits have been added. Does anyone know what the plan is e.g. for `bxcan` will this migrate from embedded-can to the embedded-hal crate once embedded-hal 1.0.0 is stable?
<re_irc> <> Hey everyone, I'm starting my master's thesis next semester in Energy and Electro-Mechanical Systems. I'm looking to focus on embedded systems broadly related to energy. Looking to incorporate some PCB design. Anyone have any suggestions on some related areas with gaps in knowledge/research opportunities?
<re_irc> <> Christopher Hunt: I believe you are working on an EV charger.
<re_irc> <> I wanted to focus on RISC-V + Rust for my thesis, but the department chair said it was too far out of their expertise. I plan on sneaking it in anyways, just not as the primary topic 😉
<re_irc> <> If anybody comes across something before I do, feel free to hit me up on twitter `dkhayes117`
<re_irc> <> If you'd want to build on something preexisting and liked stepper motor control, I believe you could have a look at this. (a bit of a shameless plug with my master's)
<re_irc> <> I think I remember seeing your post about that on twitter a while back 😀
<re_irc> <> I thought a little about looking into Silicon-Carbide FET based converters.
<re_irc> <> Or GaN
<re_irc> <> What voltages do you have in mind?
<re_irc> <> Or powers?
<re_irc> <> Well not sure, I'm pretty open-minded right now. I liked the idea of higher efficiencies and smaller footprints that Sic/GaN can offer. I thought about maybe doing a power supply for a computer server.
<re_irc> <> I understand, have you thought about e.g. USB-C PD supply? There are several voltages, up to 250 W power, etc. You could extend it with some USB peripherals, like an ethernet bridge, or USB hub.
<re_irc> <> Cool, cool. I will keep that mind. I also like IoT stuff as well. Ah, so many choices!
troth has quit [Ping timeout: 264 seconds]
troth has joined #rust-embedded
fabic has quit [Ping timeout: 264 seconds]
<re_irc> <> very out of the loop here: is there any desire/project to rework SPI transfers so they can be either blocking or DMA?
<re_irc> <> in a specific HAL or in the embedded-hal traits or..?
<re_irc> <> Regarding alpha6: Is there a reason the Error traits (eg. `spi::Error`) are not implemented for `Infallible`?
<re_irc> <> `type Error = Infallible;` was quite convenient for device implementations which don't return any errors.
<re_irc> <> jannic: to me this sounds like it absolutely should be done! Similar with `void::Void` probably?
<re_irc> <> Since 1.0.0-alpha.1, embedded-hal doesn't depend on void, so adding this implementation would require reintroducing the dependency.