emerent has quit [Ping timeout: 256 seconds]
emerent has joined #rust-embedded
richbridger has joined #rust-embedded
aquijoule_ has quit [Read error: Connection reset by peer]
fabic has joined #rust-embedded
starblue has joined #rust-embedded
starblue3 has quit [Ping timeout: 256 seconds]
<re_irc> <@t​halesfragoso:m​atrix.org> > The firmware is an RTIC based application written in Rust.
<re_irc> <@f​irefrommoonlight:m​atrix.org> Nice
<re_irc> <@c​ecton:m​atrix.org> hey 👋 I'm currently working on a crate to do the host communication for DFU in Sans IO and I would like my core crate to be no_std. I made it so but I'm not sure about the error handling. It would be great if someone could give me a few pointers. [This is what I currently have...
<re_irc> ... done.](https://github.com/dfu-rs/dfu-core/commit/f0db2d3b7d50f7c6613e2f277bb0e6f5a794a3d8) I still need to allow the dev to handle errors so I made error enums without the Error impl (but still with Debug). (Any critic is of course welcome! ♥️)
<re_irc> <@g​rantm11235:m​atrix.org> Check out [displaydoc](https://crates.io/crates/displaydoc) as a replacement for thiserror, it is no_std compatible
fabic has quit [Ping timeout: 256 seconds]
fabic has joined #rust-embedded
<re_irc> <@c​ecton:m​atrix.org> GrantM11235: Thanks!!
fabic_ has joined #rust-embedded
fabic has quit [Ping timeout: 258 seconds]
fabic has joined #rust-embedded
fabic_ has quit [Ping timeout: 272 seconds]
tokomak has joined #rust-embedded
fabic has quit [Ping timeout: 240 seconds]
edm has joined #rust-embedded
fabic has joined #rust-embedded
fabic has quit [Ping timeout: 272 seconds]
<re_irc> <@v​irtualritz:m​atrix.org> What's the easiest way to install gdb-multiarch on a mac?
<re_irc> <@9​names:m​atrix.org> looks like the homebrew recipe is a multiarch build by default, have you tried that?
fabic has joined #rust-embedded
GenTooMan has quit [Remote host closed the connection]
GenTooMan has joined #rust-embedded
fabic has quit [Ping timeout: 252 seconds]
<re_irc> <@f​irefrommoonlight:m​atrix.org> Hey dudes. How do you connect to logic analyzers (or scopes) in practice? The cheap Chinese ones, and Salae both appears to use 2.54MM pins, like you'd use with a breadboard. Works great for dev boards, but I'm not sure how to approach this with custom boards. One approach would be an adapter between...
<re_irc> ... 2.54mm and a header suitable for your board. Another is to incorporate 2.54mm headers on your board, but IMO they're too chunky
<re_irc> <@f​irefrommoonlight:m​atrix.org> I was considering something like an adapter for tag-connect, or perhaps a custom device that connects to a board using a footprint like Tag-connect, and outputs to PC with USB, then connects to Sigrok etc. Idea is, you'd design this small-pitch, 2-layer footprint into your board, and wire it up to your...
<re_irc> ... SDA, I2C, UART, and a few digi/analog lines. Then you plug it into a small logic-analyser device, which plugs into your PC via USB
<re_irc> <@f​irefrommoonlight:m​atrix.org> Ie an incremental improvement for ease-of-use
<re_irc> <@f​irefrommoonlight:m​atrix.org> Scope as personal, and if it really works, sell it
<re_irc> <@f​irefrommoonlight:m​atrix.org> I realize building dev tools like this are a bit of a self-licking icecream cone of building embedded devices for embedded devices. But, I'm looking for a way to easily troubleshoot SPI etc issues on all my boards going fwd
<re_irc> <@d​irbaio:m​atrix.org> typically you put testpads on every line that could be interesting to scope all over the board
<re_irc> <@d​irbaio:m​atrix.org> if the board is complex bringing all the interesting lines to one place where you connect a tagconnect is hard
<re_irc> <@f​irefrommoonlight:m​atrix.org> The point you bring up may make this impractical as a general solution
<re_irc> <@f​irefrommoonlight:m​atrix.org> Re test points - how do you then connect the test points to your scope or analyser?
<re_irc> <@f​irefrommoonlight:m​atrix.org> bed-of-nails jig?
<re_irc> <@d​irbaio:m​atrix.org> for development just solder to it 🤣
<re_irc> <@d​irbaio:m​atrix.org> or there are octopus magnetic flexy things you can use to hold a pin against the testpoint
<re_irc> <@s​tarblue:m​atrix.org> To connect to QFP packages I use these: http://www.mechano.co.jp/pdle2.html
<re_irc> <@d​irbaio:m​atrix.org> for factory programming/testing, bed of nails or tagconnect
<re_irc> <@f​irefrommoonlight:m​atrix.org> Hrm.
<re_irc> <@f​irefrommoonlight:m​atrix.org> I guess I'm hoping for more of a no-fuss solution
<re_irc> <@s​tarblue:m​atrix.org> You can solder old resistors to test points and cut off the other wire, helps to keep the clip in place.
<re_irc> <@f​irefrommoonlight:m​atrix.org> (What triggered this specific thing is trying to figure out why the hell my DAC output is reading 1/3 of what it should on some boards but not others)
<re_irc> <@d​irbaio:m​atrix.org> pcb troubleshooting is inherently fussy 🤣
<re_irc> <@f​irefrommoonlight:m​atrix.org> (Almost surely I fucked up teh soldering somewhere)
<re_irc> <@f​irefrommoonlight:m​atrix.org> URG
<re_irc> <@f​irefrommoonlight:m​atrix.org> Yeah
<re_irc> <@f​irefrommoonlight:m​atrix.org> OK solved by soldering on a new MCU I hate this so much
<re_irc> <@f​irefrommoonlight:m​atrix.org> (But I still want a no-fuss logic-analyzing solution. Maybe bake the flash pins into it too)
tokomak has quit [Read error: Connection reset by peer]
<re_irc> <@d​khayes117:m​atrix.org> firefrommoonlight: https://usd.saleae.com/products/pcbite-kit
<re_irc> <@f​irefrommoonlight:m​atrix.org> That looks outstanding
<re_irc> <@l​ovesegfault:m​atrix.org> Curious, does someone know why in Rust the target is called `armv7-unknown-linux-musleabihf` but on Nix it's called `armv7l-unknown-linux-musleabihf`?
<re_irc> <@d​irbaio:m​atrix.org> target names aren't standardized anywhere, and are a fun mess overall :D
<re_irc> <@d​irbaio:m​atrix.org> the "L" there indicates little-endian, I guess rust assumes it's little endian as big endian arm is super rare
<re_irc> <@l​ovesegfault:m​atrix.org> Ah, I see :)
<re_irc> <@t​hejpster:m​atrix.org> Pcbites are amazing. I bought one at work. We got two more very shortly after.
dreamcat4 has quit [Ping timeout: 250 seconds]
SanchayanMaity has quit [Ping timeout: 272 seconds]
<re_irc> <@f​irefrommoonlight:m​atrix.org> Tempting
edm has quit [Ping timeout: 272 seconds]
edm has joined #rust-embedded
dreamcat4 has joined #rust-embedded
SanchayanMaity has joined #rust-embedded
rektide_ has quit [Remote host closed the connection]
<re_irc> <@t​herealprof:m​atrix.org> Adam and I have them, too. 😉
<re_irc> <@l​achlansneff:m​atrix.org> I made a post on irl about the core::io traits and trait aliases: https://internals.rust-lang.org/t/let-trait-aliases-be-used-in-impls-or-how-to-add-io-read-write-to-libcore/14975
<re_irc> <@b​radleyharden:m​atrix.org> Have people seen the [blog post](https://blog.rust-lang.org/inside-rust/2021/07/01/What-the-error-handling-project-group-is-working-towards.html) about the direction of error handling? Looks like the `Error` trait is moving to `core`