| *** tpb <[email protected]> has joined #litex | 00:00 | |
| somlo | zyp: I'm not really sure of anything at all: so far all I have to go on is an excel spreadsheet with the pin-port mapping and some rather dense verilog that converts the gmii ethernet demo used with the v1 board to rgmii | 01:06 |
|---|---|---|
| somlo | if anything, that's where I might find some answers, once I train my pattern-matching wetware for what to look for :) | 01:06 |
| somlo | but no schematics (yet) | 01:06 |
| *** bl0x <[email protected]> has joined #litex | 01:09 | |
| *** bl0x_ <[email protected]> has quit IRC (Ping timeout: 268 seconds) | 01:10 | |
| *** Degi_ <[email protected]> has joined #litex | 02:02 | |
| *** Degi <[email protected]> has quit IRC (Ping timeout: 260 seconds) | 02:02 | |
| *** Degi_ is now known as Degi | 02:02 | |
| *** hansfbaier <[email protected]> has joined #litex | 03:32 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 03:50 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #litex | 03:51 | |
| hansfbaier | somlo: There is a schematic for the previous version of the STLV7325 board though | 04:04 |
| hansfbaier | somlo: Where exactly did you configure the delays that made the ethernet work? | 04:15 |
| *** hansfbaier <[email protected]> has quit IRC (Quit: WeeChat 3.5) | 04:59 | |
| *** shorne <[email protected]> has quit IRC (Read error: Connection reset by peer) | 06:14 | |
| *** shorne <[email protected]> has joined #litex | 06:15 | |
| *** lexano <[email protected]> has quit IRC (Ping timeout: 268 seconds) | 08:59 | |
| *** lexano <[email protected]> has joined #litex | 09:12 | |
| *** hansfbaier <[email protected]> has joined #litex | 11:48 | |
| *** hansfbaier <[email protected]> has quit IRC (Client Quit) | 11:49 | |
| *** jryans <jryans!~jryans@2001:470:69fc:105::1d> has joined #litex | 12:42 | |
| *** lambda <[email protected]> has quit IRC (Ping timeout: 248 seconds) | 12:53 | |
| *** peeps <peeps!~peepsalot@openscad/peepsalot> has joined #litex | 13:21 | |
| *** peeps[zen] <peeps[zen]!~peepsalot@openscad/peepsalot> has quit IRC (Ping timeout: 268 seconds) | 13:23 | |
| somlo | _florent_: follow-up question, what's the meaningful resolution on e.g. s7rgmii phy's rx_delay and tx_delay? I.e., if I want to "sweep" the [0.9e-9 .. 1.3e-9] range to find where my tftp transfer is "least choppy" when netbooting | 13:32 |
| somlo | should I try increments of 0.1e-9, 0.05e-9, etc? I don't have an intuitive feeling for how fine is no longer worth bothering with :) | 13:33 |
| somlo | *fine grained | 13:33 |
| *** lambda <[email protected]> has joined #litex | 13:38 | |
| *** so-offishul <[email protected]> has joined #litex | 15:14 | |
| *** so-offishul <[email protected]> has quit IRC (Remote host closed the connection) | 15:15 | |
| *** so-offish <so-offish!~so-offish@2610:148:610:2b11::11> has quit IRC (Ping timeout: 260 seconds) | 15:17 | |
| *** so-offish <so-offish!~so-offish@2610:148:610:2b11::10> has joined #litex | 15:18 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:79c2:728d:d50d:c315> has quit IRC (Read error: Connection reset by peer) | 16:08 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:1997:a090:3300:232a> has joined #litex | 16:09 | |
| *** shorne <[email protected]> has quit IRC (Read error: Connection reset by peer) | 18:15 | |
| *** shorne <[email protected]> has joined #litex | 18:21 | |
| *** shorne <[email protected]> has quit IRC (Read error: Connection reset by peer) | 18:25 | |
| *** shorne <[email protected]> has joined #litex | 18:26 | |
| somlo | hansfbaier: (on the off chance that you end up reading the logs): the previous version of the stlv7325 uses gmii (8 tx, 8 rx pins) | 18:45 |
| somlo | the new version uses rgmii (4 tx, 4rx); so the phy delays (currently at https://github.com/gsomlo/litex-boards/blob/gls-stlv7325-v2/litex_boards/targets/sitlinv_stlv7325_v2.py#L90-L91) are naturally different | 18:48 |
| _florent_ | somlo: The I/ODELAYs have 32 taps on 7-Series, so you could just make test the taps around the one that "work" | 19:23 |
| _florent_ | somlo: https://github.com/enjoy-digital/liteeth/blob/master/liteeth/phy/s7rgmii.py#L67-L70 | 19:23 |
| _florent_ | somlo: if you print iodelay_tap_average, you'll get the increment you can test | 19:24 |
| somlo | _florent_: thanks, that makes sense (for rx_delay); looks like tx_delay works a bit differently | 19:29 |
| somlo | https://github.com/enjoy-digital/liteeth/blob/master/liteeth/phy/s7rgmii.py#L169-L175 | 19:30 |
| somlo | but besides eyeballing the tftp "spinner" and deciding it's "too choppy", maybe I should try using iperf to measure (and optimize) the delays for each direction (tx vs. rx) independently of each other... | 19:31 |
| somlo | _florent: for tx_delay the valid range is [0 .. 8.0e-9], so that tx_phase can go from 0 to 360 | 20:14 |
| *** markov_twain <markov_twain!~markov_tw@user/markov-twain/x-1620001> has joined #litex | 20:16 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 20:16 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #litex | 20:17 | |
| somlo | guess the resolution there depends on what granularity the phase parameter can be at, in a xilinx `create_clkout(...)` call | 20:26 |
| somlo | it's from 0 to 360, but what happens when you feed it a decimal like 67.5? Does it end up rounding to the nearest integer, or can it handle sub-unit resolution on phase? | 20:27 |
| *** gurki is now known as naive | 20:32 | |
| *** naive is now known as gurki | 20:32 | |
| *** zjason` <zjason`[email protected]> has joined #litex | 21:28 | |
| *** zjason <[email protected]> has quit IRC (Ping timeout: 276 seconds) | 21:30 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!