Spike version won't let me log into the console
Opened this issue · 1 comments
The qemu portion is under construction waiting for an update to the latest version of the specification. I tried the spike instructions and it boots, but then it sits there consuming CPU and there's no way to log into the console and there's no networking support (that I know of) in spike so that I can ssh.
Starting syslogd/klogd: done
INIT: no more processes left in this runlevel
[ 41.310000] random: nonblocking pool is initialized
Is there a way to get spike up and running similar to the instructions for the riscv-tools?
As a work around, I mounted the root filesystem on my local linux machine and edited /etc/inittab to change the default run level to 1:
id:1:initdefault:
Then, I changed the run level one command to simply run /bin/sh:
l1:1:wait:/bin/sh
I now have a shell that I can use from spike.