Title: integration/common: fix mem_decoder (shadow base has been deprecated) · enjoy-digital/litex@16d1972 · GitHub (at github.com)
CarlFK has joined #litex
_florent_: ah, interesting! I hadn't actually tested it yet, but while playing around with the liteeth standalone generator and trying to make it fit into my addressing scheme, I couldn't help but wonder how this was ever *supposed* to work ;) glad to see it fixed
_florent_: BTW, I had been using litex_buildenv which isn't quite up-to-date with the main litex repos; I finally got my board definition working with the bare litex environment, but it was still having ethernet issues that I have not fully tracked down. But I can confirm that ISE really doesn't like the auto-added "keep" attributes when constraints are added; I had to remove that to get past the packing phase.
Xiretza: yes sorry, the code in master is a bit messy since has evolved a lot without rewrite. I'm rewritting things in the new_soc branch to have something easier to understand and retro-compatible
levi: interesting, feel free to open an issue with your platform/target so that i can look and try to find a way to avoid the workaround
rohitksingh has quit [Ping timeout: 260 seconds]
It's a custom board that no one else is likely to have, but I noticed that you commented on a similar issue occurring in the open PR at litex_buildenv where they're trying to migrate to newer litex.
That's how I got the idea of how to remove the "keep" attribute in the first place.
levi: ah ok, i thought this was the issue from the PR :)
rohitksingh has joined #litex
Where it showed up in my board is that I need to route the xtal input through the FPGA and out to the xtal input of the ethernet phy. I have no idea why the board was done this way. It works fine without "keep" but with it there's always some complaint because keep implies NOMERGE. And ISE also complains that the "keep" attributes are not applicable to primary ports, so I figured it was safe to remove.
No rush to resolve this or anything, just wanted to add some info about what was going on with my board in case it might provide more context to the larger issue.