1. add INCLUDE_xTaskGetCurrentTaskHandle for stream_buffer use 2. LDFLAGS add arch and abi info for linker for riscv64-unknown-elf multilib, if there is no arch and abi info, will link to default lib and have below error target emulation `elf32-littleriscv' does not match `elf64-littleriscv' 3. use CFLAGS to replace ASFLAGS when compile assembly code because DEBUG flag is added in CFLAGS, if we use ASFLAGS to compile assembly code, there is no debug info in assembly code objfile Signed-off-by: Eric Chan <e14002270@gmail.com> |
||
---|---|---|
.. | ||
fake_rom.lds | ||
FreeRTOSConfig.h | ||
main.c | ||
main_blinky.c | ||
Makefile | ||
ns16550.c | ||
ns16550.h | ||
Readme.md | ||
riscv-reg.h | ||
riscv-virt.c | ||
riscv-virt.h | ||
start.S |
There is an updated version of this original submission from Katsuhiro Suzuki in the FreeRTOS/Demo/RISC-V_RV32_QEMU_VIRT_GCC directory.
Emulating generic RISC-V 32bit machine on QEMU
Requirements
- GNU RISC-V toolchains (tested on Crosstool-NG)
- qemu-riscv32-system (tested on Debian 10 package)
- Linux OS (tested on Debian 10)
How to build toolchain
Clone the Crosstool-NG and build.
$ git clone https://github.com/crosstool-ng/crosstool-ng
$ ./configure --enable-local
$ make
$ ./ct-ng menuconfig
Change the following configs:
CT_EXPERIMENTAL=y
CT_ARCH_RISCV=y
CT_ARCH_64=y
CT_ARCH_ARCH=rv32ima
CT_ARCH_ABI=ilp32
CT_MULTILIB=y
CT_DEBUG_GDB=y
Build the GNU toolchain for RISC-V.
$ ./ct-ng build
A toolchain is installed at ~/x-tools/riscv64-unknown-elf directory.
How to build
Add path of toolchain that is described above section.
$ export PATH=~/x-tools/riscv64-unknown-elf:$PATH
For release build:
$ make
For debug build:
$ make DEBUG=1
If success to build, executable file RTOSDemo.axf in ./build directory.
How to run
$ qemu-system-riscv32 -nographic -machine virt -net none \
-chardev stdio,id=con,mux=on -serial chardev:con \
-mon chardev=con,mode=readline -bios none \
-smp 4 -kernel ./build/RTOSDemo.axf
How to debug with gdb
Append -s and -S options to the previous qemu command.
- -s: enable to attach gdb to QEMU at port 1234
- -S: start and halted CPU (wait for attach from gdb)
This is just recommend to use 'debug build' for more efficient debugging. Run these commands after starting the QEMU with above options:
$ riscv64-unknown-elf-gdb build/RTOSDemo.axf
(gdb) target remote localhost:1234
(gdb) break main
Breakpoint 1 at 0x80000110
(gdb) c
Continuing.
Breakpoint 1, 0x80000110 in main ()
Description
This demo just prints Tx/Rx message of queue to serial port, use no other hardware and use only primary core (currently hart 0). Other cores are simply going to wfi state and execute nothing else.