tpw_rules has joined ##openfpga
genii has quit [Remote host closed the connection]
futarisIRCcloud has joined ##openfpga
flea86 has joined ##openfpga
_whitelogger has joined ##openfpga
cr1901_web has quit [Ping timeout: 256 seconds]
cr1901_modern1 has joined ##openfpga
cr1901_modern has quit [Ping timeout: 245 seconds]
Laksen has quit [Remote host closed the connection]
gsi__ has joined ##openfpga
gsi_ has quit [Ping timeout: 255 seconds]
GenTooMan has quit [Quit: Leaving]
Bike has quit [Quit: Lost terminal]
flea86 has quit [Read error: Connection reset by peer]
ym has quit [Remote host closed the connection]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
vonnieda has joined ##openfpga
rohitksingh has joined ##openfpga
rohitksingh has quit [Ping timeout: 246 seconds]
futarisIRCcloud has joined ##openfpga
rohitksingh_work has joined ##openfpga
mumptai has joined ##openfpga
<azonenberg> whitequark, lain: sooo i wanted to do a quick demo of glscopeclient for low speed applications
<azonenberg> But now i have more questions than answers
<whitequark> oh?
<lain> :o
<azonenberg> Screenshot coming in a sec
<azonenberg> I'm also debugging an issue where my old lecroy seems to deadlock glscopeclient but only if a certain debug print is commented out
<azonenberg> Anyway, basically it looks ilke there is something nasty combinatorial in the slg46140 (at least) pipe delay block
<whitequark> huh
<azonenberg> it's glitching on the clock edge
gsi__ is now known as gsi_
azonenberg_work has joined ##openfpga
<azonenberg> oh wait
<azonenberg> i derped i think
<azonenberg> that's lut glitching, not pipe delay glitching
<azonenberg> the pipe delay doesnt glitch
<azonenberg> lol
ZombieChicken has quit [Disconnected by services]
forgottenwizard has joined ##openfpga
OmniMancer has joined ##openfpga
<sorear> if you change both inputs to a XOR gate in the same cycle, you'll get a glitch even in standard cell…
Jybz has joined ##openfpga
Jybz has quit [Client Quit]
<azonenberg> yeah i know, i just derped and thought i had done a direct output
<azonenberg> used the wrong signal to the pin :)
forgottenwizard is now known as ZombieChicken
flaviusb has quit [Remote host closed the connection]
m4ssi has joined ##openfpga
jevinskie has joined ##openfpga
_whitelogger has joined ##openfpga
Jybz has joined ##openfpga
rohitksingh has joined ##openfpga
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has joined ##openfpga
rohitksingh has quit [Ping timeout: 255 seconds]
rohitksingh has joined ##openfpga
mumptai has quit [Remote host closed the connection]
rohitksingh has quit [Ping timeout: 244 seconds]
emeb_mac has quit [Ping timeout: 258 seconds]
unkraut has quit [Remote host closed the connection]
Asu has joined ##openfpga
ZombieChicken has quit [Remote host closed the connection]
<mwk> hm, anybody has a clue what is "TML" electrical standard?
<mwk> it's an undocumented IOSTANDARD supported by spartan6, looks like a variant of TMDS
<tnt> never heard of it
unkraut has joined ##openfpga
vonnieda has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
rohitksingh_work has quit [Read error: Connection reset by peer]
vonnieda has joined ##openfpga
genii has joined ##openfpga
rohitksingh has joined ##openfpga
zem has quit [Ping timeout: 252 seconds]
rohitksingh has quit [Ping timeout: 255 seconds]
q3k is now known as oof
oof is now known as q3k
rohitksingh has joined ##openfpga
zem has joined ##openfpga
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
Asu has quit [Ping timeout: 245 seconds]
Asu has joined ##openfpga
emeb has joined ##openfpga
Laksen has joined ##openfpga
m4ssi has quit [Quit: Leaving]
Asu has quit [Remote host closed the connection]
Asu has joined ##openfpga
Jybz has quit [Ping timeout: 258 seconds]
Jybz has joined ##openfpga
Jybz has quit [Client Quit]
Jybz has joined ##openfpga
OmniMancer has quit [Quit: Leaving.]
rohitksingh has quit [Ping timeout: 255 seconds]
rohitksingh has joined ##openfpga
Ultrasauce has quit [Quit: Ultrasauce]
Ultrasauce has joined ##openfpga
galv[m] has quit [Quit: Idle kick: User has been idle for 30 days.]
OmniMancer has joined ##openfpga
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has joined ##openfpga
jevinskie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jevinskie has joined ##openfpga
jevinskie has quit [Client Quit]
<Dolu> azonenberg_work : About java, a funny one is also the arithmetic. Byte | Byte => Int as result expression type XD
Dolu has quit [Ping timeout: 246 seconds]
tms__ has quit [Ping timeout: 268 seconds]
rohitksingh has quit [Ping timeout: 258 seconds]
indy_ has joined ##openfpga
pie___ has joined ##openfpga
Jybz has quit [Quit: Konversation terminated!]
Dolu1990 has joined ##openfpga
cr1901_web has joined ##openfpga
OmniMancer has quit [Quit: Leaving.]
ZombieChicken has joined ##openfpga
GenTooMan has joined ##openfpga
Dolu1942 has joined ##openfpga
Dolu has joined ##openfpga
Dolu1942 has quit [Client Quit]
Dolu1990 has quit [Ping timeout: 252 seconds]
<nats`> ohhhh Dolu :)
<Dolu> Hi nats` XD
<Dolu> How things are going ?
Asu has quit [Ping timeout: 246 seconds]
Asu has joined ##openfpga
vonnieda has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Bike has joined ##openfpga
Asu has quit [Quit: Konversation terminated!]
cr1901_web has quit [Ping timeout: 256 seconds]
bibor has quit [Ping timeout: 252 seconds]
cr1901_web has joined ##openfpga
cr1901_web has quit [Ping timeout: 256 seconds]
futarisIRCcloud has joined ##openfpga
<ZombieChicken> Is is possible to make an FPGA (or similar device) unusable if you feed it an incorrect bitstream?
<sorear> it's *possible* but I've never heard of it being done by accident
<azonenberg_work> ZombieChicken: Hard data point: I destroyed an xc2c32a with a carefully crafted bitstream full of short circuits in one-hot muxes
<ZombieChicken> ty
<ZombieChicken> so it pretty much has to be something intentional
<azonenberg_work> i had to reverse engineer the bitstream, spend some time figuring out which lines to short
<azonenberg_work> and it still took ten minutes to achieve a fatal result
<azonenberg_work> pulling 150+ mA on a rail that should have never consumed more than about 5
<azonenberg_work> Doing it by accident, while not impossible, is improbable
<ZombieChicken> ty
<sorear> so in a real application you'd probably trip an upstream current limiter first
<azonenberg_work> Iffff you did the whole chip
<azonenberg_work> yes
<azonenberg_work> That being said, it's plausible that a single internal bus fight left long enough would blow out a single routing path or lut output or something
<azonenberg_work> rendering the chip still usable but giving bad or inconsistent results for a single gate
<adamgreig> wouldn't that be fun to debug
<azonenberg_work> DRCing of generated bitstreams, to verify that you're not doing anything like that, is definitely a must for a production-grade toolchain
<sorear> how much public intel is there about the DRC mechanisms on aws f1?
<TD-Linux> you don't upload bitstreams to f1
Laksen has quit [Quit: Leaving]
<azonenberg_work> Yeah, they do some partial reconfig magic after compiling your design on their platform through some custom scripts
<azonenberg_work> so i dont think it would be possible to generate an invalid bitstream
<azonenberg_work> Going to guess they block the ICAP
<sorear> I was under the impression f1 generated bitstreams using vivado on the same node that you have root over
<sorear> the safety stuff seems to be largely angled at preventing *external* bus fights with the other components on the card / host