Is there an existing core-v-mcu bug for this?
Bug Description
This issue was discovered during the effort to update the User Manual by @cst-jayesht. See this discussion in pull-request #350:
the err_o signal is left unconnected internally, so its behavior is undefined.
The purpose of this Issue is to flag that state of affairs and possibly update it in a future release of this project.