switching commits and instructions
diff --git a/openlane/Makefile b/openlane/Makefile
index e63579d..8d2e712 100644
--- a/openlane/Makefile
+++ b/openlane/Makefile
@@ -2,7 +2,7 @@
CONFIG = $(foreach block,$(BLOCKS), ./$(block)/config.tcl)
CLEAN = $(foreach block,$(BLOCKS), clean-$(block))
-OPENLANE_TAG ?= rc4
+OPENLANE_TAG ?= rc5
OPENLANE_IMAGE_NAME ?= openlane:$(OPENLANE_TAG)
OPENLANE_BASIC_COMMAND = "cd /project/openlane && flow.tcl -design ./$* -save_path .. -save -tag $* -overwrite"
OPENLANE_INTERACTIVE_COMMAND = "cd /project/openlane && flow.tcl -it -file ./$*/interactive.tcl"
@@ -47,7 +47,7 @@
@echo "Please export OPENLANE_ROOT"
@exit 1
endif
- git clone https://github.com/efabless/openlane.git $(OPENLANE_ROOT) && \
+ git clone https://github.com/efabless/openlane.git --branch=develop $(OPENLANE_ROOT) && \
cd $(OPENLANE_ROOT) && \
make openlane
diff --git a/openlane/README.md b/openlane/README.md
index 7cba65f..e938610 100644
--- a/openlane/README.md
+++ b/openlane/README.md
@@ -4,14 +4,13 @@
But, first you need to specify 3 things:
```bash
-export OPENLANE_TAG=<the openlane tag/version you are using. This could be rc4 or rc5 based on when you cloned openlane and what branch you are using.>
export PDK_ROOT=<The location where the pdk is installed>
-export OPENLANE_ROOT=<the absolute path to the cloned openlane directory>
+export OPENLANE_ROOT=<the absolute path to the openlane directory cloned or to be cloned>
```
-**NOTE:** we recommend using openlane:rc4. Note the following [FAQ](https://github.com/efabless/openlane/wiki#why-am-i-getting-n-well-related-drc-violations-from-magic-when-using-the-latest-version-of-the-skywater-pdk).
+**NOTE:** rc5 and caravel are still WIP so expect to run into some issues when using it.
-If you don't have openlane already, then you can get it from [here](https://github.com/efabless/openlane). Alternatively, you can clone and build the openlane master through:
+If you don't have openlane already, then you can get it from [here](https://github.com/efabless/openlane). Alternatively, you can clone and build the openlane develop branch through:
```bash
make openlane
```
@@ -99,4 +98,4 @@
- [Here](https://github.com/efabless/openlane/blob/master/doc/advanced_readme.md) you can learn how to write an interactive script.
- [Here](https://github.com/efabless/openlane/blob/master/doc/OpenLANE_commands.md) you can find a full documentation for all OpenLANE commands.
- [This documentation](https://github.com/efabless/openlane/blob/master/regression_results/README.md) describes how to use the exploration script to achieve an LVS/DRC clean design.
-- [This documentation](https://github.com/efabless/openlane/blob/develop/doc/hardening_macros.md) walks you through hardening a macro and all the decisions you should make. However, this is still on the develop branch of openlane and so may contain configuration references that are yet to come to master. For example, `FP_CONTEXT_DEF` and `FP_CONTEXT_DEF`.
+- [This documentation](https://github.com/efabless/openlane/blob/develop/doc/hardening_macros.md) walks you through hardening a macro and all the decisions you should make.
