I'm trying to boot lowRISC Ethernet-v0.5 on a Nexys4 DDR board but got
stuck in the boot process.
I want to boot OS from a SD card and downloaded the pre-built SD-image
provided by the tutorial. The SD card is partioned according to the
tutorial. I put 'boot0000.bin' in the 32M 'W95 FAT32' partion. Then the
boot process got stuck and I got the following output from
microcomthrough UART connection (full output log is attached to this mail):
Setting the clock ...
[ 10.810000] mmc0: new SDHC card at address b368
[ 10.830000] blk_queue_max_hw_sectors: set to minimum 8
[ 10.850000] mmcblk0: mmc0:b368 CBADS 30.0 GiB
[ 10.910000] mmcblk0: p1 p2 p3
rdate: timeout connecting to time server
Waiting for the sd card ...
Mounting the sd partition ...
Switch to sd root
[ 35.390000] random: nonblocking pool is initialized
INIT: version 2.88 booting
After the 'INIT: version 2.88 booting' I got no more output, so I cannot
figure out what is going on and where I made a mistake. Could you please
help me to find out the reason why the boot process was stuck?
ps: I didn't connect the board and my host PC with ethernet cable, could
this be the reason?
Thanks & Regards,
Unfortunately there was nobody in the corresponding IRC channel so I think it might be worth to ask it here.
I would like to get an overview about the lowRISC project. I would love to participate in one way or another in order to make the hardware availabe to the public one day.
Can somebody provide me a crash-course how things are working and which further steps are needed to be done?
(My apologies if I post repeated information, I didn't have much time
available lately to follow all the mailing lists that I am subscribed
We've been working in the last few weeks to do a (second) boostrap of
Debian for RISC-V, and after a few weeks of hard work it is now
bootstrapped and has been imported into the Debian infrastructure, in
particular, debian-ports (* description below).
All packages that are uploaded to the archive by any of the
hundreds/thousands of contributors are attempted to be built for each
one of the architectures/ABIs almost immediately, so having "riscv64"
as a Debian architecture is a quite critical step.
This means that, from now on, anybody can download .deb packages
targetted for riscv64 (rv64gc, to be precise) which compile
successfuly, often only a few hours after being uploaded to the
archive (as long as their build-dependencies are satisfied). You can
download them from here:
(We will attempt to provide more ready-to-use system images in the future).
One can follow the progress of this architecture (>4k packages, or
~30% of the arch-dependent packages, built successfully by now) from:
And from here one can see the detailed output of all the compilations
of gcc-8 or nethack (only 1 version of each so far), to compare with
previous builds or versions, or with other distributions:
clicking on the link of the "result" column:
clicking on the link of the "result" column:
So we hope that this is a valuable resource, and that it helps to
continue the development of RISC-V hardware, and that you can run it
on your devices in the near future ;-)
More background info about the process, if interested:
(*) In Debian, "ports" are different ABI targets (sometimes they
evolve slightly over the years, like "i386", upgrading the baseline
ISA). Those which are well established and have good support of
hardware, several developers behind and can keep up with building the
archive successfully, are designed as the main ones (amd64/x86_64,
arm64/-hf/-el, ppc64el, s390x, several mips*).
Those which are still "in the nursery" or do not have good support for
being old or similar reasons (sparc64, m68k, alpha) are in what's
known as "debian-ports", which means architectures/ABIs which are not
supported for the full lifetime of stable realeases, they cannot
compile 90% of the archive, etc. They can lag behind in building
packages, without delaying or harming the main supported architectures
-- that's the main reason to have this separation.
Manuel A. Fernandez Montecelo <manuel.montezelo(a)gmail.com>
Hi, I was going to try v0.5 on my Nexys 4 DDR. However I believe
that this version doesn't support the Compressed extension. I
disassembled the sample bbl and there are no short instructions.
Is support for the C extension available and/or planned?
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
Hi, LowRISC team:
When I do FPGA_FULL mode simulation of your Untethered lowRISC version 0.2 got from Git, I meet a strange simulation scenario showed below.
I found the "mem_nasti.r_ready[0:0]" always be 0, but driver of this wire is 1. The driver is "io_nasti_r_ready" of Rocket. So the Hellworld test will be failed.
But if I use FPGA mode to do the simulation for same Helloworld test, it is successful finished. I have checked the difference of this two simulation modes,
the difference are forcus on DRAM(xilinx mig) ,clock and reset generation which is not the interface the Helloworld test need to access.
I am not sure it is VCS simulator's problem, or I missed something?
Waiting your feedback. Thank you!
On Mon, Apr 2, 2018 at 3:44 AM, Manuel A. Fernandez Montecelo
> We've been working in the last few weeks to do a (second) boostrap of
> Debian for RISC-V, and after a few weeks of hard work it is now
> bootstrapped and has been imported into the Debian infrastructure, in
> particular, debian-ports (* description below).
this is fantastic, manuel - i've been watching the debian patches
being submitted and it's great to see the results of them being
accepted. congratulations to everyone involved, this is a huge step