Skip to content

根据Nutshell-doc的步骤来跑Nutshell没有得到预期结果? #4

@MapleLeafFall

Description

@MapleLeafFall

Hi all,
我刚开始了解nutshell芯片项目,在参考Nutshell-doc的步骤来执行命令时,得不到预期的现象。想请教下,可能是什么原因呢?

问题描述:
根据这个页面readme.md已准备环境完成,包括varilator、NEMU/Nutsehll/nexus-am源码等(都是OSCPU一生一芯代码库下的版本)。
然后参考NutShell-tutorial.md内容分别执行两个命令,都没有正常输出:
第一个命令执行报错:

cwq@ubuntu:~/4_nutshell/nexus-am/apps/microbench$ make ARCH=riscv64-nemu mainargs=test run
/home/cwq/4_nutshell/nexus-am/apps/microbench 
/home/cwq/4_nutshell/nexus-am/apps/microbench/build/microbench-riscv64-nemu 
/home/cwq/4_nutshell/nexus-am/Makefile.check:16: *** Invalid ARCH. Supported: riscv64-nutshell。 停止。

第二个命令执行提前退出:

cwq@ubuntu:~/4_nutshell/nexus-am/apps/microbench$ make ARCH=riscv64-nutshell mainargs=test run
/home/cwq/4_nutshell/nexus-am/apps/microbench 
/home/cwq/4_nutshell/nexus-am/apps/microbench/build/microbench-riscv64-nutshell 
# Building microbench [riscv64-nutshell] with AM_HOME {/home/cwq/4_nutshell/nexus-am}
# Building lib-am [riscv64-nutshell]
+ AS src/nutshell/common/mainargs.S
+ AR -> build/am-riscv64-nutshell.a
# Building lib-klib [riscv64-nutshell]
# Creating binary image [riscv64-nutshell]
+ LD -> build/microbench-riscv64-nutshell.elf
+ OBJCOPY -> build/microbench-riscv64-nutshell.bin
make -C /home/cwq/4_nutshell/NutShell emu IMAGE="/home/cwq/4_nutshell/nexus-am/apps/microbench/build/microbench-riscv64-nutshell.bin" DATAWIDTH=64
make[1]: 进入目录“/home/cwq/4_nutshell/NutShell”
make -C ./difftest emu
make[2]: 进入目录“/home/cwq/4_nutshell/NutShell/difftest”
make[2]: 对“emu”无需做任何事。
make[2]: 离开目录“/home/cwq/4_nutshell/NutShell/difftest”
make[1]: 离开目录“/home/cwq/4_nutshell/NutShell”

猜想:

  1. 第一个命令可能是因为AM代码里只支持nutshell平台而不支持NEMU平台导致的?因为nexus-am/am/arch/下只有riscv64-nutshell.mk一个文件,缺失了对应的riscv64-nemu.mk?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions