This video demonstrates the behavior and usage of GO_ID registers in MBIST design
The tool determines the size of the GO_ID depending on the location of the comparator.
The GO_ID register size would be the data bit width for the largest memory within the test step
In case of Shared comparators, the GO_ID register size would be the sum of all memories data bits width in a test step.
You can set the comparator location from the DftSpecifications
Tessent Shell Reference Manual (siemens.com)
To set the local comparators per go id property check TS manual
Tessent Shell Reference Manual (siemens.com)
To set the shared comparators per go id property check TS manual
Tessent Shell Reference Manual (siemens.com)
GO_ID registers can be sticky and non-sticky,
Sticky means that the content of the GO_ID register contains the cumulative values from the comparators from all strobes during the MemoryBIST run which is the case in Go/NoGo Mode.
Non-sticky means that the content of the GO_ID register contains the comparator values from the last strobe only which is the case in Stop-On-Error Mode.
For more information, please get back to TMB manual
Tessent MemoryBIST User's Manual (siemens.com)
Tessent MemoryBIST User's Manual (siemens.com)
N.B: check the Controller/ Memory interface generated RTL files to see specifically how the IO are connected to GO_ID register bits
N.B: you can also detect which specific memory is failing with by using compare_memory_go property