Fig. 1. OpenHW: CORE-V processor features for CVE4 & CVA6
[/vc_column_text][/vc_column][/vc_row][vc_row type="in_container" full_screen_row_position="middle" column_margin="default" column_direction="default" column_direction_tablet="default" column_direction_phone="default" scene_position="center" text_color="dark" text_align="left" row_border_radius="none" row_border_radius_applies="bg" overlay_strength="0.3" gradient_direction="left_to_right" shape_divider_position="bottom" bg_image_animation="none"][vc_column column_padding="no-extra-padding" column_padding_tablet="inherit" column_padding_phone="inherit" column_padding_position="all" background_color_opacity="1" background_hover_color_opacity="1" column_shadow="none" column_border_radius="none" column_link_target="_self" gradient_direction="left_to_right" overlay_strength="0.3" width="1/1" tablet_width_inherit="default" tablet_text_alignment="default" phone_text_alignment="default" column_border_width="none" column_border_style="solid" bg_image_animation="none"][vc_column_text]To help and support SoC design teams looking to adopt CORE-V, the OpenHW Group has established a number of working groups to address the key areas of IP development, ecosystem tools and developer resources. In order to address the typical concerns of quality and usability of open source hardware IP, the OpenHW Group Verification Task Group has published the complete verification test plan, see Fig 2. In addition, to ensure the smooth adoption within the current SoC designs flows, the DV plan is based on industry best practices and leading commercial tools. To support adopters looking to further modify or extend the designs, all the scripts and test files are also made available.[/vc_column_text][/vc_column][/vc_row][vc_row type="in_container" full_screen_row_position="middle" column_margin="default" column_direction="default" column_direction_tablet="default" column_direction_phone="default" scene_position="center" text_color="dark" text_align="left" row_border_radius="none" row_border_radius_applies="bg" overlay_strength="0.3" gradient_direction="left_to_right" shape_divider_position="bottom" bg_image_animation="none"][vc_column column_padding="no-extra-padding" column_padding_tablet="inherit" column_padding_phone="inherit" column_padding_position="all" background_color_opacity="1" background_hover_color_opacity="1" column_shadow="none" column_border_radius="none" column_link_target="_self" gradient_direction="left_to_right" overlay_strength="0.3" width="1/1" tablet_width_inherit="default" tablet_text_alignment="default" phone_text_alignment="default" column_border_width="none" column_border_style="solid" bg_image_animation="none"][image_with_animation image_url="21111" animation="None" hover_animation="none" alignment="" border_radius="none" box_shadow="none" image_loading="default" max_width="100%" max_width_mobile="default"][vc_column_text]Fig. 2. OpenHW: CORE-V verification test bench UVM environment
[/vc_column_text][/vc_column][/vc_row][vc_row type="in_container" full_screen_row_position="middle" column_margin="default" column_direction="default" column_direction_tablet="default" column_direction_phone="default" scene_position="center" text_color="dark" text_align="left" row_border_radius="none" row_border_radius_applies="bg" overlay_strength="0.3" gradient_direction="left_to_right" shape_divider_position="bottom" bg_image_animation="none"][vc_column column_padding="no-extra-padding" column_padding_tablet="inherit" column_padding_phone="inherit" column_padding_position="all" background_color_opacity="1" background_hover_color_opacity="1" column_shadow="none" column_border_radius="none" column_link_target="_self" gradient_direction="left_to_right" overlay_strength="0.3" width="1/1" tablet_width_inherit="default" tablet_text_alignment="default" phone_text_alignment="default" column_border_width="none" column_border_style="solid" bg_image_animation="none"][vc_column_text]A test plan represents not just the operational steps to complete the test and verification tasks but is also a fundamental reflection of the quality of the final deliverables. Any deficiencies or oversights in the test plan may result in defects remaining in the final products. In traditional commercial activities, the test plans and tests cases are considered as highly valued IP and not shared externally with customers or users, in fact the test methodology itself is considered a strategic competitive advantage. As open source processor IP, the CORE-V deliverables can be used as-is or as a basis for further design modifications and enhancements. Thus, the complete OpenHW CORE-V test plan and test bench is provided to help support adopters and may be used to help and assist in developing SoC level tests. The Imperas reference model covers the complete envelope of the RISC-V specification including user and privilege modes. To support processor verification, the Imperas reference model is encapsulated within SystemVerilog for test benches to compare the RTL against the reference model. The test bench also supports a step-and-compare approach which allows interactive debugging to help investigate resolve issues. In automated regression tests, the reference model can be set-up to cover implementation options across the entire range of processor feature sets and options. The configuration flexibility is just one of the many differences between IP verification and adopters DV plans for a targeted implementation within an SoC or FPGA designs. To support the team effort across multiple geographical locations and corporate members, the OpenHW Verification Working Group has leveraged the cloud-based EDA platform of Metrics Technologies. The Metrics cloud-based methodology supports both collaboration across the team members, but also the intensive compute resources required for extensive processor verification. Using a cloud-based infrastructure permits a flexible approach to the simulation capacity which can scale from the initial set-up of test cases to running the extensive verification tasks. As the group can share results, coverage and log files within the platform, it greatly helps both the communications across the distributed team and helps maintain a clear record of all results as key milestones on coverage are achieved. A recent paper estimated that simulation of 1015 (peta) instructions as a guide to the capacity that is required for processor IP verification. More information and a full demonstration of the design tools and flows is featured in a recent OpenHW TV (episode 1): ‘Open source IP verification’ which is available at https://www.openhwgroup.org/resources/openhwtv/ The OpenHW Group members are actively developing the CORE-V processor IP, verification and ecosystem support for SoC adopters. To learn more about the OpenHW Group and all the contributions from the supporting members please visit https://www.openhwgroup.org Author: Kevin McDermott VP Marketing, Imperas Software[/vc_column_text][/vc_column][/vc_row]]]>