-
Notifications
You must be signed in to change notification settings - Fork 71
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
Using native uvm classes without extended classes #49
Comments
What's wrong with using the extended _rdl classes? They can be used with existing environments because they are derived from uvm_reg* base classes. |
Thanks for the quick reply. There are issues at run time because as an example I completely change one of our uvm_blocks to extended rdl classes. Just a couple of examples, I haven't debugged too much but I was hoping for a plug and play integration into our ral sequences. In this example, apb_timer_reg_block was changed to using _rdl classes. However, apb_subsys_reg_block is still uvm_reg_block; As intended, we dont want to re-generate all existing working uvm_reg_blocks to support _rdl. Thus you cannot cast back two different types;
In this example, we use reg_map to append block submaps. Not sure why this class is not existing.
Thanks, Bo |
Uses native uvm ral classes in all cases, basically creates a model without heavy model extensions that uses uvm_reg_fields rather than the cut down classes of the lite1 model.
Checked in a first cut in 180619.01 (uvm_model_mode = native). |
Thanks Scott, verified to be a simple integration into our current uvm_regs. Closing. |
Hello,
Allow an option to generate uvm registers with native UVM class register, uvm_reg and uvm_reg_fields, as part of uvm_reg_block;
The capabilities of lite1 is limited (uvm_field_lite vs uvm_reg_field) but heavy1 is too much such that you would need to change existing UVM RAL environments because it is already using uvm_reg_block in multiple locations, with sequencers and adapters.
This way ordt can be used to generate uvm reg blocks for existing old environments and also be able to accommodate new uvm reg flow with extended rdl classes.
Thanks, Bo
The text was updated successfully, but these errors were encountered: