Is this the expected outcome? My assumption is the tool would list all the problem bits and it would be deterministic, but perhaps I am not understanding the nature of the tool correctly.
To reproduce, you can copy these files (temporarily staged in a weird directory, will be removed eventually):
I'm running Vivado 2022.1 and Python 3.9, and invoking the tool with this command:
python3.9 find_fault_bits.py betrusted_soc.bit betrusted_soc_route.dcp -r -d
Running off of commit 415fab146e3f50931b5c3ec6e38277ad1fb76908If I run this command twice in a row, I get different outputs for e.g.
betrusted_soc_sample_bits.json
.One run, for example, yields this:
and the next will give this
Here's what the diff of the two is:
Is this the expected outcome? My assumption is the tool would list all the problem bits and it would be deterministic, but perhaps I am not understanding the nature of the tool correctly.
To reproduce, you can copy these files (temporarily staged in a weird directory, will be removed eventually):
https://ci.betrusted.io/trng/betrusted_soc_route.dcp https://ci.betrusted.io/trng/betrusted_soc.bit