TCal

Results 198 comments of TCal

I have ``` verilator is already the newest version (4.038-1). ``` so that could be it. I can also try reproducing on my Pixelbook.

On ChromeOS, it works for me. But, I have Verilator 4.038-1. I'm on ChromeOS Version 102.0.5005.6 (Official Build) dev (64-bit).

Hello @ggangliu , Is there an actual error so that `proj_template` cannot be built? That would be surprising since we haven't seen failures in our GitHub Actions tests. Yes, we...

Hi @spicker23 -- you didn't have any problem until you started making changes to switch over to Amaranth, right?

It's strange @danc86 , this was the first timing check that I added (just a grep of the Vivado build log), and I haven't disabled it as far as I...

https://github.com/google/CFU-Playground/blob/main/soc/common_soc.mk#L79-L92 I suspect that now the timing check is performed only if you explicitly set "USE_VIVADO", but it isn't performed if you use Vivado as the default. Yes, the Makefile...

> Please make LiteX consistent rather then working around it. :+1:

@minexo79 thanks for giving this a try! Some boards have their quirks and need some special handling. Have you built for the board in the basic LiteX environment (outside of...

@minexo79 let me know if you want some hints about the "basic LiteX" build for your board.

@minexo79 Ok, then it's a bit like Fomu. With Fomu, we flash the bitstream and the binary together (to the same external flash). There is board-specific code to handle it...