Olof Kindgren

Sorry. Completely missed this. First thing to check; does the LED blink? If yes, then it's most likely a UART issue, e.g. wrong baud rate. If not, check for any...

Was this ever resolved? I could swear also that I had a branch where I added yosys support to the ISE backend but I can't find it now

I agree. There's not much effort to change it to a a `parameter` instead of a `localparam` in serving.v, *but* the CoreScore rules also say that we must use version...

That's a good idea. That should hopefully reduce the number of msgpack-related issues as well. Come to think of, there are now two executable scripts in corescore. Might even start...

Awesome! Thanks for working on this. I hope I can get around to review this soon, but please ping me if you don't hear back

Thank you for the work you have done. I have found some time to start reviewing now. Will let you know as soon as I have any comments

@Pocketkid2 My attack plan right now is to start by pulling in all independent smaller fixes and then it would be great if you could rebase and squash the remaining...

> > One more thing! After playing around with the new flow API I have discovered that some things didn't really work as intended. In particular, it was not possible...

Alright. First two tiny commits added. Right now I'm looking at the nextpnr changes. I _think_ we can make the diff much smaller if we do an `elif` here https://github.com/olofk/edalize/pull/322/files#diff-57dbc9962eed8258be08d24cc0ba97652eaff3c92c76d9c445be10002fc3cef0L92...

[This](https://github.com/olofk/edalize/pull/193#pullrequestreview-503352325) was the chipdb discussion I was thinking about. At least part of it. Still missing a user-friendly way to pull in the right ones without involving the user in...