update build.sh to use rpi-4 directly; fix README
This commit is contained in:
parent
3807e2e149
commit
aed2a619f1
|
@ -64,18 +64,12 @@ openocd -f zc706.cfg -c "pld load 0 blinker_migen.bit; exit"
|
|||
|
||||
Clone this repo onto your development/build machine and the raspberry pi that controls the Xilinx 7000 board
|
||||
|
||||
On the dev machine, the below script builds zc706 and secure copies it to the nixbuild.m-labs.hk server:
|
||||
On the dev machine, the below script builds zc706 and secure copies it to the target pi (in your pi $HOME directory):
|
||||
```shell
|
||||
cd ~/zynq-rs
|
||||
./build.sh $your_user_or_ssh_id
|
||||
```
|
||||
|
||||
Alternatively, you may copy the zc706 build to the target pi (in your pi $HOME directory, for example) using:
|
||||
```shell
|
||||
cd ~/zynq-rs
|
||||
scp -C target/armv7-none-eabihf/release/experiments your_user_or_ssh_id@pi_hostname:/home/your_user_or_ssh_id/zynq-rs/zc706.elf
|
||||
```
|
||||
|
||||
On the pi, we need an information rich environment that includes a relatively reliable `gdb` experience (that includes `ctrl-p` and `ctrl-n` command history that persists across `cgdb` executions), run:
|
||||
```shell
|
||||
ssh pi4
|
||||
|
|
2
build.sh
2
build.sh
|
@ -1 +1 @@
|
|||
nix-shell --command "cargo xbuild --release -p experiments" && scp -P 2204 -C target/armv7-none-eabihf/release/experiments $1@nixbld.m-labs.hk:/home/$1/zc706/zc706.elf
|
||||
nix-shell --command "cargo xbuild --release -p experiments" && scp -C target/armv7-none-eabihf/release/experiments $1@rpi-4.m-labs.hk:/home/$1/zc706/zc706.elf
|
||||
|
|
Loading…
Reference in New Issue