Skip to content

Commit 427d2a2

Browse files
authored
Refreshed u585 board stes and removed nucelo board. (#9)
1 parent ead5f6b commit 427d2a2

4 files changed

Lines changed: 8 additions & 110 deletions

File tree

docs/board-support/ST/B-U585I-IOT02A/index.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -33,22 +33,17 @@ In the diagram below, you can see many of the board's physical components:
3333

3434
## Connecting to the Device
3535

36-
### Physical Connection
37-
The board has two micro-USB ports. Connect a micro-USB cable to the port labeled **STLINK-V3E USB port (CN8)** in the top right corner of the board. Once connected, power and debug LEDs should illuminate, indicating the board is ready for use.
38-
39-
### Serial Connection
4036
To monitor your device's output:
41-
1. Open your preferred serial terminal application
42-
2. Configure the following settings:
37+
1. Connect your board to your computer with a USB cable using the STLINK port (**CN8**) on your board.
38+
2. Open your preferred console application.
39+
3. Configure the following settings:
4340
* **Port**: Select the port where your device is connected
4441
* **Baud Rate**: 115200
4542
* **Data Bits**: 8
4643
* **Parity**: None
4744
* **Flow Control**: None
4845
* **Line Endings**: None
49-
50-
{: .note}
51-
The device will appear as a USB serial port when properly connected. On Linux/macOS it will typically be `/dev/ttyACM0` or similar, on Windows it will be a COM port.
46+
4. Start the new connection.
5247

5348
---
5449

-1.56 MB
Binary file not shown.

docs/board-support/ST/NUCLEO-H723ZG/index.md

Lines changed: 0 additions & 95 deletions
This file was deleted.

docs/quickstart/firmware/hardware.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ nav_order: 2
1010
This guide covers building and flashing the Ocre runtime onto actual development boards. While simulated environments are great for initial testing, deploying to real hardware allows you to test your applications under authentic conditions and take advantage of board-specific features like sensors and networking capabilities.
1111

1212
{: .note}
13-
Please refer to the "Building and Flashing the Ocre Runtime" section for your board in our in our [Board Support](../../../board-support) section for your boards name, as well as any additional setup instructions should you need them.
13+
Please refer to the **Building and Flashing the Ocre Runtime** section for your board in our in our [Board Support](../../../board-support) section for your boards name, as well as any additional setup instructions should you need them.
1414

1515
---
1616

@@ -81,14 +81,12 @@ You can also run the **West Build** task directly from the **Ocre Workspace** fi
8181

8282
To flash the Ocre Runtime to your device follow these steps:
8383

84-
1. Connect your board to your computer.
85-
2. Open your [serial console](../../quickstart/prerequisites/serial-console/index.md), and connect to your board.
86-
1. Flash the application to your device:
84+
1. Connect your board to your computer and ensure it's recognized by your serial console. (See the **Connecting to the Device** section in the [board support](../../../board-support) guide for your specific board for more details.)
85+
2. From your terminal, flash the application to your device:
8786
```
8887
west flash
8988
```
90-
91-
After flashing, restart/reset your board to run the application. If successful, you should see the following output on your console:
89+
3. After flashing, restart/reset your board to run the application. If successful, you should see the following output on your console:
9290

9391
![](../success.png)
9492

0 commit comments

Comments
 (0)