Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extension `zicsr' required #125

Open
ahmdotm opened this issue Jun 19, 2024 · 2 comments
Open

extension `zicsr' required #125

ahmdotm opened this issue Jun 19, 2024 · 2 comments

Comments

@ahmdotm
Copy link

ahmdotm commented Jun 19, 2024

I used --with-arch=rv64imac_zicsr --with-abi=lp64 for my toolchain configuration and I still get this:
ized opcode csrr a6,mcycleh', extension zicsr' required
make: *** [/home/othman/Reev_EH1/Cores-VeeR-EH1/tools/Makefile:182: printf.o] Error 1

@noobwei
Copy link

noobwei commented Dec 25, 2024

I don't know if it's accurate but a similar issue happened to me.

I used gcc in https://github.com/riscv-collab/riscv-gnu-toolchain and changed the prefix to /opt/riscv/bin/riscv64-unknown-linux-gnu
Then I got Error: unrecognized opcode csrw 0x7c0,x1, extension zicsr required

I didn't succeed in adding ziscr to the default Makefile. It didn't make sense to simply say ABI = -mabi=ilp32 -march=rv32imc_zicsr, because I got /opt/riscv/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: /opt/riscv/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/../../../../riscv64-unknown-linux-gnu/lib/libgcc_s.so.1: error adding symbols: file in wrong format'

Merry Christmas to you all btw.

@noobwei
Copy link

noobwei commented Dec 26, 2024

I have fixed my issue by rebuilding the toolchain and using --with-arch=rv32imc_zicsr --with-abi=ilp32.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants