| commit | 277b210dd86636cc910bf6cd9a5477d01a10603f | |
| author | Alistair Francis <alistair.francis@wdc.com> | |
| Wed, 14 Sep 2022 10:11:06 +0000 (14 12:11 +0200) | ||
| committer | Alistair Francis <alistair@alistair23.me> | |
| Mon, 26 Sep 2022 21:04:38 +0000 (27 07:04 +1000) | ||
| tree | 89d327e0332c45272ba5d97fdba033af1386f9ec | treesnapshot (tar.gz zip) |
| parent | 4c0f0b6619126637e802f07c9fe8e9fffbc1c4bb | commitdiff |
target/riscv: Set the CPU resetvec directly
Instead of using our properties to set a config value which then might
be used to set the resetvec (depending on your timing), let's instead
just set the resetvec directly in the env struct.
This allows us to set the reset vec from the command line with:
-global driver=riscv.hart_array,property=resetvec,value=0x20000400
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20220914101108.82571-2-alistair.francis@wdc.com>
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Instead of using our properties to set a config value which then might
be used to set the resetvec (depending on your timing), let's instead
just set the resetvec directly in the env struct.
This allows us to set the reset vec from the command line with:
-global driver=riscv.hart_array,property=resetvec,value=0x20000400
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20220914101108.82571-2-alistair.francis@wdc.com>
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
| target/riscv/cpu.c | diffblobblamehistory | |
| target/riscv/cpu.h | diffblobblamehistory | |
| target/riscv/machine.c | diffblobblamehistory |