Monday, 2020-07-13

*** tpb has joined #litex00:00
*** fitzsim has quit IRC00:07
*** HoloIRCUser has joined #litex00:27
*** HoloIRCUser1 has quit IRC00:30
*** Degi has quit IRC01:27
*** Degi has joined #litex01:28
*** HoloIRCUser1 has joined #litex01:48
*** HoloIRCUser has quit IRC01:48
*** gregdavill has joined #litex02:40
*** jaseg has quit IRC02:44
gregdavillloxodes: I just took a look at your dma code, and opened an issue with a fix. Pretty sure you just need to flush the caches.02:45
*** jaseg has joined #litex02:45
loxodesgregdavill: thanks! the fix worked for me03:00
loxodesI'm trying to understand why this fixed it - so the vexriscv cpu was caching some of the "adc_sram" memory, and reading unrelated hid the problem because that filled up the cache with something else?03:06
loxodesand adding the volatile keyword to dram_array didn't help in this case because that only works on the compiler?03:08
gregdavillYeah, I think so. I'm not entirely sure of the logic behind how the cache lines are filled on the vex. But in general you should always invalidate the cache when using DMA and shared memory spaces.03:10
*** ranzbak has quit IRC03:57
*** st-gourichon-fid has joined #litex04:55
*** HoloIRCUser2 has joined #litex04:59
*** HoloIRCUser1 has quit IRC05:02
*** HoloIRCUser1 has joined #litex05:23
*** HoloIRCUser2 has quit IRC05:27
*** HoloIRCUser1 has quit IRC05:49
*** kgugala__ has quit IRC05:51
*** kgugala has joined #litex05:52
*** ranzbak has joined #litex06:01
*** kgugala_ has joined #litex06:46
*** kgugala has quit IRC06:50
*** ranzbak has quit IRC06:53
*** ranzbak has joined #litex07:00
*** st-gourichon-f has joined #litex07:27
*** st-gourichon-fid has quit IRC07:31
*** st-gourichon-f has quit IRC07:39
*** gregdavill_ has joined #litex09:38
*** gregdavill has quit IRC09:41
*** scanakci has quit IRC10:23
*** kgugala has joined #litex11:11
*** kgugala_ has quit IRC11:14
*** kgugala has quit IRC11:22
*** kgugala has joined #litex11:22
*** _whitelogger has quit IRC13:25
*** gregdavill_ has quit IRC13:26
*** _whitelogger has joined #litex13:26
*** Degi has quit IRC13:27
*** acathla has quit IRC13:27
*** somlo has quit IRC13:27
*** _franck_ has quit IRC13:27
*** Finde has quit IRC13:27
*** tmbinc has quit IRC13:27
*** wizzy has quit IRC13:27
*** Degi has joined #litex13:28
*** acathla has joined #litex13:28
*** somlo has joined #litex13:28
*** _franck_ has joined #litex13:28
*** Finde has joined #litex13:28
*** wizzy has joined #litex13:28
*** tmbinc has joined #litex13:28
*** kgugala_ has joined #litex16:13
*** kgugala has quit IRC16:16
*** kgugala_ has quit IRC16:27
*** kgugala has joined #litex16:27
kbeckmannIs anyone working on integrating PSRAM/qspi-ram support in litex? I have some quite low quality code that works but is good enough to verify that the chip works. (write 42Mbps / read 27Mbps at 50MHz cpu core)16:45
kbeckmannjust asking before i put in an effort in making it nice. would be fun to run it at the max speed and so on.16:45
zypthere's hyperram at least: https://github.com/gregdavill/litex-hyperram/blob/master/hyperbus.py17:13
tpbTitle: litex-hyperram/hyperbus.py at master · gregdavill/litex-hyperram · GitHub (at github.com)17:13
kbeckmannright, that nice. but i was thinking of integrating with LY68L6400SLIT17:27
kbeckmannah i see that https://github.com/enjoy-digital/litex/pull/381 exists, that should be usable for (q)spi-ram as well17:33
tpbTitle: spi_flash: Add quadspi support by mateusz-holenko · Pull Request #381 · enjoy-digital/litex · GitHub (at github.com)17:33
*** kgugala has quit IRC17:46
*** kgugala has joined #litex17:46
*** m4ssi has joined #litex20:26
*** m4ssi has quit IRC20:58
*** lf_ has joined #litex23:49
*** lf has quit IRC23:49

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