Greg Davill

Understood. Unfortunately I don't seem to have any photos when the original fault occurred that show the fuse holder, so it's not easy to check to see if it was...

This has been on my list to do for awhile. So Tom took the lead, I'll go through and review later. I can do tests on hardware too. One question...

Sure! Here is a good reference for all the SYZYGY pins: https://github.com/butterstick-fpga/test-fixture-sw/blob/main/gateware/rtl/platform/butterstick_r1d0.py#L52-L54 This is what I'll be basing the LiteX boards platform file on.

I'm not familiar enough with OSX's drivers to have any extra insight on this unfortunately.

Gave this a spin. It's not working exactly right. I can compile an example project, but loading it fails. The main issue is that my PC's has an internal dfu...

Has this now been fixed with the introduction of picolibc? I see that `-flto` is a default enabled option with the current upstream code.

Brainstorming sounds like a good idea. One idea, which I think could work in practice, but may be not very elegant. The initial command which creates the multiple applets, also...

You could just specify run multiple times? ``` glasgow run uart --pin-rx 1 --pin-tx 0 -V 3.3 -b 115200 pty run uart --pin-rx 2 --pin-tx 3 -b 115200 pty ```

Turn each command into a string? ``` glasgow run "uart --pin-rx 1 --pin-tx 0 -V 3.3 -b 115200 pty" "uart --pin-rx 2 --pin-tx 3 -b 115200 pty" ``` So argparse...

Yep, bitarray is not needed. I was poking around with it to try to handle the bit reversal. I'll remove the import Thanks for the comments! I'll work through them...