Add picorv32 support for Alhambra board

[drtrigon]

According to YosysHQ/picorv32#92 picorv32 RISC soft core runs on Alhambra board. Is it possible to add support for this to FPGArduino?

[emard]

If picorv32 core can use the same gcc that works for our f32c-rv32 and approximately have the SOC (mmaped io, leds, spi, timers) also same or similar to f32c soc and are mapped preferrably to the same memory addresses then I'd be happy to add some board names, strings and compiler options to boards.txt and/or platform.txt Can somebody try our rv32 binaries on picorv32 and report if they work at least to make a led blinky?

…

On 10/22/18, drtrigon ***@***.***> wrote: According to YosysHQ/picorv32#92 picorv32 RISC soft core runs on Alhambra board. Is it possible to add support for this to FPGArduino? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #32

[drtrigon]

I try to help with whatever I can. The toolchain I used successfully is "RISC-V GNU toolchain and libraries for a pure RV32I target" as mentioned in https://github.com/cliffordwolf/picorv32#building-a-pure-rv32i-toolchain. It uses riscv32-unknown-elf-gcc, riscv32-unknown-elf-objcopy and from icestorm/icestudio toolchain iceprog (see https://github.com/FPGAwars/Alhambra-II-FPGA/blob/master/examples/picorv32/picosoc/Makefile).

[emard]

Can you try to use our f32c-rv32 compiled binary to get LED blinky on picorv32? In the meantime I probably should get picorv32 for ulx3s, I think it's already done at prjtrellis but haven't tried to download and compile I'm currently busy with new boards ULX3S and some hardware support around it

…

On 10/23/18, drtrigon ***@***.***> wrote: I try to help with whatever I can. The toolchain I used successfully is "RISC-V GNU toolchain and libraries for a pure RV32I target" as mentioned in https://github.com/cliffordwolf/picorv32#building-a-pure-rv32i-toolchain. It uses `riscv32-unknown-elf-gcc`, `riscv32-unknown-elf-objcopy` and from icestorm/icestudio toolchain `iceprog`. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #32 (comment)

[drtrigon]

Can you try to use our f32c-rv32 compiled binary to get LED blinky on picorv32?

I tried, but not with much success... I used code from a working project and just tried to replace the toolchain with yours, see attached Makefile.txt (the commented parts are the ones from the working toolchain for reference).

Running it results in (the .elf file has a size of 0 bytes):

$ make prog
../../fpgarduino/f32c/bin/riscv-elf-gcc -std=gnu11 -DHX8KDEMO -march=RV32I -Wl,-Bstatic,-T,sections.lds,--strip-debug -ffreestanding -nostdlib -o firmware.elf start.s firmware.c
collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped
$HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: /tmp/cc4XMh7D.o: ABI is incompatible with that of the selected emulation
$HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: failed to merge target specific data of file /tmp/cc4XMh7D.o
$HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: /tmp/cc39QdcM.o: ABI is incompatible with that of the selected emulation
$HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: failed to merge target specific data of file /tmp/cc39QdcM.o
make: *** [firmware.elf] Fehler 1

So my questions:

• Can you be more specific what I should test exactly (source files, commands for compiling, etc.)?
• Would it be possible to integrate the picorv32 icestorm/icestudio toolchain as it is open source too (e.g. the programmer could be needed)?

[emard]

Aiieeee segmentation fault in riscv linker :) Our riscv support is obviously not too functional no more testing from you needed, we must refresh this riscv support. Maybe better for alhambra board is to use another more stable riscv toolchain that you know works for your hardware It is no problem for integrate from licensing point of view but we lack of ing-hours to assemble all parts into stuff that works. I can package another riscv compiler and all required programming tools and libs, if you succeed with anything that leads to a blink led

…

On 10/26/18, drtrigon ***@***.***> wrote: > Can you try to use our f32c-rv32 compiled binary to get LED blinky on > picorv32? I tried, but not with much success... I used code from a working project and just tried to replace the toolchain with yours, see attached [Makefile.txt](https://github.com/f32c/arduino/files/2520503/Makefile.txt) (the commented parts are the ones from the working toolchain for reference). Running it results in (the .elf file has a size of 0 bytes): > $ make prog ../../fpgarduino/f32c/bin/riscv-elf-gcc -std=gnu11 -DHX8KDEMO -march=RV32I -Wl,-Bstatic,-T,sections.lds,--strip-debug -ffreestanding -nostdlib -o firmware.elf start.s firmware.c collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped $HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: /tmp/cc4XMh7D.o: ABI is incompatible with that of the selected emulation $HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: failed to merge target specific data of file /tmp/cc4XMh7D.o $HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: /tmp/cc39QdcM.o: ABI is incompatible with that of the selected emulation $HOME/Downloads/icestudio/fpgarduino/f32c/bin/../lib/gcc/riscv-elf/4.9.2/../../../../riscv-elf/bin/ld: failed to merge target specific data of file /tmp/cc39QdcM.o make: *** [firmware.elf] Fehler 1 So my questions: - Can you be more specific what I should test exactly (source files, commands for compiling, etc.)? - Would it be possible to integrate the picorv32 icestorm/icestudio toolchain as it is open source too (e.g. the programmer could be needed)? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #32 (comment)

[gornjas]

Our current riscv toolchain is exactly the same as the mips version, i.e. is gcc-7.2 based and should be perfectly fine. The question is why the OP has fetched the long obsoleted 4.9.2 toolchain - could that be a bug in our Arduino json / packaging?

[emard]

Yes, that's true we should package 7.2 into arduino....

…

On 10/27/18, Marko Zec ***@***.***> wrote: Our current riscv toolchain is exactly the same as the mips version, i.e. is gcc-7.2 based and should be perfectly fine. The question is why the OP has fetched the long obsoleted 4.9.2 toolchain - could that be a bug in our Arduino json / packaging? -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #32 (comment)

[gornjas]

How did that regression happen? I thought we already switched over to 7.2 a year ago, and were using gcc-6 based toolchains prior to that. The bm/package_fpga_index.json is clearly referencing 7.2 based toolchains.

I'm inclined to wipe out all the pre-7.2 .zip archives from the web, otherwise we'll be getting into this again and again...

[emard]

There were no regression, we only upgraded mips to 7.2 and riscv 7.2 I forgot :)

…

On 10/27/18, Marko Zec ***@***.***> wrote: How did that regression happen? I thought we already switched over to 7.2 a year ago, and were using gcc-6 based toolchains prior to that. The bm/package_fpga_index.json is clearly referencing 7.2 based toolchains. I'm inclined to wipe out all the pre-7.2 .zip archives from the web, otherwise we'll be getting into this again and again... -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #32 (comment)

[gornjas]

How's that possible? There's a single integrated toolchain archive for both mips + riscv toolchains per OS/architecture (win32, osx, lin32, lin64)? I.e. they are not downloaded separately, and there's no way to separate them in the json?

[gornjas]

I removed the pre gcc-7.2 toolchains from the bm on our website as a precaution for this to reocur.

[emard]

If zip toolchain is just removed this from bm installation directory without any other fix, fpgarduino board manager will no longer be installable effectively breaking everything :)

…

On 10/27/18, Marko Zec ***@***.***> wrote: I removed the pre gcc-7.2 toolchains from the bm on our website as a precaution for this to reocur. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #32 (comment)

[emard]

When I look better, we should have 7.2 toolchain for both mips+riscv in boards manager for bsd linux win osx so gcc 4.9 probably remained from some old installation?

…

On 10/27/18, The EMARD ***@***.***> wrote: If zip toolchain is just removed this from bm installation directory without any other fix, fpgarduino board manager will no longer be installable effectively breaking everything :) On 10/27/18, Marko Zec ***@***.***> wrote: > I removed the pre gcc-7.2 toolchains from the bm on our website as a > precaution for this to reocur. > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > #32 (comment)

[emard]

OK I found it linux 32-bit is really old toolchain from 2015 because Marko provided only linux-64 bit 7.2 and I had no better idea than to keep old toolchain for 32-bit systems otherwise they would compiletely break without any toolchain

…

On 10/27/18, The EMARD ***@***.***> wrote: When I look better, we should have 7.2 toolchain for both mips+riscv in boards manager for bsd linux win osx so gcc 4.9 probably remained from some old installation? On 10/27/18, The EMARD ***@***.***> wrote: > If zip toolchain is just removed this from bm installation directory > without > any other fix, fpgarduino board manager will no longer be installable > effectively breaking everything :) > > > On 10/27/18, Marko Zec ***@***.***> wrote: >> I removed the pre gcc-7.2 toolchains from the bm on our website as a >> precaution for this to reocur. >> >> -- >> You are receiving this because you commented. >> Reply to this email directly or view it on GitHub: >> #32 (comment) >

[drtrigon]

I got the toolchain from http://www.nxlab.fer.hr/fpgarduino/ and it was 64-bit:

• http://www.nxlab.fer.hr/dl/lin/64/ujprog
• http://www.nxlab.fer.hr/fpgarduino/bm/f32c-lin64-toolchain.tar.gz