Saturday, 2021-03-06

*** tpb has joined #litex00:00
*** pftbest has quit IRC00:01
*** pftbest has joined #litex00:17
*** pftbest has quit IRC00:23
*** FFY00_ has joined #litex00:33
*** TMM has quit IRC00:57
*** TMM has joined #litex00:57
*** lf has quit IRC00:58
*** lf has joined #litex00:58
*** j4cbo has joined #litex01:18
*** pftbest has joined #litex01:19
*** pftbest has quit IRC01:24
*** pftbest has joined #litex01:51
*** pftbest has quit IRC01:55
*** Emantor has quit IRC02:20
*** Emantor has joined #litex02:20
*** Degi has quit IRC03:11
*** Degi has joined #litex03:14
promach3_florent_: however I suppose `tWR` is not needed for `WRITE_AP` where it is using AUTO-PRECHARGE mechanism ?04:19
promach3I mean no need to manually compute the Precharge Time04:20
*** lkcl has quit IRC04:24
promach3by the way, for Micron definition on `DM` , it is a bit confusing on how exactly `DM` works  ?04:27
* promach3 uploaded an image: image.png (49KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/JvSqvlHYwpnbUIrVWelisSvx/image.png >04:27
*** lkcl has joined #litex04:38
*** lkcl has quit IRC05:24
j4cbohi! i'm trying to run linux-on-litex-vexriscv on my ecpix5, and i've got the gateware built from litex_boards and found prebuilt linux images at https://github.com/litex-hub/linux-on-litex-vexriscv/issues/164 but am stuck on getting the device tree `rv32.dtb`... is there a way to generate that from the litex_boards repo or do i need to rebuild with linux-on-litex-vexriscv/make.py ?05:26
*** lkcl has joined #litex05:37
*** lkcl has quit IRC06:49
*** pftbest has joined #litex07:00
*** lkcl has joined #litex07:01
*** lkcl has quit IRC07:17
*** lkcl has joined #litex07:30
*** pftbest has quit IRC07:46
*** pftbest has joined #litex08:06
*** pftbest has quit IRC08:11
*** Bertl is now known as Bertl_zZ08:12
_florent_promach3: DM is  a data mask for writes, similar to Wishbone's sel, AXI's strobe. Writing a DRAM controller can be complicated since there are lots of things to do correctly and as you see, reading datasheets does not always give you a clear understanding. Before writing your own, I would first recommend playing with one controller in simulation: Xilinx's MIG, LiteDRAM, Ultraembedded's DDR3 controller, etc...08:50
_florent_promach3: This will gives you a better understanding of things and you could then implement your own ideas08:51
_florent_promach3: For LiteDRAM, with LiteX installed, it's pretty easy to create a simulation with various DRAM modules (can be SDR/DDR/DDR2/DDR3/DDR4): litex_sim --with-sdram --sdram-module=xxyy --trace08:53
_florent_This will allow you to see the internal signals and how the DFI interface should behave08:53
promach3_florent_: See https://gist.github.com/promach/2c477b1dbc39f04a1271fb229e6d678c09:11
promach3why need to mask ? What will happen if user choose to pull DM to low logic during write cycle ? and is this allowed at all ?09:13
_florent_promach3: this is allowed yes to have DM always pulled low (some boards are wired like this) but will make you loose the byte granularity on writes, your granularity is then on DRAM's burst words.09:25
_florent_promach3: DM is just here to have byte granularity on the write accesses (ie you only want to update some bytes of the DRAM word)09:27
promach3_florent_: you mean `DM` has the purpose or meaning of `bit-select` in verilog ?09:29
*** pftbest has joined #litex09:33
_florent_promach3: When writes are done on bus with a data-width > 8, you are doing a single write for multiple bytes and then need to be able to indicate which bytes are valid and need to be updated in memory, which bytes should be ignored. That's the purpose of DM.09:36
pftbestj4cbo: when you run linux-on-litex-vexriscv/make.py it will generate a dtb file in the images directory.09:46
promach3_florent_: so, for simplicity, just hardwire `DM` to low logic ?09:47
*** Melkhior has joined #litex09:50
promach3but `DM` (or `TDQS` pin) is of `inout` nature09:50
_florent_promach3: yes start simple with DM as output hardwired to 010:08
promach3but the pin itself is `inout` ?10:08
promach3_florent_:10:08
_florent_You can just use it as an output10:16
*** shorne has quit IRC10:22
*** kgugala has joined #litex10:24
*** kgugala_ has quit IRC10:28
*** lkcl has quit IRC10:38
*** kgugala_ has joined #litex10:51
*** lkcl has joined #litex10:52
*** kgugala has quit IRC10:55
*** shorne has joined #litex10:58
promach3_florent_: but `TDQS_n` needs to be `High-Z` ?11:09
*** _whitelogger has quit IRC11:54
*** _whitelogger has joined #litex11:56
*** shorne has quit IRC12:17
pftbestHow to stop litex_sim ?12:24
pftbestis Ctrl+C a good way to stop it?12:27
*** shorne has joined #litex12:34
*** kgugala_ has quit IRC13:07
_florent_pftbest: yes, that's the way to do it. (We should probably improve this)13:09
*** kgugala has joined #litex13:33
*** pftbest has quit IRC13:52
*** pftbest has joined #litex13:55
*** pftbest has quit IRC14:12
*** pftbest has joined #litex14:13
*** pftbest has quit IRC14:15
*** pftbest has joined #litex14:17
*** pftbest has quit IRC14:26
*** pftbest has joined #litex14:27
*** pftbest has quit IRC14:38
*** pftbest has joined #litex14:44
*** pftbest has quit IRC14:51
*** pftbest has joined #litex15:17
*** pftbest has quit IRC15:19
*** pftbest has joined #litex15:19
*** Bertl_zZ is now known as Bertl15:23
*** pftbest has quit IRC15:45
*** pftbest has joined #litex15:46
*** pftbest has quit IRC15:50
*** pftbest has joined #litex16:10
*** lkcl has quit IRC16:27
*** lkcl has joined #litex16:41
*** TMM has quit IRC17:17
*** TMM has joined #litex17:17
*** kgugala_ has joined #litex17:50
*** kgugala has quit IRC17:52
zyphas anybody tried integrating the luna usb stack with litex?18:57
_florent_zyp: I think Greg Davill did some tests with Luna and LiteX20:06
_florent_https://github.com/gregdavill/ButterStick-projects/commit/7c3a714b6e6817bd1d430d6ba120dde419d1e3a020:17
zypah, nice20:19
zypnot having any luck with etherbone on ecpix-5, getting neither ping nor arp replies21:21
*** st-gourichon-fid has quit IRC22:08
*** st-gourichon-fid has joined #litex22:09
*** st-gourichon-fid has quit IRC22:19
*** st-gourichon-fid has joined #litex22:20
*** nelgau has quit IRC23:13
*** sorear has quit IRC23:14
*** shorne has quit IRC23:15
*** sorear has joined #litex23:17
*** shorne has joined #litex23:22

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