lekernel changed the topic of #milkymist to: Mixxeo, Migen, Milkymist-ng & other Milkymist projects :: Logs: http://en.qi-hardware.com/mmlogs :: Mixxeo preorder lists.milkymist.org/pipermail/devel-milkymist.org/2013-May/003344.html
antgreen has quit [Ping timeout: 252 seconds]
antgreen has joined #milkymist
antgreen has quit [Ping timeout: 256 seconds]
antgreen has joined #milkymist
proppy__ is now known as proppy
sh4rm4 has quit [Ping timeout: 252 seconds]
Martoni has joined #milkymist
sh4rm4 has joined #milkymist
lekernel has joined #milkymist
qwebirc40651 has joined #milkymist
qwebirc40651 has quit [Ping timeout: 250 seconds]
lekernel has quit [Quit: Leaving]
lekernel has joined #milkymist
<lekernel>
great project management from libftdi... I sent an email at the address at the beginning of the source files about the broken error reporting, and got an answer telling me to (1) use the mailing list (2) check git head (where the problem isn't fixed, either)
<Fallenou>
^^
<lekernel>
ie. "I'm (1) too lazy too follow this up myself, and I (2) won't even check the git repos and simply assume you didn't"
<lekernel>
and won't even update the contact info in the source, too
<kyak>
at least you got a reply
<larsc>
I think the first one is a reply you'd get rather often
bhamilton has joined #milkymist
bhamilton has quit [Quit: Leaving.]
bhamilton has joined #milkymist
lekernel has quit [Ping timeout: 256 seconds]
lekernel has joined #milkymist
bhamilton has quit [Quit: Leaving.]
bhamilton has joined #milkymist
bhamilton has quit [Client Quit]
bhamilton has joined #milkymist
bhamilton has quit [Quit: Leaving.]
bhamilton has joined #milkymist
sh4rm4 has quit [Ping timeout: 252 seconds]
sh4rm4 has joined #milkymist
<wpwrak>
as far as (2) goes, i think statistics are in favour of that assumption :)
<wpwrak>
(making diodes) nice. now you just need a transistor and then you're all set to switch from FPGAs to XXL-ASICs :)
<Fallenou>
XXL toasters
<Fallenou>
well, toasters can run NetBSD, don't they? :)
<wpwrak>
if you time it right, you'll have no heating costs to worry about next winter :)
<Fallenou>
;)
antgreen has quit [Ping timeout: 245 seconds]
bhamilton1 has joined #milkymist
bhamilton1 has quit [Read error: Connection reset by peer]
bhamilton has quit [Read error: Connection reset by peer]
bhamilton has joined #milkymist
<lekernel>
hmm, the CCFL driver from my dead laptop doesn't like the plasma tube - can't generate enough voltage
<lekernel>
I wonder how effective the "protection" (advertised in the control IC datasheet) against open lamp is - apparently the thing can sustain arcs in air indefinitely without tripping the protection :)
<lekernel>
it only trips when the electrodes are so far apart that the arc cannot start
<lekernel>
I wonder what this is supposed to protect...
bhamilton1 has joined #milkymist
bhamilton has quit [Read error: Connection reset by peer]
qi-bot has quit [Ping timeout: 256 seconds]
Martoni has quit [Quit: ChatZilla 0.9.90 [Firefox 20.0/20130329043827]]
antgreen has joined #milkymist
bhamilton has joined #milkymist
bhamilton1 has quit [Read error: Connection reset by peer]
<lekernel>
it's an internal signal that you get out of the fpga, and depending on the output pin it looks different?
<lekernel>
this just looks like normal transmission line ringing to me
<lekernel>
one trace is probably shorter or better matched than the other?
<lekernel>
if you're measuring at the pin, note that most BGA packages actually contain a bit of PCB with traces connecting the balls to the chip. but this usually only plays at higher frequencies.
<larsc>
but should it be that bad, there is up to 80% overshoot, while the other looks perfect
<larsc>
series resistor makes the ripple go away, maybe I'll just go with that instead of trying to figure out what's causing the effect
antgreen has quit [Remote host closed the connection]
bhamilton has quit [Read error: Connection reset by peer]
bhamilton1 has joined #milkymist
bhamilton1 has quit [Read error: Connection reset by peer]
antgreen has joined #milkymist
<lekernel>
how long are your traces?
<lekernel>
and have you tried using a slow slew rate?
<lekernel>
SLEW=SLOW or SLEW=QUIETIO
<lekernel>
remember 1ns rise time is ca. 1GHz, and you seem to be below 1ns ...
<larsc>
slew is slow and drive strength is minimum
<lekernel>
doesn't look that slow to me
<lekernel>
the signal period is 16ns, right?
<lekernel>
how different are the two traces?
<larsc>
period should be 32ns
<lekernel>
and how long are they?
<larsc>
good question
<lekernel>
power/ground plane voids can also cause impedance mismatches and this little mess
<larsc>
the signals are on different IO banks
<larsc>
traces should be about the same length
<larsc>
going into different directions though
<lekernel>
also, I believe it is safe to assume massive process (and voltage/temperature) variation on slew rate on different slowtan IO pins
<lekernel>
even many things that Xilinx characterize have 300+% PVT, and AFAIR they did not characterize slew rate
<lekernel>
power/ground planes can also affect trace impedance in a significant way
<lekernel>
even if the traces have the same length
<lekernel>
s/length/geometry
<lekernel>
and power plane void = impedance mismatch on all traces that cross the void
<larsc>
hm ok
<larsc>
thanks
<lekernel>
did you compare a second board?
<larsc>
not yet
<lekernel>
btw if you find some hard numbers on slowtan slew rates, I'd be happy to learn about them...
<larsc>
actually my next step was to try a different board with the same fpga
<larsc>
this is a series7
<lekernel>
your slew rate really seems quite fast... try zooming on it using the signal that looks good
<lekernel>
then you have an idea of what kind of frequency the traces are supposed to handle without excessive ringing
bhamilton has joined #milkymist
bhamilton has quit [Quit: Leaving.]
antgreen has quit [Quit: Leaving]
Alarm_ has joined #milkymist
Alarm_ has quit [Quit: ChatZilla 0.9.90 [Firefox 21.0/20130511120803]]