You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/learning-paths/embedded-and-microcontrollers/avh_balena/2setup.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: "Preparing a custom Balena OS image"
2
+
title: "Prepare a custom Balena OS image"
3
3
weight: 2
4
4
5
5
### FIXED, DO NOT MODIFY
@@ -8,19 +8,19 @@ layout: learningpathall
8
8
9
9
## Sign up for Balena Cloud
10
10
11
-
The free Balena Cloud service manages IoT devices and applications. You can deploy Balena apps without Balena Cloud using the open source [OpenBalena project](https://github.com/balena-io/open-balena), but for simplicity this tutorial uses the hosted service.
11
+
The free Balena Cloud service manages IoT devices and applications. You can deploy Balena apps without Balena Cloud using the open source [OpenBalena project](https://github.com/balena-io/open-balena), but for simplicity this Learning Path uses the hosted service.
12
12
13
-
Navigate to the [Balena Cloud Sign up](https://dashboard.balena-cloud.com/signup) form and create a new account. The free account lets you manage up to 10 devices with no cost. This Learning Path requires only one device.
13
+
Navigate to the [Balena Cloud Sign up](https://dashboard.balena-cloud.com/signup) form and create a new account. The free account lets you manage up to 10 devices with no cost. This Learning Path requires only one device.
14
14
15
-
After you have created your account, you can create a fleet. A fleet is a collection of devices serving as a single target for deploying applications.
15
+
After you've created your account, you can create a fleet. A fleet is a collection of devices serving as a single target for deploying applications.
16
16
17
17
Create a new fleet and name it `AVH-Testing`.
18
18
19
19
## Download the Balena OS image
20
20
21
-
Add a device to your fleet. Navigate to the `Devices` section of your fleet and click on the `Add Device` button. This will open a dialog to create a custom device image.
21
+
Add a device to your fleet. Navigate to the `Devices` section of your fleet and click on the `Add Device` button. This opens a dialog to create a custom device image.
22
22
23
-
23
+
![Dialog window showing device configuration options including device type selection, edition settings, and network configuration for creating a custom Balena OS image#center](add_device.webp"Add Device dialog window")
24
24
25
25
You can use the Raspberry Pi 4 device on Arm Virtual Hardware (AVH) as the new device.
26
26
@@ -33,14 +33,14 @@ Leave the default values for everything else.
33
33
Download the image by clicking on the drop-down arrow on the right side of the `Flash` button and select `Download balenaOS`.
34
34
35
35
{{% notice Note %}}
36
-
There is no need to install Balena Etcher, the tool used to write SD cards.
36
+
There's no need to install Balena Etcher, the tool used to write SD cards.
37
37
{{% /notice %}}
38
38
39
39
The file is large so the download may take some time.
40
40
41
41
## Convert the download to an AVH custom image
42
42
43
-
When the download is finished, you can convert the Balena OS device image into a custom AVH image that you can upload to the AVH service and run on a Raspberry Pi 4 device.
43
+
When the download finishes, you can convert the Balena OS device image into a custom AVH image that you can upload to the AVH service and run on a Raspberry Pi 4 device.
44
44
45
45
The conversion can be done using a Linux shell script.
46
46
@@ -52,11 +52,11 @@ The conversion script requires a Linux environment with root access. If needed,
52
52
53
53
On a Linux machine, execute the script as root with the downloaded Balena OS image file as the only parameter:
Copy file name to clipboardExpand all lines: content/learning-paths/embedded-and-microcontrollers/avh_balena/3install.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,31 +8,31 @@ layout: learningpathall
8
8
9
9
## Create a new device
10
10
11
-
To create a new device, you need a user account for [Arm Virtual Hardware (AVH)](https://app.avh.arm.com/). If you don't have an account, you can create one using the `Create an Arm account` link below the `LOGIN` button. If you create a new account, you will be automatically enrolled in a free 30-day trial.
11
+
To create a new device, you need a user account for [Arm Virtual Hardware (AVH)](https://app.avh.arm.com/). If you don't have an account, you can create one using the `Create an Arm account` link below the `LOGIN` button. If you create a new account, you'll be automatically enrolled in a free 30-day trial.
12
12
13
-
From the AVH dashboard, click on the `Create Device` button. Select Raspberry Pi 4 from the list of devices.
13
+
From the AVH dashboard, click on the `Create Device` button. Select Raspberry Pi 4 from the list of devices.
14
14
15
-
On the next screen you will be asked to configure your device by choosing the firmware to use.
15
+
On the next screen you'll be asked to configure your device by choosing the firmware to use.
16
16
17
-
Use the `Upload your own firmwware` on the right side to drag or browse for the file `balenaos_rpi4b.zip`.
17
+
Use the `Upload your own firmwware` on the right side to drag or browse for the file `balenaos_rpi4b.zip`.
![AVH firmware upload screen showing drag-and-drop area for uploading custom firmware file with Raspberry Pi 4 device selected#center](upload_firmware.webp"Upload custom firmware screen")
20
20
21
-
Uploading the file takes some time.
21
+
Uploading the file takes some time.
22
22
23
23
After the file is uploaded, click `NEXT`.
24
24
25
25
The final step is to name the AVH device. Select your own name or use `balena-testing-device`.
26
26
27
-
You do not need to set any advanced boot options.
27
+
You don't need to set any advanced boot options.
28
28
29
-
Wait for the device to be created. It is ready to use when you see the ready message:
29
+
Wait for the device to be created. It's ready to use when you see the ready message:
30
30
31
-
31
+
![AVH console showing device status message indicating the Raspberry Pi 4 virtual device is ready and displaying boot completion logs#center](device_ready.webp"Device ready message")
32
32
33
33
## Verify your device is ready
34
34
35
-
You now have access to the console and be are presented with a log in prompt.
35
+
You now have access to the console and are presented with a log in prompt.
36
36
37
37
Log in with the username `root`. If a password is required, use `balena`.
38
38
@@ -44,7 +44,7 @@ Verify `balena` available by running:
44
44
balena version
45
45
```
46
46
47
-
You will see output similar to:
47
+
You'll see output similar to:
48
48
49
49
```output
50
50
Client:
@@ -77,8 +77,8 @@ Server:
77
77
GitCommit: 949e6fa-dirty
78
78
```
79
79
80
-
Return to your Balena Cloud dashboard and refresh the `Devices` page.
80
+
Return to your Balena Cloud dashboard and refresh the `Devices` page.
81
81
82
-
You will see your newly deployed device is registered and connected to your fleet. You are now ready to deploy applications to your device!
82
+
You'll see your newly deployed device is registered and connected to your fleet. You're now ready to deploy applications to your device!
83
83
84
-
84
+
![Balena Cloud dashboard showing the Devices page with one Raspberry Pi 4 device connected, online, and ready to receive application deployments in the AVH-Testing fleet#center](balena_devices.png"Connected device in Balena Cloud")
Copy file name to clipboardExpand all lines: content/learning-paths/embedded-and-microcontrollers/avh_balena/4deploy.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,46 +14,46 @@ As an example, you can deploy a Grafana dashboard from Balena Hub that will show
14
14
15
15
Open Balena Hub in a new tab by clicking on the Balena Hub button on the top right corner of your Balena Cloud dashboard.
16
16
17
-
17
+
![Balena Cloud dashboard header showing the Balena Hub button in the top right corner next to other navigation elements#center](balena_hub_button.png"Balena Hub button location")
18
18
19
19
On the Balena Hub, click `Apps` in the top navigation bar, then search for `balena-app`. This is a pre-built dashboard backed by Grafana and served by Nginx.
20
20
21
-
21
+
![Balena Hub Apps page displaying search results for balena-app, showing the application card with description and deployment options#center](balena_hub_app.webp"balena-app in Balena Hub")
22
22
23
-
Click on the app to open the details page.
23
+
Click on the app to open the details page.
24
24
25
-
Look for the `Deploy` button in the upper-right corner of the page.
25
+
Look for the `Deploy` button in the upper-right corner of the page.
26
26
27
-
Clicking this button will take you back to your Balena Cloud dashboard with a dialog to deploy `balena-app` to a fleet.
27
+
Clicking this button takes you back to your Balena Cloud dashboard with a dialog to deploy `balena-app` to a fleet.
28
28
29
-
29
+
![Deployment dialog showing fleet selection options with AVH-Testing fleet highlighted and advanced configuration settings collapsed#center](balena_app_deploy.png"Deploy balena-app to fleet")
30
30
31
31
Select `Use an existing fleet instead` and choose the `AVH-Testing` fleet.
32
32
33
33
You don't need to do any advanced configuration for this app. Click the `Deploy to fleet` button to begin the deployment.
34
34
35
35
{{% notice Note %}}
36
-
If you have more than one device in your fleet, this process will deploy the selected application to all devices in your fleet simultaneously.
36
+
If you have more than one device in your fleet, this process deploys the selected application to all devices in your fleet simultaneously.
37
37
{{% /notice %}}
38
38
39
-
Once the deployment is finished, click on your device in Balena Cloud dashboard to open up the device page. You will see that the Grafana and Nginx services have been deployed to and are running on your device.
39
+
Once the deployment finishes, click on your device in Balena Cloud dashboard to open up the device page. You'll see that the Grafana and Nginx services have been deployed to and are running on your device.
40
40
41
-
41
+
![Balena Cloud device page showing active services with Grafana and Nginx containers running, including service status indicators and log output#center](balena_app_running.webp"balena-app services running on device")
42
42
43
-
You will also be able to see the system logs from your device, and optionally get access to the device's terminal from this Balena Cloud screen.
43
+
You'll also be able to see the system logs from your device, and optionally get access to the device's terminal from this Balena Cloud screen.
44
44
45
-
## Accessing your Grafana dashboard
45
+
## Access your Grafana dashboard
46
46
47
-
Your application is now running, but it's not accessible from the outside world. In order to view your Grafana dashboard in your browser, you will need to tell Balena to make your device accessible from a public URL.
47
+
Your application is now running, but it's not accessible from the outside world. To view your Grafana dashboard in your browser, you need to tell Balena to make your device accessible from a public URL.
48
48
49
-
Toggle the `Public Device URL` switch to the `On` position.
49
+
Toggle the `Public Device URL` switch to the `On` position.
50
50
51
-
A link will appear next to the switch, click on it to open the newly created public URL.
51
+
A link appears next to the switch, click on it to open the newly created public URL.
52
52
53
-
53
+
![Balena-app login screen showing username and password fields over a dark background with the Grafana logo and branding#center](balena_app_login.webp"balena-app login page")
54
54
55
-
This will open the `balena-app` on your device in your browser. You will be presented with a log in screen, use the default username `admin` and password `admin` to log in. You will be prompted to set a new password for the `admin` user before continuing.
55
+
This opens the `balena-app` on your device in your browser. You're presented with a log in screen, use the default username `admin` and password `admin` to log in. You'll be prompted to set a new password for the `admin` user before continuing.
![Grafana dashboard showing real-time system metrics including CPU usage, memory consumption, network traffic, and container status for the Balena OS device#center](balena_app_dashboard.webp"balena-app dashboard with system metrics")
58
58
59
59
You now see the Grafana dashboard monitoring your Balena OS installation on this device, including the containers running Grafana and Nginx.
Copy file name to clipboardExpand all lines: content/learning-paths/embedded-and-microcontrollers/avh_balena/_index.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
---
2
-
title: Deploy IoT apps using Balena Cloud and Arm Virtual Hardware
2
+
title: Deploy IoT applications with Balena Cloud and Arm Virtual Hardware
3
+
4
+
description: Learn how to create a custom Balena OS image, run it on Arm Virtual Hardware, and deploy IoT applications to a virtual Raspberry Pi 4 device.
Copy file name to clipboardExpand all lines: content/learning-paths/embedded-and-microcontrollers/cmsis_rtx/_index.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
2
title: Build an RTX5 RTOS application with Keil μVision
3
3
4
+
description: Learn how to create, build, and debug an RTX5 RTOS-based application using Keil μVision with CMSIS-RTOS2 API and Event Recorder for embedded Cortex-M development.
Copy file name to clipboardExpand all lines: content/learning-paths/embedded-and-microcontrollers/cmsis_rtx/build_and_run.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,9 @@ Click `Run` (`F5`) to start the application, and after a short time, click `Stop
23
23
24
24
Observe in the `RTX RTOS` view that the threads have been created. Two other threads, `osRtxIdleThread` and `osRtxTimerThread` will also be created.
25
25
26
-
26
+
![Screenshot of the RTX RTOS view in Keil μVision showing the list of created threads including thread_1, thread_2, osRtxIdleThread, and osRtxTimerThread with their status and priority information#center](keil_rtos.png"RTX RTOS threads view")
27
27
28
-
However no output is seen in the `printf viewer`. This is because semihosting is not supported. You will learn how to address this in the next section.
28
+
However no output is seen in the `printf viewer`. This is because semihosting isn't supported. You'll learn how to address this in the next section.
29
29
30
30
Exit the debug session (`Ctrl+F5`).
31
31
@@ -48,13 +48,13 @@ You must now create a `Debug Configuration`:
48
48
49
49
When debugging, use the `OS Data` view to observe RTOS information. Open from the `Window` > `Show View` menu. Use the pull down to select different categories.
50
50
51
-
51
+
![Screenshot of the OS Data view showing RTOS thread information including task names, states, and stack usage#center](os_data.png"OS Data view with thread details")
52
52
53
53
For thread aware debug, right-click on the debug connection in the `Debug Control` view, and select `Display threads`.
54
54
55
-
55
+
![Screenshot of the Debug Control view with the context menu showing the Display threads option for thread-aware debugging#center](debug_control.png"Debug Control view with thread display option")
56
56
57
-
You will see the printf() output in `Target Console` pane.
57
+
You'll see the printf() output in `Target Console` pane.
Copy file name to clipboardExpand all lines: content/learning-paths/embedded-and-microcontrollers/cmsis_rtx/create.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This learning path will introduce the steps to create a basic RTX based RTOS app
11
11
12
12
For more information on the latest update, see the [CMSIS v6 is here](https://community.arm.com/arm-community-blogs/b/tools-software-ides-blog/posts/cmsis-v6-is-here) blog.
13
13
14
-
You will use [Keil MDK](/install-guides/mdk) through this Learning Path. If you are using [Arm Development Studio](/install-guides/armds) refer to the appropriate comments.
14
+
You'll use [Keil MDK](/install-guides/mdk) through this Learning Path. If you're using [Arm Development Studio](/install-guides/armds) refer to the appropriate comments.
15
15
16
16
{{% notice Note%}}
17
17
If using `Arm Keil Studio for Visual Studio Code` please go to [Build an RTX5 RTOS application with Keil Studio (VS Code)](/learning-paths/embedded-and-microcontrollers/cmsis_rtx_vs/).
@@ -47,15 +47,15 @@ Then select `CMSIS C/C++ Project`, using `Arm Compiler for Embedded 6`.
47
47
48
48
### Select device
49
49
50
-
You will then be prompted to `Select Device` for your project. A list of all devices with their CMSIS-Packs installed will be shown.
50
+
You'll then be prompted to `Select Device` for your project. A list of all devices with their CMSIS-Packs installed will be shown.
51
51
52
52
For this example, select `Arm` > `Arm Cortex-M4` > `ARMCM4`. Click `OK`.
53
53
54
54
## Manage Run-Time Environment
55
55
56
-
You will first be presented with the `Manage Run-Time Environment` dialog, which allows you to specify the CMSIS software components that will be used in the project.
56
+
You'll first be presented with the `Manage Run-Time Environment` dialog, which allows you to specify the CMSIS software components that will be used in the project.
57
57
58
-
Under `CMSIS`, select `CORE`, as well as `RTOS2 (API)` > `Keil RTX5`, in `Source` form. You will also need to select `CMSIS` > `OS Tick (API)` > `SysTick`.
58
+
Under `CMSIS`, select `CORE`, as well as `RTOS2 (API)` > `Keil RTX5`, in `Source` form. You'll also need to select `CMSIS` > `OS Tick (API)` > `SysTick`.
0 commit comments