configuration-structure icon indicating copy to clipboard operation
configuration-structure copied to clipboard

Published 20 hours ago • verified publisher icon riscv

The way of storage for CS (Configuration Structure) and mconfigtr CSR

Open zhangdujiao opened this issue 9 months ago • 1 comments

  1. What are the requirements or suggestions for the CS storage method: RAM, ROM, or non-volatile efuse?

  2. Is the mconfigtr CSR burned into efuse after tape-out? or it is written into firmware after tape-out, or it can be written by firmware after the boot?

  3. Whether the mconfigtr can be read only after the core is powered on, or it can be read by a debugger from outside the cluster?

zhangdujiao avatar May 11 '24 06:05 zhangdujiao

  1. Whether the mconfigtr can be read only after the core is powered on, or it can be read by a debugger from outside the cluster?

I would expect that the external debugger would find the address of CS by reading confstrptr in the Debug Module.

pdonahue-ventana avatar May 11 '24 15:05 pdonahue-ventana

  1. Whether the mconfigtr can be read only after the core is powered on, or it can be read by a debugger from outside the cluster?

I would expect that the external debugger would find the address of CS by reading confstrptr in the Debug Module.

yes, thanks, I want to know how to store the CS in SoC, maybe the efuse or other Nonvolatile memory？

zhangdujiao avatar Jun 04 '24 06:06 zhangdujiao