RV32E toolchain

[akhilesh Kotwaliwale]

Hi all,

I am trying to configure RV32E toolchain with picorv32 on my local system. But the linker is throwing an error while mapping as shown below.

Can anyone kindly help me finding bugs?

Thank you.

[Tommy Murphy]

Where did you get that toolchain from?

At 8.2.0 it seems very old.

And it also looks like a bare metal toolchain but is being passed Linux toolchain flags and seems to be looking for glibc rather than newlib which is odd.

I would start by looking for a more recent toolchain.

[martin ribelotta]

Here: https://github.com/xpack-dev-tools/riscv-none-elf-gcc-xpack/releases

This bundles a multilib toolchain with rv32e support.

This is the result of execute riscv-none-elf-gcc -print-multi-lib:

rv32e/ilp32e;@march=rv32e@mabi=ilp32e
rv32ea/ilp32e;@march=rv32ea@mabi=ilp32e
rv32eac/ilp32e;@march=rv32eac@mabi=ilp32e
rv32ec/ilp32e;@march=rv32ec@mabi=ilp32e
rv32em/ilp32e;@march=rv32em@mabi=ilp32e
rv32ema/ilp32e;@march=rv32ema@mabi=ilp32e
rv32emac/ilp32e;@march=rv32emac@mabi=ilp32e
rv32emc/ilp32e;@march=rv32emc@mabi=ilp32e
rv32i/ilp32;@march=rv32i@mabi=ilp32
rv32ia/ilp32;@march=rv32ia@mabi=ilp32
rv32iac/ilp32;@march=rv32iac@mabi=ilp32
rv32iaf_zicsr/ilp32f;@march=rv32iaf_zicsr@mabi=ilp32f
rv32iafc_zicsr/ilp32f;@march=rv32iafc_zicsr@mabi=ilp32f
rv32iafd_zicsr/ilp32d;@march=rv32iafd_zicsr@mabi=ilp32d
rv32iafdc_zicsr/ilp32d;@march=rv32iafdc_zicsr@mabi=ilp32d
rv32ic/ilp32;@march=rv32ic@mabi=ilp32
rv32if_zicsr/ilp32f;@march=rv32if_zicsr@mabi=ilp32f
rv32ifc_zicsr/ilp32f;@march=rv32ifc_zicsr@mabi=ilp32f
rv32ifd_zicsr/ilp32d;@march=rv32ifd_zicsr@mabi=ilp32d
rv32ifdc_zicsr/ilp32d;@march=rv32ifdc_zicsr@mabi=ilp32d
rv32im/ilp32;@march=rv32im@mabi=ilp32
rv32ima/ilp32;@march=rv32ima@mabi=ilp32
rv32imaf_zicsr/ilp32f;@march=rv32imaf_zicsr@mabi=ilp32f
rv32imafc_zicsr/ilp32f;@march=rv32imafc_zicsr@mabi=ilp32f
rv32imafd_zicsr/ilp32d;@march=rv32imafd_zicsr@mabi=ilp32d
rv32imafdc_zicsr/ilp32d;@march=rv32imafdc_zicsr@mabi=ilp32d
rv32imc/ilp32;@march=rv32imc@mabi=ilp32
rv32imf_zicsr/ilp32f;@march=rv32imf_zicsr@mabi=ilp32f
rv32imfc_zicsr/ilp32f;@march=rv32imfc_zicsr@mabi=ilp32f
rv32imfd_zicsr/ilp32d;@march=rv32imfd_zicsr@mabi=ilp32d
rv32imfdc_zicsr/ilp32d;@march=rv32imfdc_zicsr@mabi=ilp32d
rv64i/lp64;@march=rv64i@mabi=lp64
rv64ia/lp64;@march=rv64ia@mabi=lp64
rv64iac/lp64;@march=rv64iac@mabi=lp64
rv64iaf_zicsr/lp64f;@march=rv64iaf_zicsr@mabi=lp64f
rv64iafc_zicsr/lp64f;@march=rv64iafc_zicsr@mabi=lp64f
rv64iafd_zicsr/lp64d;@march=rv64iafd_zicsr@mabi=lp64d
rv64iafdc_zicsr/lp64d;@march=rv64iafdc_zicsr@mabi=lp64d
rv64ic/lp64;@march=rv64ic@mabi=lp64
rv64if_zicsr/lp64f;@march=rv64if_zicsr@mabi=lp64f
rv64ifc_zicsr/lp64f;@march=rv64ifc_zicsr@mabi=lp64f
rv64ifd_zicsr/lp64d;@march=rv64ifd_zicsr@mabi=lp64d
rv64ifdc_zicsr/lp64d;@march=rv64ifdc_zicsr@mabi=lp64d
rv64im/lp64;@march=rv64im@mabi=lp64
rv64ima/lp64;@march=rv64ima@mabi=lp64
rv64imac/lp64;@march=rv64imac@mabi=lp64
rv64imaf_zicsr/lp64f;@march=rv64imaf_zicsr@mabi=lp64f
rv64imafc_zicsr/lp64f;@march=rv64imafc_zicsr@mabi=lp64f
rv64imafd_zicsr/lp64d;@march=rv64imafd_zicsr@mabi=lp64d
rv64imafdc_zicsr/lp64d;@march=rv64imafdc_zicsr@mabi=lp64d
rv64imc/lp64;@march=rv64imc@mabi=lp64
rv64imf_zicsr/lp64f;@march=rv64imf_zicsr@mabi=lp64f
rv64imfc_zicsr/lp64f;@march=rv64imfc_zicsr@mabi=lp64f
rv64imfd_zicsr/lp64d;@march=rv64imfd_zicsr@mabi=lp64d
rv64imfdc_zicsr/lp64d;@march=rv64imfdc_zicsr@mabi=lp64d

You can see the support of rv32emac and all of their variants (e, ec, emc, etc). The @march, @mabi indicate the combination of -march=... and -mabi=... in the command line that select the correct mode.

--
You received this message because you are subscribed to the Google Groups "RISC-V ISA Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isa-dev+u...@groups.riscv.org.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/isa-dev/LO0P265MB6866C115A8D6B0362C2F686FF9C29%40LO0P265MB6866.GBRP265.PROD.OUTLOOK.COM.

[Tommy Murphy]

That link is to a toolchain that's much more recent than the one in your screenshot?

---

From: martin ribelotta <martinr...@gmail.com>
Sent: Friday, January 13, 2023 12:13:29 PM
To: Tommy Murphy <tommy_...@hotmail.com>
Cc: akhilesh Kotwaliwale <akhil...@gmail.com>; RISC-V ISA Dev <isa...@groups.riscv.org>
Subject: Re: [isa-dev] RV32E toolchain

 

[martin ribelotta]

Yes, that's it. The last version is gcc 12.2.0 but you have 11.x, 10.x and 8.x series

[Tommy Murphy]

@akhilesh Kotwaliwale - can you post (attach) a full build log to show what exactly is going on please?

Also - can you post logs rather than screenshots as they are very difficult to read on some devices and for some people.

[akhilesh Kotwaliwale]

Hey,

I have followed your lead Martin Ribelotta, and it requires me to have glibc 2.28 for ubuntu 18.04.

While trying to do so, I got stuck and confused what the error is.

Attaching hereby the complte build log.

[Tommy Murphy]

The latest xPack Project RISC-V toolchain doesn't require GLIBC v2.28:

https://xpack.github.io/blog/2022/08/30/riscv-none-elf-gcc-v12-2-0-1-released/

What happens when you try that?

---

From: akhilesh Kotwaliwale <akhil...@gmail.com>
Sent: Monday, January 16, 2023 8:39:47 AM
To: RISC-V ISA Dev <isa...@groups.riscv.org>
Cc: Martin Ribelotta <martinr...@gmail.com>; akhilesh Kotwaliwale <akhil...@gmail.com>; RISC-V ISA Dev <isa...@groups.riscv.org>; Tommy Murphy <tommy_...@hotmail.com>

Subject: Re: [isa-dev] RV32E toolchain

[akhilesh Kotwaliwale]

I require it for installing xpm.

[Tommy Murphy]

> I require it for installing xpm.

You don't need xpm.

Just download the toolchain archive and extract it.

[akhilesh Kotwaliwale]

Ok. I have done that. I guess the toolchain is built. But the error while running simulation.

vvp -N testbench.vvp
TRAP after 8224 clock cycles
ERROR!
Makefile:25: recipe for target 'test' failed
make: *** [test] Error 1

[Tommy Murphy]

Sorry, I don't know what vvp is.

This, or something related?

https://github.com/riscv-verification/RVVI#the-virtual-verification-peripherals-used-in-the-test-bench---rvvi-vvp

It would help to provide more detailed context and details of what you're trying to run/simulate here.

Doesn't this vvp provide options to get more details - e.g. verbose log etc.?

[Tommy Murphy]

Oh - is vvp here Icarus Verilog?

If so, then wouldn't the -v flag help?

And maybe some of the other diagnostic flags?

https://linux.die.net/man/1/vvp

[akhilesh Kotwaliwale]

It is an error in verilog testbench. The variable test_passed is not receiving the value 1. I am now trying to debug.

[Tommy Murphy]

Did you see this already?

https://github.com/YosysHQ/picorv32#makefile-and-testbenches

"Note: The test bench is using Icarus Verilog. However, Icarus Verilog 0.9.7 (the latest release at the time of writing) has a few bugs that prevent the test bench from running. Upgrade to the latest github master of Icarus Verilog to run the test bench."

[akhilesh Kotwaliwale]

Yes i did. And I have icarus verilog version  10.1