whitequark[cis] changed the topic of #glasgow to: https://glasgow-embedded.org · digital interface explorer · https://www.crowdsupply.com/1bitsquared/glasgow · code https://github.com/GlasgowEmbedded/glasgow · logs https://libera.irclog.whitequark.org/glasgow · matrix #glasgow-interface-explorer:matrix.org · discord https://1bitsquared.com/pages/chat
notgull has joined #glasgow
<whitequark[cis]> <wklaebe> "hmm... I wonder how hard it will..." <- pretty hard
davidrysk[m] has quit [Quit: Idle timeout reached: 172800s]
notgull has quit [Ping timeout: 264 seconds]
trh has quit [Quit: weg]
trh has joined #glasgow
<whitequark[cis]> same problem
<whitequark[cis]> the voltage there is 1.1 V
<whitequark[cis]> the level shifters don't go that low
WilfriedKlaebe[m has joined #glasgow
<WilfriedKlaebe[m> <whitequark[cis]> "pretty hard" <- Uh. Would it be easier to just sniff the conversation on the CC line?
galibert[m] has quit [Quit: Idle timeout reached: 172800s]
<theorbtwo[m]> Oh! Somehow, I thought they would go arbitrarily low.
stary[m] has joined #glasgow
<stary[m]> looks like even at the edge of the minimum spec it's just about a miss - 1.65v min vcc, then V_ih is 0.65*vcc for 1.0725v
<stary[m]> but that's only sniffing, not actually carrying out your own pd transactions
josuaH[m] has quit [Quit: Idle timeout reached: 172800s]
<whitequark[cis]> what you could do is ac-couple it
<whitequark[cis]> like, bias the input to always be at Vcc/2, then couple the PD input (which is DC-balanced for inscrutable historical reasons) into it
<whitequark[cis]> you'll be able to get captures quite easily
<whitequark[cis]> note that that 1.1V actually depends on whether the device is a source or a sink (again for inscrutable USB reasons)
<whitequark[cis]> so you really do want AC coupling
<theorbtwo[m]> Most inscrutable usb reasons are "we don't want to add more pins", I think.
<theorbtwo[m]> You probably know better than me, sorry.
Foxyloxy_ has joined #glasgow
nemanjan00[m] has quit [Quit: Idle timeout reached: 172800s]
Foxyloxy_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Foxyloxy_ has joined #glasgow
Foxyloxy_ has quit [Client Quit]
galibert[m] has joined #glasgow
<galibert[m]> Isn't USB-PD a RF protocol without the RF?
<galibert[m]> (which is as insane as it reads, yes)
<whitequark[cis]> but it still is 4b5b encoded
<whitequark[cis]> presumably because they wanted to reuse existing ASICs by just cutting in before the modulator/demodulator
redstarcomrade has joined #glasgow
<WilfriedKlaebe[m> "or 24MHz BFSK on the Vbus line" sounds RF to me 😅
<galibert[m]> yeah but wit the central frequency at 0Hz
<galibert[m]> s/wit/with/
<whitequark[cis]> I think it had like 21.4 MHz?
<galibert[m]> That would be before they un-RFed it, right?
redstarcomrade has quit [Read error: Connection reset by peer]
huntersvonnegut[ has quit [Quit: Idle timeout reached: 172800s]
omnitechnomancer has quit [Quit: Idle timeout reached: 172800s]
<whitequark[cis]> am i insane or is openocd awful at documenting their behavior?
<whitequark[cis]> if i'm using adapter assert [trst|srst], i get different polarities for the two signals
<whitequark[cis]> nothing anywhere i can see in the code makes this legible either
<whitequark[cis]> oh, i see what happened
<whitequark[cis]> openocd is fine, but my board has active-high SRST instead of the expected active-low one
<WilfriedKlaebe[m> should be labeled NSRST then?
<whitequark[cis]> I guess what openocd does is document logical polarity for TRST/SRST
<whitequark[cis]> this is actually not unreasonable
<whitequark[cis]> it would have helped if this doc or https://github.com/openocd-org/openocd/blob/master/src/jtag/interface.h#L241-L255 would have said that "TRST/SRST are usually active-low" or something like that
<whitequark[cis]> especially given that every board will have nTRST low but SRST will vary in practice
<whitequark[cis]> ... actually no it's worse
<whitequark[cis]> so r,s,t,u correspond to srst,trst=00,01,10,11
<whitequark[cis]> free inversion!
<whitequark[cis]> (if you incorrectly assume that the two low bits are the states of the signals, like everything else in the remote_bitbang protocol does)
<_whitenotifier-9> [glasgow] whitequark opened pull request #590: Enable the use of Amaranth 0.5 new I/O - https://github.com/GlasgowEmbedded/glasgow/pull/590
<_whitenotifier-9> [glasgow] whitequark synchronize pull request #586: [WIP] An applet for controlling a quad-SPI (QSPI/QPI) bus - https://github.com/GlasgowEmbedded/glasgow/pull/586
<_whitenotifier-9> [glasgow] whitequark commented on pull request #590: Enable the use of Amaranth 0.5 new I/O - https://github.com/GlasgowEmbedded/glasgow/pull/590#issuecomment-2185096737
notgull has joined #glasgow
notgull has quit [Ping timeout: 260 seconds]
<_whitenotifier-9> [glasgow] wanda-phi reviewed pull request #590 commit - https://github.com/GlasgowEmbedded/glasgow/pull/590#discussion_r1650158992
qwertyface[m] has quit [Quit: Idle timeout reached: 172800s]
sigstoat[m] has quit [Quit: Idle timeout reached: 172800s]
benny2366[m] has quit [Quit: Idle timeout reached: 172800s]
nf6x[m] has joined #glasgow
<nf6x[m]> Just curious: Are there any plans for the two no-connect pins in future Glasgow revisions which include revC-compatible headers?
redstarcomrade has joined #glasgow
redstarcomrade has joined #glasgow
redstarcomrade has quit [Changing host]
jan2642[m] has quit [Quit: Idle timeout reached: 172800s]
thomasflummer[m] has quit [Quit: Idle timeout reached: 172800s]
duskwuff[m] has quit [Quit: Idle timeout reached: 172800s]
redstarcomrade has quit [Read error: Connection reset by peer]
redstarcomrade has joined #glasgow
redstarcomrade has joined #glasgow
redstarcomrade has quit [Changing host]
gsuberland has joined #glasgow
dos1 has joined #glasgow
andymandias has quit [Ping timeout: 252 seconds]
dos has quit [Ping timeout: 252 seconds]
dos1 is now known as dos
andymandias has joined #glasgow