Thursday, 2022-03-03

*** tpb <[email protected]> has joined #litex00:00
*** Peanut <Peanut!~paul@user/peanut> has quit IRC (Ping timeout: 240 seconds)01:47
*** Peanut <Peanut!~paul@user/peanut> has joined #litex01:47
*** bl0x_ <bl0x_!~bastii@p200300d7a70ffe004ca26f9ad24b4fff.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 240 seconds)02:21
*** bl0x_ <bl0x_!~bastii@p200300d7a70fb1009a8e59174a2e2e90.dip0.t-ipconnect.de> has joined #litex02:24
*** pavelow_ <[email protected]> has quit IRC (Quit: No Ping reply in 180 seconds.)02:42
*** pavelow <[email protected]> has joined #litex02:42
*** Degi <[email protected]> has quit IRC (Ping timeout: 240 seconds)03:11
*** Degi <[email protected]> has joined #litex03:11
*** FabM <FabM!~FabM@2a03:d604:103:600:c472:c3e9:cd21:d258> has joined #litex08:06
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has quit IRC (Remote host closed the connection)08:38
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has joined #litex08:39
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has quit IRC (Read error: Connection reset by peer)08:39
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has joined #litex08:39
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has quit IRC (Read error: Connection reset by peer)08:39
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has joined #litex08:42
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has quit IRC (Remote host closed the connection)08:42
*** vomoniyi[m] <vomoniyi[m]!~vomoniyig@2001:470:69fc:105::3023> has quit IRC (Quit: You have been kicked for being idle)09:00
*** Peanut <Peanut!~paul@user/peanut> has quit IRC (Ping timeout: 256 seconds)10:03
*** Peanut <Peanut!~paul@user/peanut> has joined #litex10:03
*** DoubleJ <DoubleJ!~DoubleJ@user/doublej> has joined #litex11:36
*** acathla_ is now known as acathla11:52
*** linear_cannon <[email protected]> has quit IRC (Ping timeout: 240 seconds)13:01
*** linear_cannon <[email protected]> has joined #litex13:05
*** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (*.net *.split)13:31
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:d5e1:c3ff:9fb6:6884> has quit IRC (*.net *.split)13:31
*** Wolfvak <Wolfvak!~Wolfvak@user/wolfvak> has quit IRC (*.net *.split)13:31
*** tcal <tcal!sid456577@2a03:5180:f:2::6:f781> has quit IRC (*.net *.split)13:31
*** FabM <FabM!~FabM@armadeus/team/FabM> has joined #litex13:32
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:d5e1:c3ff:9fb6:6884> has joined #litex13:32
*** Wolfvak <Wolfvak!~Wolfvak@user/wolfvak> has joined #litex13:32
*** tcal <tcal!sid456577@2a03:5180:f:2::6:f781> has joined #litex13:32
*** Abhishek_ <[email protected]> has joined #litex13:39
tntOk, so after nearly a full day of playing with constrainst and xdc and all that stuff, this is the culprit :13:47
tnthttps://github.com/enjoy-digital/litex/commit/3c34039b731b42e27e2ee6c8e399e5eb8f3a058f13:47
tntThat causes the false path constraint in the XDC to be processed before the generated clock from the IP are created and so it doesn't find those clocks (not created yet).13:48
tntand AFAICT the purpose of that commit doesn't even work (at least not on current vivado). Trying to just use LOC constraints on the pins that don't match what was used in the .xci just results in DRC errors because some part of the IP end up locked to one place and some other to anothe rplace and it can't route things.13:49
tntDamnit ... I was preparing a PR to litex-board for the ADI board ... do one last test on master ... and now dma_test fails :/15:25
tnt[  319.751518] litepcie 0000:01:00.0: Reading too late, 92 buffers lost15:25
tnt[  319.751667] litepcie 0000:01:00.0: Writing too late, 57 buffers lost15:25
tntand litepci_util says 'Unable to find DMA RX_DELAY (min errors: 2048/2048), exiting'15:25
tntMmmm that whole RX_DELAY thing is new, and if I try to use the "old" dma_test it works.15:39
*** cr1901_ <cr1901_!~cr1901@2601:8d:8600:911:cf1:8507:720a:c17> has joined #litex15:51
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:d5e1:c3ff:9fb6:6884> has quit IRC (Ping timeout: 240 seconds)15:54
*** david-sawatzke[m <david-sawatzke[m!~david-saw@2001:470:69fc:105::1634> has quit IRC (Quit: You have been kicked for being idle)16:00
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)16:25
*** TMM_ <[email protected]> has joined #litex16:25
*** Peanut <Peanut!~paul@user/peanut> has quit IRC (Quit: Power Outage)17:01
*** bl0x_ <bl0x_!~bastii@p200300d7a70fb1009a8e59174a2e2e90.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 240 seconds)18:37
tntI'm a bit at a loss how a DMA loopback test can "loose" packet ... this isn't a real-time process, if there is no buffer descriptors, just wait until there is one.19:14
tntI haven't dug into the code yet but that seems highly suspitious.19:15
*** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Ping timeout: 240 seconds)19:17
*** cr1901_ is now known as cr190120:03
tntSo IIUC this is the so called "loop mode" where the descriptor are just looped indefinitely, completely free-running of any software control which is definitely not what I'd want.21:25
tntUnfortunately it looks like the kernel driver has no other mode, so I'll need to write my own from scratch unless someone has an example that doesn't use loop mode ?21:25
*** linear_cannon <[email protected]> has quit IRC (Ping timeout: 240 seconds)22:37
*** linear_cannon <[email protected]> has joined #litex22:42
*** linear_cannon <[email protected]> has quit IRC (Ping timeout: 256 seconds)22:56
*** linear_cannon <[email protected]> has joined #litex23:10
*** linear_cannon <[email protected]> has quit IRC (Read error: Connection reset by peer)23:32
*** linear_cannon <[email protected]> has joined #litex23:32

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!