diff options
| author | Evgeniy Naydanov <evgeniy.naydanov@syntacore.com> | 2025-02-25 20:08:44 +0300 |
|---|---|---|
| committer | Evgeniy Naydanov <evgeniy.naydanov@syntacore.com> | 2025-03-07 11:27:34 +0300 |
| commit | 45231117b8686af3b896c9645a7b5b7b3b8e1cfc (patch) | |
| tree | c694850c9871e2fb624375c71b108e104485f474 /git-hooks/commit-msg | |
| parent | e88edb71a54b8b831bc62adc41dae47f23003e02 (diff) | |
| download | riscv-openocd-45231117b8686af3b896c9645a7b5b7b3b8e1cfc.zip riscv-openocd-45231117b8686af3b896c9645a7b5b7b3b8e1cfc.tar.gz riscv-openocd-45231117b8686af3b896c9645a7b5b7b3b8e1cfc.tar.bz2 | |
src/target/riscv: error out of the `examine()` in case `abits` is zero
The spec requires `abits` to be no less then 7 ( [3.1. Debug Module
Interface (DMI)]):
> The DMI uses between 7 and 32 address bits
Commit a450a7d4966a19c48b2543810f5b8370af6383e5 ("Fix data types around
batch.{c,h}") introduced a check that issues a warning if `abits` is
less then 7. The reason it's a warning and not an error -- on Spike
`abits` is 6.
However, if the examination is to proceed when `abits` is zero, an
assert in `get_dmi_scan_length()` will trigger when attempting to
communicate over DMI.
Link: https://github.com/JanMatCodasip/riscv-openocd/blob/a450a7d4966a19c48b2543810f5b8370af6383e5/src/target/riscv/batch.c#L25
It's impossible to communicate over DMI with `abits == 0`, so an error
is returned instead of a warning in this case.
Change-Id: Ice4622adccfc8304b37bc678253cc19d8ac1457e
Signed-off-by: Evgeniy Naydanov <evgeniy.naydanov@syntacore.com>
Diffstat (limited to 'git-hooks/commit-msg')
0 files changed, 0 insertions, 0 deletions