-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPXACT parse hdl paths #14
Comments
The IP-XACT importer does not currently support After reviewing the IP-XACT spec in a bit more detail, I think it may be difficult to add meaningful importer support for this. IP-XACT seems to do a much better job in capturing the semantics of HDL paths with its variety of SystemRDL spec authors did a really poor job of defining how HDL paths work to the point of them being almost useless. There is no sensible way to do path indexing, they limit to only two path views (RTL and gates), and the specification for the This means that if I were to add importer support, I suspect it would only work properly for a very narrow subset of IP-XACT features, rendering it pretty crippled. I suppose I could add support for simple cases, but it would be difficult to support the |
Hello All supporting the basic hdl_path specification from IP-XACT into RDL would already be very helpful! |
Hi,
What IPXACT xml tag is mapped to the hdl_path of a component? For example, I have an IPXACT file that one of its field supposed to have hdl_path, which is described in "pathSements" field, but the compiler doesn't seem to support it.
The text was updated successfully, but these errors were encountered: