whitequark changed the topic of #amaranth-lang to: Amaranth hardware definition language · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang
Degi_ has joined #amaranth-lang
Degi has quit [Ping timeout: 260 seconds]
Degi_ is now known as Degi
<_whitenotifier-e> [YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±1] https://github.com/YoWASP/yosys/compare/086154b87ead...f06d85d668d2
<_whitenotifier-e> [YoWASP/yosys] whitequark f06d85d - Update dependencies.
<Degi> mubes: That should work, it should not have any pullups / pulldowns by default. Which board are you using? Any chance that the pin is damaged?
<d1b2> <mubes> It’s our own board, and the whole batch (well, the few we’ve tested) have the same behaviour. This conversation also got going over in #fpga and it’s been suggested it might be being optimised out. Will check that once the dog is walked and errands have been run. Will report back.
<Degi> How do you detect that there is a pulldown?
<d1b2> <mubes> We have a 10K pullup on the pin and its sitting at 2v2
jn has quit [*.net *.split]
gatecat has quit [*.net *.split]
gatecat has joined #amaranth-lang
jn has joined #amaranth-lang
mindw0rk has quit [Quit: ZNC 1.8.2 - https://znc.in]
mindw0rk has joined #amaranth-lang
mindw0rk has quit [Client Quit]
mindw0rk has joined #amaranth-lang
urja has quit [Read error: Connection reset by peer]
<d1b2> <mubes> Just to close this one off, ensuring the pin was pulled into the config and not optimised out fixed the problem (more discussion in #fpga )
urja has joined #amaranth-lang
FL4SHK has quit [Ping timeout: 246 seconds]
<Degi> Interesting that pulling is on by default
lf has quit [Ping timeout: 260 seconds]
lf has joined #amaranth-lang
FL4SHK has joined #amaranth-lang