Wait one clock after SoC reset drops to start cache access raptor-wip
authorRaptor Engineering Development Team <support@raptorengineering.com>
Sat, 16 Apr 2022 18:39:57 +0000 (13:39 -0500)
committerRaptor Engineering Development Team <support@raptorengineering.com>
Sat, 16 Apr 2022 18:44:06 +0000 (13:44 -0500)
commitc1a38c32b850f96c0d83da0a5cd3c04285271147
tree71a7649c16b79ca61404e1618d4a23bb0ed932bd
parentb25bcf06665b246515186a10b954dcea24df5bf4
Wait one clock after SoC reset drops to start cache access

When the SoC reset drops, it may take up to one clock cycle
for the issuer to get the core into a known good state with
a valid PC that points to the desired reset vector.  As a
result, there is a risk the ICache starts loading a cache line
from an invalid Wisbbone address, potentially locking the bus
or causing a boot delay.

Wait one clock cycle after the SoC reset drops to start
issuing any instructions, thereby also waiting the same
amount of time to start fetching any instructions.

With the other related commits, this fully fixes Bug #812
src/soc/simple/issuer.py