Catherine
Catherine
> I think it might technically be possible to work around it I guess you could, when targeting older Yosys, always provide a `$divfloor` cell as a part of `nmigen.back.verilog`,...
One problem is that there could actually be shorts on the side of pull drivers too.
Yes, the selftest is completely broken on revC, please stop reiterating this over and over again. I should probably just remove it.
No, we still have to implement some form of selftest on revC. I've renamed the issue.
There is already a (preview quality) SWD applet! There's no actual gdbserver (or flasher) support *right now* mostly because I was going to integrate with @azonenberg's jtaghal, and jtaghal isn't...
That's mostly pointless, it's just more C code I cannot actually distribute with Glasgow itself... Really, the protocol is not very complex.
Update: I will not even try to rely on jtaghal, Glasgow-native gdbserver is superior in every way.
There's a prototype of an SWD applet. What's missing is the actual debugger code. Currently the bottleneck is maintainer time / review bandwidth so there is little you can do...
We should probably have a different issue for SWIM, as far as I remember it's a completely different protocol.
Does openocd have something like the JTAG bitbang interface but for SWD? Anything that works through a socket rather than through libusb would work.