Ilia Sergachev

Hi! 1) Are you sure it's the only change (fb1513e9 vs 7f1e3936) ? 2) Anything in dmesg? 3) 7 Gb/s data rate looks like PCIe 2x, I don't have any...

I can cause the same problem on both old and new versions with some CPU load and some positive niceness, but can't detect any difference between them yet. Still trying....

One more problem I spotted is that dma_test is not so good at detecting errors - even when the module reports overflows/underflows dma_test can show 0 errors. That's most likely...

> writes are now done continously (as it was before in fact) Was it? Look at something old enough: https://github.com/enjoy-digital/litepcie/blob/19207c8dcd88aebce378b0124bc4831452a48c5f/litepcie/software/user/litepcie_util.c#L304

Hi! Apart from what @enjoy-digital already answered: - lowering the frequency does not help - inverting the chain is not trivial on this board, can do later with other boards...

I tested with OpenOCD too and it also fails somewhere with 2 devices on the chain (flash programming of Artix for sure, but maybe something else too). Will be able...

I'm back to tests with this board; latest openFPGALoader still fails the same way. The only way I found to program ECP5 with OpenOCD is to use an .svf file...

> Have you specified which device is the target? Sure - see --index-chain x in the commands in the 1st message. > Maybe checking signals between probe and EPC5, between...

In the latest version (2.37.349), one wakelock (FutureService) remains out of two. Had both FutureService and ZMessagingService on the previous version of Wire. Android 7.1.2, no google apps.

AXILiteDownConverter is not used here, it's axi64 -> axi32 -> axilite32 -> wb32 with the first conversion being the problem. One possible solution is here: https://github.com/enjoy-digital/litex/pull/1387