*** tpb has joined #litex | 00:00 | |
*** pftbest has quit IRC | 00:01 | |
*** pftbest has joined #litex | 00:17 | |
*** pftbest has quit IRC | 00:23 | |
*** FFY00_ has joined #litex | 00:33 | |
*** TMM has quit IRC | 00:57 | |
*** TMM has joined #litex | 00:57 | |
*** lf has quit IRC | 00:58 | |
*** lf has joined #litex | 00:58 | |
*** j4cbo has joined #litex | 01:18 | |
*** pftbest has joined #litex | 01:19 | |
*** pftbest has quit IRC | 01:24 | |
*** pftbest has joined #litex | 01:51 | |
*** pftbest has quit IRC | 01:55 | |
*** Emantor has quit IRC | 02:20 | |
*** Emantor has joined #litex | 02:20 | |
*** Degi has quit IRC | 03:11 | |
*** Degi has joined #litex | 03:14 | |
promach3 | _florent_: however I suppose `tWR` is not needed for `WRITE_AP` where it is using AUTO-PRECHARGE mechanism ? | 04:19 |
---|---|---|
promach3 | I mean no need to manually compute the Precharge Time | 04:20 |
*** lkcl has quit IRC | 04:24 | |
promach3 | by 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 #litex | 04:38 | |
*** lkcl has quit IRC | 05:24 | |
j4cbo | hi! 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 #litex | 05:37 | |
*** lkcl has quit IRC | 06:49 | |
*** pftbest has joined #litex | 07:00 | |
*** lkcl has joined #litex | 07:01 | |
*** lkcl has quit IRC | 07:17 | |
*** lkcl has joined #litex | 07:30 | |
*** pftbest has quit IRC | 07:46 | |
*** pftbest has joined #litex | 08:06 | |
*** pftbest has quit IRC | 08:11 | |
*** Bertl is now known as Bertl_zZ | 08: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 ideas | 08: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 --trace | 08:53 |
_florent_ | This will allow you to see the internal signals and how the DFI interface should behave | 08:53 |
promach3 | _florent_: See https://gist.github.com/promach/2c477b1dbc39f04a1271fb229e6d678c | 09:11 |
promach3 | why 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 #litex | 09: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 |
pftbest | j4cbo: 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 #litex | 09:50 | |
promach3 | but `DM` (or `TDQS` pin) is of `inout` nature | 09:50 |
_florent_ | promach3: yes start simple with DM as output hardwired to 0 | 10:08 |
promach3 | but the pin itself is `inout` ? | 10:08 |
promach3 | _florent_: | 10:08 |
_florent_ | You can just use it as an output | 10:16 |
*** shorne has quit IRC | 10:22 | |
*** kgugala has joined #litex | 10:24 | |
*** kgugala_ has quit IRC | 10:28 | |
*** lkcl has quit IRC | 10:38 | |
*** kgugala_ has joined #litex | 10:51 | |
*** lkcl has joined #litex | 10:52 | |
*** kgugala has quit IRC | 10:55 | |
*** shorne has joined #litex | 10:58 | |
promach3 | _florent_: but `TDQS_n` needs to be `High-Z` ? | 11:09 |
*** _whitelogger has quit IRC | 11:54 | |
*** _whitelogger has joined #litex | 11:56 | |
*** shorne has quit IRC | 12:17 | |
pftbest | How to stop litex_sim ? | 12:24 |
pftbest | is Ctrl+C a good way to stop it? | 12:27 |
*** shorne has joined #litex | 12:34 | |
*** kgugala_ has quit IRC | 13:07 | |
_florent_ | pftbest: yes, that's the way to do it. (We should probably improve this) | 13:09 |
*** kgugala has joined #litex | 13:33 | |
*** pftbest has quit IRC | 13:52 | |
*** pftbest has joined #litex | 13:55 | |
*** pftbest has quit IRC | 14:12 | |
*** pftbest has joined #litex | 14:13 | |
*** pftbest has quit IRC | 14:15 | |
*** pftbest has joined #litex | 14:17 | |
*** pftbest has quit IRC | 14:26 | |
*** pftbest has joined #litex | 14:27 | |
*** pftbest has quit IRC | 14:38 | |
*** pftbest has joined #litex | 14:44 | |
*** pftbest has quit IRC | 14:51 | |
*** pftbest has joined #litex | 15:17 | |
*** pftbest has quit IRC | 15:19 | |
*** pftbest has joined #litex | 15:19 | |
*** Bertl_zZ is now known as Bertl | 15:23 | |
*** pftbest has quit IRC | 15:45 | |
*** pftbest has joined #litex | 15:46 | |
*** pftbest has quit IRC | 15:50 | |
*** pftbest has joined #litex | 16:10 | |
*** lkcl has quit IRC | 16:27 | |
*** lkcl has joined #litex | 16:41 | |
*** TMM has quit IRC | 17:17 | |
*** TMM has joined #litex | 17:17 | |
*** kgugala_ has joined #litex | 17:50 | |
*** kgugala has quit IRC | 17:52 | |
zyp | has anybody tried integrating the luna usb stack with litex? | 18:57 |
_florent_ | zyp: I think Greg Davill did some tests with Luna and LiteX | 20:06 |
_florent_ | https://github.com/gregdavill/ButterStick-projects/commit/7c3a714b6e6817bd1d430d6ba120dde419d1e3a0 | 20:17 |
zyp | ah, nice | 20:19 |
zyp | not having any luck with etherbone on ecpix-5, getting neither ping nor arp replies | 21:21 |
*** st-gourichon-fid has quit IRC | 22:08 | |
*** st-gourichon-fid has joined #litex | 22:09 | |
*** st-gourichon-fid has quit IRC | 22:19 | |
*** st-gourichon-fid has joined #litex | 22:20 | |
*** nelgau has quit IRC | 23:13 | |
*** sorear has quit IRC | 23:14 | |
*** shorne has quit IRC | 23:15 | |
*** sorear has joined #litex | 23:17 | |
*** shorne has joined #litex | 23:22 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!