From 801f11bfc314b83890f4e4c1fdefe0d74c3cd017 Mon Sep 17 00:00:00 2001
From: Samuel Tardieu <sam@rfc1149.net>
Date: Tue, 30 Jul 2024 13:35:01 +0200
Subject: [PATCH] Update instructions

---
 INSTALL.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/INSTALL.md b/INSTALL.md
index bc8f219..0afc3e1 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -23,7 +23,8 @@ $ cargo install probe-rs-tools
 You must flash the I²C bootloader using a JTAG probe:
 
 ```shell
-$ cargo run --profile production -p bootloader
+$ cd bootloader
+$ cargo run --profile production
 ```
 
 The bootloader is in charge of launching the existing controller, or
@@ -35,7 +36,8 @@ JTAG probe.
 You canflash the controller directly using a JTAG probe:
 
 ```shell
-$ cargo run --profile production -p controller
+$ cd controller
+$ cargo run --profile production
 ```
 
 ## Raspberry Pi
@@ -60,7 +62,8 @@ The Python module is located in `controller/python/controller.py`.
 The `firmware-updater` program can be either be built on the Raspberry Pi:
 
 ```shell
-$ cargo build --profile production -p firmware-updater
+$ cd firmware-updater
+$ cargo build --profile production
 ```
 
 or can be cross-compiled from another machine, provided you have
@@ -68,7 +71,8 @@ already installed `aarch-unknown-linux-musl-gcc` which is needed for
 linking:
 
 ```shell
-$ cargo build --profile production -p firmware-updater --target aarch-unknown-linux-musl
+$ cd firmware-updater
+$ cargo build --profile production --target aarch-unknown-linux-musl
 ```
 
 ### Updating the firmware
-- 
GitLab