Critical Issue
Description
If, on the Project Settings tab, Global reset is turned off, a transaction can be issued from a component in a reset domain that is not currently reset to a domain that is currently in reset. The transaction might be accepted by the interconnect logic within the domain that is currently in reset. The result is system-dependent, but can include system lockup the transaction appears to have been accepted, but actually is ignored.
Resolution
Carefully control reset deassertion sequencing among multiple reset domains and ensure that transactions are not issued across reset domain boundaries when some reset domains are in reset but others are not in reset.