V93k Testsuite parameter "site_match"

[halinim]

This "site_match" paramter is currently a constant and set to value 2. This means "Auto" for v93k.

"Auto" does the following:

• Site_Match = OFF in case of shared pins
• SIte_Match = ON in case of non-shared pins -> This allows asynchronous site execution, but leading to test time overhead
  (When match loop patterns are used, site match should be ON )

When no shared pins and no match_loop patterns are being used, there will be a significant test time overhead which can increase test time by. ~25-30% for 96-sites.

Would it be possible to pass a setting of "Site_Match= Off (0) by app level? When no Site_Match value is defined by app,, it should keep the default setting i..e Auto (2)

[info-rchitect]

This isn't the first parameter that has been hardcoded. It would be good to audit all of the parameters to check for defaulting to a constant.

[redxeth]

Agreed-- I have a fix in the works for allowing adding a program_comment -- was goint to add accessors so that it can be changed at the app level if desired. So maybe I can fix this as well.

[redxeth]

@halinim it appears that you can modify the site_match parameter when you create an instance/testsuite. Basically anything that is in this ATTRS hash can be used.

You would need to update interface to support modifying it as is done in the example interface built in to OrigenTesters (for self-test purposes):

https://github.com/Origen-SDK/origen_testers/blob/master/lib/origen_testers/test/interface.rb#L110

You'd do it like this in that example:

ts.site_match = 0

And that's it.

I confirmed it appears to work. We can chat about how to implement on your current projects.