Not able to run riscv-rv32imac testsuites

Hesham Almatary hesham.almatary at cl.cam.ac.uk
Tue Aug 6 15:19:26 UTC 2019


Hi Vaibhav,

* I recommend you use rv64* because of a potential 32-bit HTIF issue on Spike.
* Make sure you install Spike correctly [1] and it's in your path or
also qemu-system-riscv* instead.
* If you're building RTEMS for Spike (i.e., rv*_spike), make sure to
add RISCV_ENABLE_HTIF_SUPPORT to your configure line [2] when you
build RTEMS.
* It might be easier to try rv64* on QEMU (i.e., no Spike) instead.

[1] https://github.com/riscv/riscv-isa-sim
[2] https://docs.rtems.org/branches/master/user/bsps/bsps-riscv.html

On Tue, 6 Aug 2019 at 14:52, Vaibhav Gupta <vaibhavgupta40 at gmail.com> wrote:
>
> I am getting following error:
> .
> .
> $ rtems-test --rtems-bsp=rv32imac_spike --rtems-tools=$HOME/development/rtems/5 ~/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
>
> RTEMS Testing - Tester, 5.0.not_released
>  Command Line: /home/varodek/development/rtems/5/bin/rtems-test --rtems-bsp=rv32imac_spike --rtems-tools=/home/varodek/development/rtems/5 /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
>  Host: Linux varodek 5.0.9-arch1-1-ARCH #1 SMP PREEMPT Sat Apr 20 15:00:46 UTC 2019 x86_64
>  Python: 3.7.3 (default, Mar 26 2019, 21:43:19) [GCC 8.2.1 20181127]
> Host: Linux-5.0.9-arch1-1-ARCH-x86_64-with-arch (Linux varodek 5.0.9-arch1-1-ARCH #1 SMP PREEMPT Sat Apr 20 15:00:46 UTC 2019 x86_64 )
> [ 2/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: capture.exe
> [ 3/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: cdtest.exe
> [ 4/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: cxx_iostream.exe
> [ 1/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: base_sp.exe
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/capture.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/capture.exe: exit-code:2
> warning: switched to dry run due to errors
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/cxx_iostream.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/cxx_iostream.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/cdtest.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/cdtest.exe: exit-code:2
> warning: switched to dry run due to errors
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/base_sp.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/base_sp.exe: exit-code:2
> warning: switched to dry run due to errors
> warning: switched to dry run due to errors
> [ 1/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: base_sp.exe
> Result: invalid    Time: 0:00:00.032377 base_sp.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/base_sp.exe
> [ 2/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: capture.exe
> Result: invalid    Time: 0:00:00.037950 capture.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/capture.exe
> [ 3/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: cdtest.exe
> Result: invalid    Time: 0:00:00.038061 cdtest.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/cdtest.exe
> [ 4/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | riscv32/rv32imac: cxx_iostream.exe
> Result: invalid    Time: 0:00:00.034353 cxx_iostream.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/cxx_iostream.exe
> [ 7/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: minimum.exe
> [ 8/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: nsecs.exe
> [ 5/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: fileio.exe
> [ 6/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: hello.exe
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/minimum.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/minimum.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/nsecs.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/fileio.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/nsecs.exe: exit-code:2
> warning: switched to dry run due to errors
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/fileio.exe: exit-code:2
> warning: switched to dry run due to errors
> warning: switched to dry run due to errors
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/hello.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/hello.exe: exit-code:2
> warning: switched to dry run due to errors
> [ 5/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: fileio.exe
> Result: invalid    Time: 0:00:00.009235 fileio.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/fileio.exe
> [ 6/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: hello.exe
> Result: invalid    Time: 0:00:00.005886 hello.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/hello.exe
> [ 7/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: minimum.exe
> [ 8/11] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:4  W:0  | riscv32/rv32imac: nsecs.exe
> Result: invalid    Time: 0:00:00.011045 nsecs.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/nsecs.exe
> [ 9/11] p:1  f:0  u:0  e:0  I:0  B:0  t:0  i:7  W:0  | riscv32/rv32imac: paranoia.exe
> [10/11] p:1  f:0  u:0  e:0  I:0  B:0  t:0  i:7  W:0  | riscv32/rv32imac: ticker.exe
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/paranoia.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/paranoia.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/ticker.exe: exit-code:2
> warning: switched to dry run due to errors
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/ticker.exe: exit-code:2
> [11/11] p:1  f:0  u:0  e:0  I:0  B:0  t:0  i:8  W:0  | riscv32/rv32imac: unlimited.exe
> warning: switched to dry run due to errors
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/unlimited.exe: exit-code:2
> error: spike.cfg:58: execute failed: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/unlimited.exe: exit-code:2
> warning: switched to dry run due to errors
> [ 9/11] p:1  f:0  u:0  e:0  I:0  B:0  t:0  i:7  W:0  | riscv32/rv32imac: paranoia.exe
> Result: invalid    Time: 0:00:00.011650 paranoia.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/paranoia.exe
> [10/11] p:1  f:0  u:0  e:0  I:0  B:0  t:0  i:7  W:0  | riscv32/rv32imac: ticker.exe
> Result: invalid    Time: 0:00:00.009872 ticker.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/ticker.exe
> [11/11] p:1  f:0  u:0  e:0  I:0  B:0  t:0  i:8  W:0  | riscv32/rv32imac: unlimited.exe
> Result: invalid    Time: 0:00:00.002352 unlimited.exe
> =>  run: spike --isa=RV32IMAC /home/varodek/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples/unlimited.exe
>
> Passed:         1
> Failed:         0
> User Input:     0
> Expected Fail:  0
> Indeterminate:  0
> Benchmark:      0
> Timeout:        0
> Invalid:       10
> Wrong Version:  0
> Wrong Build:    0
> Wrong Tools:    0
> -----------------
> Total:         11
> Invalid:
>  capture.exe
>  cdtest.exe
>  cxx_iostream.exe
>  base_sp.exe
>  nsecs.exe
>  fileio.exe
>  hello.exe
>  paranoia.exe
>  ticker.exe
>  unlimited.exe
> Average test time: 0:00:00.093749
> Testing time     : 0:00:01.031239
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel


More information about the devel mailing list