Jump to content
rahuljn

Alternate register name can not be same as register name

Recommended Posts

Hi Folks

 

I have a scenarieo where the same register is interpreted in 2 different way depending on the working mode of the IP.

I choose alternate register to describe such behaviour but I see some limitations there. I can not have the same name of the register and its alternate register. Why this is forbidden in the schema ?

 

Thanks

RahulJn

Share this post


Link to post
Share on other sites

If I understand well, the reason for such schema constraints is to avoid name collisions in generated files

But in the above scenario, at a time(i.e. in a given mode) either the main register or one of its alternate register will be valid. so any way there will no naming collision so why there is such constrains

 

Thanks

Rahuljn

Share this post


Link to post
Share on other sites

Hi Rahuljn,

 

This is a known bug in the constraints defined for the schema. Since the fix does not impact the schema syntax in any way, we have already independently proposed a fix that should cause an update to the hosted schema files in the near future.

 

Thanks,

Mark

Share this post


Link to post
Share on other sites

Hi Mark,

 

So after the fix, I can have two registers at the same offset with the same name.So in IP-Xact, I will have a register and one alternate register both having the same name

Can you confirm please ?

 

In summary, it is possible to have register and all of its alternate registers can have the same name.

Am I right ?

 

 

Thanks

RahulJn

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×