13:25 <sebo> Hello, is there anybody using the CSRConstant method? I'm using it like this self.allone = CSRConstant(value=0x0BADCAFE).

13:26 <sebo> In my test: data = yield from dut.allone.read() throws an error.

13:26 <sebo> TypeError: 'int' object is not iterable.

13:27 <sebo> However, using CSRStatus is working...

14:21 <_florent_> sebo: https://github.com/enjoy-digital/litex/commit/6ef96b17bca5e7be7fbbf5cc32d8866739f80b19 :)

14:22 <_florent_> sebo: as discussed together, it would be good to have access methods for CSRFields too, but don't have the time to look at it for now

15:44 <sebo> Thanks _florent_ for correcting this. I do remember for the fields. Is it worth opening an issue for a later fix?

15:45 <_florent_> sebo: yes sure, feel free to open one.

16:21 <sebo_> ok

16:57 <Wolfvak> hi, just mentioning that the latest linux-on-vexriscv doesnt seem to work on orangecrab 25F, without the wishbone-memory parameter I get a memory failure, with the parameter it just gets stuck with the "Booting from boot.json" and its been there for a few minutes

18:45 <_florent_> Hi Wolfvak, thanks for the feedback. I switched ECP5/DDR3 to native LiteDRAM interface last week and got it working correctly on my OrangeCrab 25F, but there are indeed variability between boards

18:45 <_florent_> this is related to DM handling in the ECP5DDRPHY. I would need to spend more time looking at it.

18:46 <_florent_> In the meantime, I indeed encourage using --with-wishbone-memory, but I'm not sure I tested it again last week

18:47 <_florent_> I'll do the test tomorrow and check. If it's stuck when booting from the SDCard, it could be the DMA that is not connected correctly in this case

18:59 <Wolfvak> I just tried again and it managed to boot into linux, seems to be almost random

18:59 <Wolfvak> I just kept resetting it and eventually it worked

19:06 <Wolfvak> one more thing: "litex-mmc f0005800.mmc: Requested clk_freq=25000000: set to 32000000 via div=2" seems like the driver wants to set it to 25MHz but you're rounding it to 32MHz? shouldn't it be down to 16MHz instead? SD card initialization will fail if you don't properly enable the high speed functionality

19:07 <Wolfvak> ran a bit of a "stress test" https://i.imgur.com/sUwZdTg.png