You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current XML output includes the Instance view but does not include the "data dictionary "
ie
addrmap counters {
counter_t transaction_cnt[10];
counter_t error_cnt[5];
};
so the xml will list tranaction_cnt and error_cnt but there is no indication that register def is the same.
I would be useful to include a "type" tag in the instances and a "data type" tree in the xml or a parallel xml file.
The text was updated successfully, but these errors were encountered:
Understand request - it has some benefits.
Just fyi, a couple reasons this feature was considered lower priority:
rdl allows instance info to be overriden for many parameters via dynamic assign, eg could do error_cnt->reset=0x1f which makes the 2 instances of counter_t different
rdl allows anonymous instances, which have no type
if true, adds a component tag containing component id path for each
instance that has a non-anonymous component id. Addresses a subset of
issue #52 - allows instances derived from the same component to be
identified.
The current XML output includes the Instance view but does not include the "data dictionary "
ie
addrmap counters {
counter_t transaction_cnt[10];
counter_t error_cnt[5];
};
so the xml will list tranaction_cnt and error_cnt but there is no indication that register def is the same.
I would be useful to include a "type" tag in the instances and a "data type" tree in the xml or a parallel xml file.
The text was updated successfully, but these errors were encountered: