[libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page

bugzilla-daemon at libre-riscv.org bugzilla-daemon at libre-riscv.org
Fri Mar 6 16:51:44 GMT 2020


--- Comment #181 from Jock Tanner <tanner.of.kha at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #173)

> … i gave serious consideration to scripting a from-scratch
> source-build of python 3 (which is what you need to do if installing pypy3,
> which we did a few months ago).

Did you use pyenv back then? If not, I would highly recommend it.

(In reply to Luke Kenneth Casson Leighton from comment #180)
> ok jock i replicated things, all good.  yes you're right, do that symlink
> for now.  i've updated the page
> https://libre-riscv.org/HDL_workflow/coriolis2/
> can you double-check it looks reasonable.

There was also a minor quirk I did not mention.

When you do (1.3)

> git clone https://www-soc.lip6.fr/git/alliance.git

sources appears in '~/alliance/alliance/alliance/src', not in
'~/alliance/alliance/src'. The rest of the paths are correct.

> the next thing to do would be to make sure nmigen is installed correctly as
> well as yosys from latest source code, and try some of the soclayout
> experiments.
> some of them aren't fully documented, you can see in this bugreport i say
> things like "run make vst then python doAlu16.py" rather than just "make
> lvx", however just go through them and see how you get on ok?

TBH I could not grasp that instructions at all. =)

I created my `user-LOGIN.mk` and run `make` in a different folders. I came to
realization that my Arch-hosted chroot is broken: every attempt at `make` has
ended up in `dreal` segfaulted. But in Debian 10-hosted chroot I managed to get
either an empty `dreal` window or an error message other than segfault.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-riscv-dev mailing list