dft: implementing interface to support different test modes
This is a refactoring change + public API change where we start supporting different tests modes. The test mode currently does nothing except for independendly architect and stitch each test mode.
In the future, different tests modes may have different types of scan (ex: internal scan, scan compression, boundary scan, etc) and may support to include/exclude cells in certain modes.
clang-tidy review says "All clean, LGTM! :+1:"
clang-tidy review says "All clean, LGTM! :+1:"
It would be nice to add a test with multiple test modes even if it doesn't do much yet.
It would be nice to add a test with multiple test modes even if it doesn't do much yet.
There is not much to test now as I just wanted to finish the config hierarchy for other developers.
Test modes need more work to be implements. For one we need to add new ports to select the current active mode, ways to include/exclude cells in each test mode and add muxes in the scan chain signals depending on what cells are part of what test mode.
For sure more work than can be done in just one PR :)
I added an error message notifying that we don't currently support more than one test mode.
clang-tidy review says "All clean, LGTM! :+1:"
clang-tidy review says "All clean, LGTM! :+1:"
@fgaray this seems to have gotten lost and now has a bunch of merge conflicts. Is this something we should try to cleanup and get merged?
(@AcKoucher FYI)