_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://libera.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
Degi_ has joined #litex
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
TrailingEdge has joined #litex
FabM has joined #litex
FabM has quit [Changing host]
FabM has joined #litex
TrailingEdge has left #litex [WeeChat 2.3]
TrailingEdge has joined #litex
Brinx has quit [Remote host closed the connection]
toshywoshy has quit [Ping timeout: 268 seconds]
toshywoshy has joined #litex
Yanan has joined #litex
<Yanan> Hi everyone, is there any document on how to implement a new PHY for litedram? I am planing to add support for efinix FPGAs.
toshywoshy has quit [Ping timeout: 256 seconds]
toshywoshy has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
Brinx has joined #litex
Brinx has quit [Ping timeout: 252 seconds]
Brinx has joined #litex
jersey99 has quit [Quit: Client closed]
Yanan has quit [Ping timeout: 260 seconds]
TrailingEdge has quit [Quit: WeeChat 2.3]
TrailingEdge has joined #litex
<sensille> what would be a good starting point for a riscv on a small fpga with ethernet? it has SDRAM, but is probably not needed
<sensille> hm, based on SoCCore it automatically builds a ROM of 24k, which is a lot for the small chip. maybe i can add the SDRAM, copy from spi flash on startup and run from SDRAM
<sensille> maybe icebreaker-fpga is a good starting point
Brinx has quit [Remote host closed the connection]
FabM has quit [Quit: Leaving]
<zyp> sensille, you mentioned having a colorlite board the other day, in which case the obvious starting point would be the example project for the colorlite board
<sensille> yeah, done that. i mean for adding a CPU
<sensille> i have the rv901t
<sensille> i managed to build a bitstream, but it doesn't ping. while with a different project (Litex-CNC) it pings. now i'm trying to find the difference in the board definition
<zyp> by «adding a CPU», do you mean in the sense of writing your own?
<sensille> no, an existing risc core. the is what i currently have, c&p'd from various sources: https://dpaste.org/4o3rn
<tpb> Title: dpaste/4o3rn (Python) (at dpaste.org)
<sensille> i should take the working (pinging) project and morph it into what i want to have in baby steps
jersey99 has joined #litex
<sensille> boils down to: when i change sys_clk from 30mhz to 50mhz it works
<sensille> maybe ... litex derives the 30 from the 25, but not exactly, and then derives the 125mhz from the inexact 30?
<sensille> no, eth_clocks0_rx is an input
<zyp> no, it's just that 30 is too slow to keep up with the ethernet stream once the data is passed over to the sys domain
<sensille> oh. so maybe some modul could check that and bail out?
<sensille> do you happen to know what the minimum is?
<zyp> a gigabit data stream is 125 MT/s at 8-bit, or 31.25 MT/s at 32-bit
<zyp> I mean, it's as simple as 1000 / 32 :)
<zyp> I'm assuming it's 32-bit, given that it works at 50 but not 30
<sensille> :)
<sensille> it's nice that litex hides everything from me, but in a case like this at least some insight could be helpful :)
<zyp> well, you could insert a litex.soc.interconnect.stream.Monitor in a stream pipeline to gain insight into how it's performing
zjason` has joined #litex
zjason has quit [Ping timeout: 256 seconds]
Brinx has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
jersey99 has quit [Quit: Client closed]