From: Andrey Miroshnikov Date: Sat, 2 Oct 2021 18:48:42 +0000 (+0100) Subject: Updated coriolis2 wiki to include automated process, still needs a bit more detail... X-Git-Tag: opf_rfc_ls005_v1~3772 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=ea9570830e237c052698745c54b152ef4ad4d591;p=libreriscv.git Updated coriolis2 wiki to include automated process, still needs a bit more detail/cleanup. Added example adder floorplan image. --- diff --git a/HDL_workflow/chip_r_floorplan.png b/HDL_workflow/chip_r_floorplan.png new file mode 100644 index 000000000..cc0c30d39 Binary files /dev/null and b/HDL_workflow/chip_r_floorplan.png differ diff --git a/HDL_workflow/coriolis2.mdwn b/HDL_workflow/coriolis2.mdwn index e7f96b4ee..41c9317a2 100644 --- a/HDL_workflow/coriolis2.mdwn +++ b/HDL_workflow/coriolis2.mdwn @@ -2,6 +2,36 @@ TODO: include tasyagle +## NEW IN PROGRESS - Automated Installation +The new automated method of installing/setting coriolis2 is as follows: +1. Clone the repo "dev-env-setup". Tutorial assumes the directory is located under your user's home. +2. Run the script "mk-deb-chroot" to create a chroot environment. Tutorial assumes the name is "libresoc" +3. Run the script "cp-scripts-to-chroot" to copy the dev-env-setup directory over to your new chroot environment. +4. Login into the new scroot environment as a normal user (should be the same as your current user). +5. Run the script "coriolis-install" +6. Once cgt window appears, go to File, Open Cell, and type chip_r. +7. You should now have a working Coriolis environment! + +In a terminal: + $ cd ~/dev-env-setup + $ sudo bash + # ./mk-deb-chroot libresoc + # ./cp-scripts-to-chroot libresoc + +In a separate terminal as normal user: + $ scroot -c libresoc + (libresoc)$ cd ~/dev-env-setup + (libresoc)$ ./coriolis-install + +And now you wait...I suggest occasionally checking the status messages, especially after apt finished updating the packages and the script moves on to compiling yosys, coriolis2, alliance, as well as when alliance-check-toolkit generates the floorplan for you. + +This is what the chip floorplan should look like: + +[[!img chip_r_flooplan.png ]] + +# Sections to be updated... + + ## debootstrap First set up an schroot debootstrap jail with debian 10.