joonho hwangbo
0bc098496c
Update scripts/build-setup.sh
...
Co-authored-by: Abraham Gonzalez <abe.j.gonza@gmail.com >
2024-01-22 13:25:16 -08:00
joonho.whangbo
b4d56b6a4f
Dedup chipyard conda lock file, add esp-tools to lean conda-lock
2024-01-22 11:17:29 -08:00
joonho.whangbo
16eeeae8fc
Use lean conda for faster initial setup
2024-01-22 01:55:28 -08:00
Jerry Zhao
df2ed07b25
Add parsing for deprecated flags to avoid breaking user flows
2024-01-21 23:29:48 -08:00
joonho.whangbo
b5d7e2f6cb
Remove skip-validate option
2024-01-21 16:28:54 -08:00
Jerry Zhao
bb23af97be
Add clearer --skip flags to build-setup
2024-01-04 21:58:33 -08:00
Jerry Zhao
e8f89d228c
Move CIRCT install to its own step in build-setup script
2023-12-18 14:22:01 -08:00
abejgonzalez
551c096bc9
Fix CIRCT installer path | Run CRON every 15m
2023-12-07 11:00:59 -08:00
abejgonzalez
dd6cff58a6
Fix CI (proper use of CONDA_PREFIX + GH token)
2023-12-01 10:11:13 -08:00
abejgonzalez
dae66b0d56
Bump
2023-11-30 17:30:36 -08:00
abejgonzalez
d2b3181e48
Update CI to install circt | Update every day
2023-11-30 16:09:42 -08:00
abejgonzalez
b9e504411a
Install CIRCT outside of conda (add CI to auto-update)
2023-11-30 15:47:14 -08:00
abejgonzalez
eca7b960f6
More robust env.sh | Fix conda activate if in subshell
2023-11-06 17:22:05 -08:00
JL102
a7993db08e
I think now I put &&s everywhere that is necessary
2023-10-06 19:00:11 -04:00
JL102
aded25fee0
Made indentation consistent
2023-10-06 18:49:10 -04:00
JL102
b76ab6b5b0
Replaced "try-catch" with a more special-purpose set of functions
...
This also fixed the weird issue I was experiencing where the try-catch in step 1 caused step 3 to break
2023-10-06 18:43:52 -04:00
JL102
6b70dd6d39
Added "try-catch" to all build-setup steps
...
This was the only way I knew how to display the step at which the build-setup process failed.
I've personally experienced failures at multiple of the build steps, and before I got used to Chipyard,
it was hard to figure out which step was the culprit. With this, users should have a bit more info to
troubleshoot their issues. For some of the build steps that required multiple lines, I figured it made
more sense to put them into a sub-script, rather than putting a && at the end of each line. But for the
firesim one for example, since it was two .sh calls, I just put a && after the first one, inside of the
try block, to make sure both lines run.
2023-10-05 02:17:25 -04:00
Abraham Gonzalez
4cfc16674c
Remove pre-commit from env.sh
2023-08-30 11:39:13 -07:00
abejgonzalez
c7f1fe220d
Enable precommit | Format files
2023-08-28 14:56:55 -07:00
abejgonzalez
0674488f9f
Bump lockfiles | Force user-installed conda during conda-lock [ci skip]
2023-07-12 00:21:26 +00:00
Sagar Karandikar
4f282afdc5
Update build-setup.sh
2023-06-16 09:41:53 -07:00
abejgonzalez
1f687af997
Generate all lockfiles at once
2023-05-09 14:12:09 -07:00
abejgonzalez
dbbf7c90b4
Separate out conda-lock generation into new script
2023-05-09 13:58:40 -07:00
Jerry Zhao
f01101da4b
Remove init-fpga scripts and references, init-submodules now also inits-fpga
2023-05-07 16:03:27 -07:00
abejgonzalez
482f91d0e5
Clear screen on prompt [ci skip]
2023-04-20 14:50:32 -07:00
Jerry Zhao
63a7d13ec7
Fix newline in message in build-setup.sh
2023-02-23 10:12:03 -08:00
Jerry Zhao
13f87e9ff6
Recommend riscv-tools for gemmini users in build-setup script
2023-02-05 09:11:56 -08:00
Jerry Zhao
7780ed23bf
Bump to scala 2.13.10/chisel 3.5.5/latest rocketchip
2023-01-26 00:12:28 -08:00
abejgonzalez
b6d6ea6db1
Init FPGA submodules in build-setup.sh
2022-12-20 11:02:07 -08:00
abejgonzalez
1b12c6adf6
Rename to run_step | Add comments
2022-12-12 14:42:29 -08:00
abejgonzalez
a0ad9d2055
Remove need for conda in build-toolchains-extra.sh
2022-12-12 10:56:54 -08:00
abejgonzalez
5996ec69a5
Rework build-setup | Add single-node CI
2022-12-09 17:33:41 -08:00
Jerry Zhao
927bd6fc80
Move build-setup script to correct directory ( #1271 )
2022-12-08 09:51:30 -08:00
