coreplex: CacheBlockOffsetBits was wrong!
This bug is ancient. I don't understand how it never mattered before. Anyway, in processors with a custom CacheBlockBytes, this value is wrong! The symptom is that TL1 components end up missing high address bits. This causes, for example, a system to jump to 0 instead of RAM. I don't understand how this very serious bug did not cause problems before.
This commit is contained in:
parent
549e006988
commit
0baa1c9a45
@ -109,7 +109,7 @@ class BaseCoreplexConfig extends Config (
|
|||||||
case BroadcastConfig => BroadcastConfig()
|
case BroadcastConfig => BroadcastConfig()
|
||||||
case BankedL2Config => BankedL2Config()
|
case BankedL2Config => BankedL2Config()
|
||||||
case CacheBlockBytes => 64
|
case CacheBlockBytes => 64
|
||||||
case CacheBlockOffsetBits => log2Up(here(CacheBlockBytes))
|
case CacheBlockOffsetBits => log2Up(site(CacheBlockBytes))
|
||||||
case EnableL2Logging => false
|
case EnableL2Logging => false
|
||||||
case _ => throw new CDEMatchError
|
case _ => throw new CDEMatchError
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user