feldim2425 has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
feldim2425 has joined #amaranth-lang
<_whitenotifier-b>
[amaranth] whitequark opened pull request #968: Expand flipped object forwarding in `lib.wiring` to respect `@property` and `del` - https://github.com/amaranth-lang/amaranth/pull/968
<_whitenotifier-b>
[amaranth-lang/amaranth-lang.github.io] github-merge-queue[bot] 20274d4 - Deploying to main from @ amaranth-lang/amaranth@74e613b49d89356db73687fd2f0bbd8290158291 🚀
nelgau has quit [Read error: Connection reset by peer]
<vipqualitypost[m>
any time I just try to `m.d.sync += anodes.eq(some_value)` that fits in the width of anodes.
<vipqualitypost[m>
I did this before in a different project and it worked but that was older version of amaranth. did something change that I'm missing?
<Wanda[cis]>
hahahahah.
<Wanda[cis]>
beautiful.
<vipqualitypost[m>
is it something obvious again 😢
<Wanda[cis]>
nah, just... we overdosed horrible Python hacks and broke the language a little
<Wanda[cis]>
(it's a bug on our part)
<Wanda[cis]>
but: the thing you're doing is actually deprecated, and amaranth crashes when trying to print out the deprecation warning
<Wanda[cis]>
(or rather, shortly after it)
<galibert[m]>
Shouldn’t it be anodes.o or something?
<Wanda[cis]>
yup
<Wanda[cis]>
anodes.o.eq
<Wanda[cis]>
because a pin is a triple of three signals, and you need specifically the output data
<Wanda[cis]>
it... happened to work by accident with anodes.eq
<vipqualitypost[m>
right! i was reading through that earlier conversation on the DDR or SDRAM but didn't think to try the same things here
<vipqualitypost[m>
great, it seems happier now!
<galibert[m]>
i/o/oe, it’s not just a good idea, it’s the law !
<galibert[m]>
(or something)
<vipqualitypost[m>
so anodes.oe should also be specified on dir="o" pins?
<galibert[m]>
No
<galibert[m]>
But it’s there
<galibert[m]>
It’s set to 1 for o pins and 0 for I pins so you don’t need to touch it
<vipqualitypost[m>
so is oe only used on bidirectional pins in that case?
<galibert[m]>
Yes
<vipqualitypost[m>
makes sense. thank you Wanda and galibert!