Open sunnystormy opened 3 years ago
Try renaming the riscv-gcc prefix in this cross.mk to match one of your 32bit toolchains. riscv32-unknown-elf-
sounds like it would work in this case. I haven't tried building riscv-gcc from source though for this project, I just used the xPack binaries which I've had no problem with.
I'm currently trying to get a simulator built to run the Miyamoto-Sprint project. When I run the makefile for the simulator with the verilator switch I get the following output:
riscv-none-embed-gcc -Wall -flto -march=rv32i -mabi=ilp32 -Os -ffreestanding -nostdlib -I../firmware/../software/lib/ -I../firmware/../software/common/ -DBOOT_DISPLAY -T ../firmware/boot.lds -o ../firmware/boot_multi.elf ../firmware/boot.S ../firmware/bootprint.c ../firmware/winbond_configure.S ../firmware/issi_configure.S ../firmware/flash_detect.S ../firmware/../software/common/font.c ../firmware/../software/lib/vdp.c ../firmware/../software/lib/assert.c make: riscv-none-embed-gcc: No such file or directory make: *** [../firmware/boot.mk:89: ../firmware/boot_multi.elf] Error 127
None of the risc-v toolchains I have installed have the designation I see in the emitted message. My newlib toolchains start with "riscv32/64-unknown-elf-*". Is there a specific configuration I need in order to produce the toolchain used here?
Thank you for your help!