home.social

Search

27 results for “TalesFromTheArmchair”

  1. Wow, someone's successfully targeted my embedded Rust USB host stack to *EHCI*. That's, like, a *real* host controller... github.com/imxrt-rs/imxrt-usbh #rustlang #embeddedrust #rustembedded

  2. @dotstdy I've definitely used such compilers in the past. Their apparent attitude was, "#include includes exactly the bytes of that file into the translation unit at this point", so if the included file didn't end with a newline, it effectively concatenated the next input line onto the end of the final "line" of the included file. And because most header files end with "#endif", and most compilers ignore any junk on the same line following an "'#endif", it effectively ignored the next input line completely, causing confusing errors.

  3. Today's waypoint on my #Rust journey: a new crate, implementing #SSDP client and server, which depends on my other crate. For instance, this is what you want if you're implementing #upnp, which I might have a go at later on github.com/pdh11/cotton/tree/m

  4. Just found myself writing a function with the signature fn control_transfer_ok_with<F: FnMut(&mut [u8]) -> usize>(
    mut f: F,
    ) -> impl FnMut(
    u8,
    u8,
    SetupPacket,
    DataPhase,
    ) -> Pin<Box<dyn Future<Output = Result<usize, UsbError>>>> and am now going to go and touch grass for a bit, kthxbye. It cut 200 lines of boilerplate out of my unit tests, though! #rust #rustLang #asyncRust

  5. git commit -m"Really quite surprised that this compiles; committing it rn before the compiler changes its mind"
    #Rust #RustLang #AsyncRust

  6. So I think I got my head around async/await in #Rust, and I also know how IRQs work on embedded systems. But it was oddly hard to find a good article on exactly how to join up those two bits of knowledge: how to ".await" where what you're waiting for is an IRQ happening ("transfer complete", for instance). This article, though, was great and cleared it all up: interrupt.memfault.com/blog/em (it talks about #Embassy but I bet it works the same in #rtic 2)

  7. When we were little, my brother and I had a lot of Space Lego #Lego #SpaceLego #VintageLego

  8. 1979 model, several billion squillion light-years on the clock, one careful owner from new #Lego #SpaceLego #VintageLego

  9. The official reference manual for the RP2040 says that the I2C protocol was originally defined "in the Dead Sea Scrolls" and gleefully declares the PIO peripheral to be Turing-complete after showing that it can add two 32-bit integers in under a minute. Basically the whole thing reads like 20something me wrote it, and I'm here for that. #raspiPico #rp2040

  10. Peter Hartley @TalesFromTheArmchair ·

    If this doesn't stir something in you, I might have bad news about your inner child

  11. So I think I got my head around async/await in #Rust, and I also know how IRQs work on embedded systems. But it was oddly hard to find a good article on exactly how to join up those two bits of knowledge: how to ".await" where what you're waiting for is an IRQ happening ("transfer complete", for instance). This article, though, was great and cleared it all up: interrupt.memfault.com/blog/em (it talks about #Embassy but I bet it works the same in #rtic 2)

  12. Peter Hartley @TalesFromTheArmchair ·

    So I think I got my head around async/await in , and I also know how IRQs work on embedded systems. But it was oddly hard to find a good article on exactly how to join up those two bits of knowledge: how to ".await" where what you're waiting for is an IRQ happening ("transfer complete", for instance). This article, though, was great and cleared it all up: interrupt.memfault.com/blog/em (it talks about but I bet it works the same in 2)

  13. So I think I got my head around async/await in #Rust, and I also know how IRQs work on embedded systems. But it was oddly hard to find a good article on exactly how to join up those two bits of knowledge: how to ".await" where what you're waiting for is an IRQ happening ("transfer complete", for instance). This article, though, was great and cleared it all up: interrupt.memfault.com/blog/em (it talks about #Embassy but I bet it works the same in #rtic 2)

  14. So I think I got my head around async/await in #Rust, and I also know how IRQs work on embedded systems. But it was oddly hard to find a good article on exactly how to join up those two bits of knowledge: how to ".await" where what you're waiting for is an IRQ happening ("transfer complete", for instance). This article, though, was great and cleared it all up: interrupt.memfault.com/blog/em (it talks about #Embassy but I bet it works the same in #rtic 2)

  15. Peter Hartley @TalesFromTheArmchair ·

    Today's waypoint on my journey: a new crate, implementing client and server, which depends on my other crate. For instance, this is what you want if you're implementing , which I might have a go at later on github.com/pdh11/cotton/tree/m

  16. Every time I run "cargo test-all-features" I'm mentally doing it in the voice of General Kala from Flash Gordon #rust #NicheReference

  17. Peter Hartley @TalesFromTheArmchair ·

    Every time I run "cargo test-all-features" I'm mentally doing it in the voice of General Kala from Flash Gordon