venv for Python setup (#653)
* Python uses venv * Small fixes to python calls
This commit is contained in:
@@ -19,7 +19,7 @@ After general setup, you still need these steps:
|
||||
1. Run the script:
|
||||
|
||||
```shell
|
||||
python3 uf2conv.py -c -f 0xada52840 -o target/opensk.uf2 target/nrf52840_mdk_dfu_merged.hex
|
||||
py_virtual_env/bin/python3 uf2conv.py -c -f 0xada52840 -o target/opensk.uf2 target/nrf52840_mdk_dfu_merged.hex
|
||||
```
|
||||
|
||||
1. Boot into DFU mode. Keep the user button pressed on your hardware while
|
||||
|
||||
@@ -64,10 +64,10 @@ Afterwards, you can upgrade the other partition with
|
||||
```shell
|
||||
# Board A -> B
|
||||
./deploy.py --board=nrf52840dk_opensk_b --opensk --programmer=none --version=1
|
||||
python3 -m tools.deploy_partition --board=nrf52840dk_opensk_b --version=1
|
||||
py_virtual_env/bin/python3 -m tools.deploy_partition --board=nrf52840dk_opensk_b --version=1
|
||||
# Board B -> A
|
||||
./deploy.py --board=nrf52840dk_opensk_a --opensk --programmer=none --version=1
|
||||
python3 -m tools.deploy_partition --board=nrf52840dk_opensk_a --version=1
|
||||
py_virtual_env/bin/python3 -m tools.deploy_partition --board=nrf52840dk_opensk_a --version=1
|
||||
```
|
||||
|
||||
respectively. You can only upgrade the partition that is not currently running,
|
||||
@@ -81,5 +81,5 @@ for example:
|
||||
```shell
|
||||
./deploy.py --board=nrf52840dk_opensk_a --opensk --version=0 --vendor-hid
|
||||
./deploy.py --board=nrf52840dk_opensk_b --opensk --programmer=none --version=1 --vendor-hid
|
||||
python3 -m tools.deploy_partition --board=nrf52840dk_opensk_b --version=1 --vendor-hid
|
||||
py_virtual_env/bin/python3 -m tools.deploy_partition --board=nrf52840dk_opensk_b --version=1 --vendor-hid
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user