summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md40
1 files changed, 10 insertions, 30 deletions
diff --git a/README.md b/README.md
index baf1bd0..e7437ad 100644
--- a/README.md
+++ b/README.md
@@ -4,8 +4,6 @@ This repository, maintained by SiFive, Inc, makes it easy to get started develop
### Contents ###
-* RISC-V Software Toolchain
-* RISC-V Debugging Toolchain
* Board Support Packages for FE310 and Development Kits
* A Few Example Programs
@@ -24,33 +22,15 @@ cd freedom-e-sdk
make help
```
-#### Building Tools from Source ####
+#### Install the RISC-V Toolchain ####
-Ubuntu packages needed:
+The RISC-V GNU Toolchain and OpenOCD are available from the SiFive Website at
- $ sudo apt-get install autoconf automake libmpc-dev libmpfr-dev libgmp-dev gawk bison flex texinfo libtool libusb-1.0-0-dev make g++ pkg-config libexpat1-dev zlib1g-dev
+https://www.sifive.com/boards
-Next, build the tools:
-
-```
-cd freedom-e-sdk
-make tools [BOARD=freedom-e300-hifive1]
-```
-
-If your machine has enough resources, you can speed up the build process by adding `-j n` to `make`, where `n` is the number of processors of your build system.
-
-
-#### Using Pre-Built Binary Tools ####
-
-If you would like to avoid compiling the tools from source, they are
-available as pre-built binaries from
-
-https://www.sifive.com/products/tools
-
-For OpenOCD and/or RISC-V GNU Toolchain,
-download the .tar.gz for your platform, and unpack it to
-your desired location. Then, use the `RISCV_PATH` and `RISCV_OPENOCD_PATH`
-variables when attempting to use the tools:
+For OpenOCD and/or RISC-V GNU Toolchain, download the .tar.gz for your platform,
+and unpack it to your desired location. Then, use the `RISCV_PATH` and
+`RISCV_OPENOCD_PATH` variables when attempting to use the tools:
```
cp openocd-<date>-<platform>.tar.gz /my/desired/location/
@@ -96,17 +76,17 @@ Run `make help` for more commands.
After setting up the software and debug toolchains, you can build and
execute everyone's favorite benchmark as follows:
-- Compile the benchmark with the command `make software PROGRAM=dhrystone`.
-- Run on the HiFive1 board with the command `make upload PROGRAM=dhrystone`.
+- Compile the benchmark with the command `make software BOARD=freedom-e300-hifive1 PROGRAM=dhrystone LINK_TARGET=dhrystone`. Note that a slightly different linker file is used for Dhrystone which stores read only data in DTIM instead of external flash.
+- Run on the HiFive1 board with the command `make upload BOARD=freedom-e300-hifive1 PROGRAM=dhrystone`.
This will take a few minutes. Sample output is provided below.
- Compute DMIPS by dividing the Dhrystones per Second result by 1757, which
was the VAX 11/780's performance. In the example below, 729927 / 1757 =
415 DMIPS.
- Compute DMIPS/MHz by dividing by the clock rate: in the example below,
- 415 / 260 = 1.60 DMIPS/MHz.
+ 415 / 268 = 1.55 DMIPS/MHz.
```
-core freq at 259830579 Hz
+core freq at 268694323 Hz
Dhrystone Benchmark, Version 2.1 (Language: C)