Could someone here help me test https://github.com/efabless/caravel_board/tree/main/firmware_vex/gpio_test

Hi. I'm trying that but when I do the make flash I got "No matching FTDI devices on USB bus! ". Any idea why that happen? the IO test worked and I got the config file

you need to reconfigure the setup for flashing firmware. unplug the hat from nucleo, swap over the power jumpers and plug in the usb cable

Ok, I done that

you have both power jumpers on 'main' ?

I get the following error with the default riscv64 toolchain from debian

../crt0_vex.S: Assembler messages:
../crt0_vex.S:59: Error: unrecognized opcode `csrw mtvec,a0', extension `zicsr' required
../crt0_vex.S:87: Error: unrecognized opcode `csrw mie,a0', extension `zicsr' required
../irq_vex.h: Assembler messages:
../irq_vex.h:31: Error: unrecognized opcode `csrw 3008,a5', extension `zicsr' required

Hi, sorry for the late response, yes both jumpers are on main. Doing the make flash exits before doing something. The first flash worked but now I can not stop the LED flash. I tried to change to other chip but same behavior, so I don't know what to do or how to reset the board. the output is this from make flash

python3 ../util/caravel_hkflash.py gpio_test.hex

Success: Found one matching FTDI device at <ftdi://ftdi:232>h:1:9/1

Caravel data:

mfg        = 0000

product    = 00

project ID = 00000000

make: *** [Makefile:44: flash] Error 2

@proppy I've seen this with a hand installed assembler. I just did pip3 install mpy-cross and that worked for me

For me seems that the board can not be flash, after that first flash.

@Matt Venn I think mpy-cross is different, it's for compiling the mpy files. For gpio_test we need a bare metal risc-v compiler.