English is currently available.
RISC-V Microcontrollers DISCUSSION
A firmware image for a RISC-V MCU links successfully but reaches an exception after entering library code. How should the selected instruction set, calling convention and library build be checked before blaming the compiler?
Reference: GCC: RISC-V target options (https://gcc.gnu.org/onlinedocs/gcc/RISC-V-Options.html).
Compare the exact core's supported ISA extensions with the compiler's -march setting. An instruction accepted by the assembler is not necessarily implemented by the target. Record the trap cause and failing instruction address, then disassemble that location using the same build's ELF file.
Check -mabi separately because it controls the calling convention, including how floating-point arguments are passed. Objects and libraries must use compatible conventions. A hard-float library and a soft-float application are not made compatible merely by enabling floating-point instructions in one source file.
Build a minimal call that reproduces the fault and inspect startup code, stack alignment and library selection. Keep the toolchain version and complete options with the artifact. Avoid choosing extensions because a different RISC-V board used them successfully.
