Jim Wilson

There is a build log in the riscv-openocd dir you can try looking at. But in general, riscv-tools isn't expected to build anymore because it has been unmaintained for too...

What exact command did you type and what exact error did you get? Note that spike does not search the path for pk, so you must give the full path...

RISC-V objdump will work on any binary that contains RISC-V code. That includes executables, object files, and shared libraries. I generally use objdump -dr for object files and objdump -dR...

If you are using glibc, libc.so is a linker script, a text file, that refers to libc.so.6, which is an actual shared library. So, no, you can't disassemble libc.so as...

Those look like native (x86?) libraries for the simulator, compiler, etc. A RISC-V objdump won't be able to disassemble them because they don't have RISC-V instructions in them. Use the...

The sysroot dir is the target / dir, so yes, those are RISC-V libraries. Gconv is part of glibc. It supports conversion from one character encoding to another. Try "man...

What exactly do you mean by "source instruction"? Gcc -S gives you assembly code, gcc -c gives you an object file. Objdump -dr on an object file gives you assembly...

Disassembler reports whatever is in there. If you don't want F and C in the code, then you have to compile without them, e.g. use -march=-rv32i -mabi=ilp32 when compiling, and...

Stop using -D. This is almost always a mistake. If you see docs that recommend use of -D file a bug report against them. use -d instead. You have 00000000...

Only disassembly of ELF files is expected to work. bin and mem files don't have the info necessary for the disassebler to give correct results.