Presentation
Automated "Spec to Sign-Off" of CSR and Integration Verification at SOC
DescriptionMotivation:
Initial milestone of SOC verification includes the verification of the integrity check and register access checks of all IP's. To reduce the closure time of verification with improved quality and reduced resource effort, automation is deployed. This enables backend team to start on floor planning and subsequent activities ahead of time in the project life cycle which results in early closure of project.
Issue with current approach:
Release to release test coding - Specification changes due to addition/removal of IP's as a result of architecture changes
Register addition/removal
Change of security policies for any given IP
Manual coding of tests are error prone and time consuming
Dealing with local changes made [check-in/check-out issue]- prone to data loss
Ineffective Disk space usage
Attribute sheet to be updated manually and track for the same
Process and Pay-OFF of automation:
Achieving efficient and effective closure of initial phase of verification by adopting the Maximum automation, centralized Execution and distributed Debug involves
Automated test generation by considering the specification for register access and integration check
Centralized regression launch for all blocks on every label release
Failures dispatched to dedicated owners for timely debug
All generated code is maintained in repository by auto check-in
Initial milestone of SOC verification includes the verification of the integrity check and register access checks of all IP's. To reduce the closure time of verification with improved quality and reduced resource effort, automation is deployed. This enables backend team to start on floor planning and subsequent activities ahead of time in the project life cycle which results in early closure of project.
Issue with current approach:
Release to release test coding - Specification changes due to addition/removal of IP's as a result of architecture changes
Register addition/removal
Change of security policies for any given IP
Manual coding of tests are error prone and time consuming
Dealing with local changes made [check-in/check-out issue]- prone to data loss
Ineffective Disk space usage
Attribute sheet to be updated manually and track for the same
Process and Pay-OFF of automation:
Achieving efficient and effective closure of initial phase of verification by adopting the Maximum automation, centralized Execution and distributed Debug involves
Automated test generation by considering the specification for register access and integration check
Centralized regression launch for all blocks on every label release
Failures dispatched to dedicated owners for timely debug
All generated code is maintained in repository by auto check-in
Event Type
Engineering Poster
Networking
TimeMonday, June 235:00pm - 6:00pm PDT
LocationEngineering Posters, Level 2 Exhibit Hall