_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
Coldberg has quit [Ping timeout: 256 seconds]
Degi_ has joined #litex
Degi has quit [Ping timeout: 252 seconds]
Degi_ is now known as Degi
FabM has joined #litex
FabM has joined #litex
<_florent_> Hi chiefwigms, sorry I got your mail but haven't been able to answer yet
<_florent_> The 1000basex support for Ultrascale+ has indeed not been done yet, but this should not be too complicated:
<_florent_> - for 7-series/Ultrascale, the parameters are directly extracted from the generated files of the wizard configured for as SGMII PHY
<_florent_> - the parameters are also in the same order than the wizard, so it's easy to integrate them with a diff tool
<_florent_> - so supporting GTYE4 instead of GTHE3 should be a matter of remplacing the instance in the ku_1000basex phy
<_florent_> I could have a look and provide at least a skeleton if you want
<_florent_> In the long term, I would like to rely directly LiteICLink for the 1000basex PHYs (that already has GTYE4 support), but this work hasn't been started yet
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
Coldberg has joined #litex
Coldberg has quit [Ping timeout: 265 seconds]
lkcl has quit [Ping timeout: 250 seconds]
C-Man has joined #litex
cr1901 has quit [Ping timeout: 256 seconds]
chiefwigms has quit [Quit: Client closed]
lkcl has joined #litex
cr1901 has joined #litex
Guest20 has joined #litex
Guest20 has quit [Client Quit]
somlo has quit [Quit: Leaving]
chiefwigms has joined #litex
<chiefwigms> Hey _florent_ - thanks! i'll give that a shot.. i'll let you know in a few hours if that worked.. thanks!
somlo has joined #litex
<_florent_> chiefwigms: ok great, in case you don't get it working, I could also help and do some tests on hardware
C-Man has quit [Ping timeout: 240 seconds]
<chiefwigms> so i generated one the eth core for the kcu105 (ku_1000basex.py)
<chiefwigms> some of the parameter values don't match up (granted i'm using viviado 2021)
<chiefwigms> but where do the i_ & o_ values come from?
<chiefwigms> like ` i_TXCTRL0 = Cat(*[tx_data[10*i+8] for i in range(2)]),`
<chiefwigms> or some of the o_ params just call Open(), but others have internal variables
rom has joined #litex
<rom> hi
<rom> I'm working on building a SoC with Litex, currently running the Linux on Litex demo just fine, and is looking to customize it a bit
<rom> I'd like to change the DDR IP to an SDRAM controller (to use SDRAM instead of DDR). Can anyone point me in the right direction?
<rom> Thanks
FabM has quit [Quit: Leaving]
rom has quit [Ping timeout: 246 seconds]
C-Man has joined #litex
Coldberg has joined #litex
C-Man has quit [Ping timeout: 240 seconds]
<chiefwigms> i think i see where the values came from... did you do any custom input parameters for the wizard?
<chiefwigms> i can send a pastebin of diffs for the kcu105
<alanvgreen> rom: Typically you'd be working with an existing board from litex-boards. The board definition in the target file will add the correct type of ram for the board. If you have new board kind of board, you could make new platform and target files to match.
<alanvgreen> rom: If you adding RAM via a PMOD or some other connector, you will probably want to subclass your board's target SoC target. In the constructor, make a PHY and pass it to call add_sdram() - see litex_boards/targets/radiona_ulx3s.py for an example. You'll need to define the signals returned by platform.request("sdram"), either by modifying the corresponding platform file or by calling platform.add_extension()
<tpb> Title: Pasteboard - Uploaded Image (at pasteboard.co)
<chiefwigms> do any of those diffs matter (short of TXCTRL*/TXDATA/TXUSRCLK*/GTHRX*)?
<chiefwigms> (i meant anything that's a scalar type binary/dec/string)
<alanvgreen> rom: oh, I see an the terasic_de10nano board optionally add sdram via a connector - that would be a good starting point
<_florent_> chiefwigms: your parameters seem really different than the one we have, I'm not sure the same input settings have been used
pftbest has quit [Read error: Connection reset by peer]
<_florent_> chiefwigms: I could try to generate the Ultrascale+ settings tomorrow if you want
pftbest has joined #litex
<OmkarBhilare[m]> Hello, Today in my gsoc project I finished gpmc to wishbone wrapper on beaglewire (fpga cape for beaglebone).
<OmkarBhilare[m]> I wanted to interface SDRAM to the fpga using litedram.
<OmkarBhilare[m]> Can you please provide me a skeleton/support for the standalone sdram.
<OmkarBhilare[m]> <_florent_ "For SDRAM, the initialization is"> Once the ip is produced, I believe I can do this on my own.
<chiefwigms> 🤷‍♂️ sure
<tpb> Title: Pasteboard - Uploaded Image (at pasteboard.co)
<chiefwigms> sorry.. wrong window
<chiefwigms> that was just a diff between a generated vivado 2021.1 (kcu105 which is a kintex ultra) and what's in the liteeth repo
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex