Seb

Hi Guys, Was there any progress made on this topic? This is something I am also very interested in. Thanks! FYI, the first solution proposed by @imphil seems to do...

From what I could gather, there isn't yet a `modelsim.py` description in the `edalize/tools` folder. I suppose this is due to the migration from tool to flow approach. I will...

I am not very familiar with the internals of edalize, so it might take more time than I anticipated. @olofk any idea how much work it would be for you...

I am also encountering the same issue and wondering if there is a solution to this. In my case, I have a top level core that depends on other cores....

So on my setup, it works well when using the FLOW approach. I am not sure why I get those checks failures. Maybe @olofk can help explaining why this fails?...

Thanks for the suggestion @olofk I tried and it does indeed work as expected. My only comment would be to say that the Vivado implementation step `power_opt_design` is quite common...

I get your point. For sure there are many ways to look at it and different people will have different approaches and will use different parameters. Thanks for being responsive,...

Hi guys, I am following up on the topic regarding multi-cut vias. This is indeed quite typical to use double-cut vias instead of single ones to improve yield. This is...

Adding some context to this issue. When I look at the logcat for when I try to open the application for the first time, I can see that there is...

thanks for your proposal. I was able to find a fix for this issue. But I could not find a way to make it a system app while baking it...