Skip to content

Commit cb77a71

Browse files
authored
Merge pull request #2962 from pareenaverma/main
Perform Migration between Arm SoC Power LP
2 parents c37c3d9 + 11895a8 commit cb77a71

5 files changed

Lines changed: 16 additions & 21 deletions

File tree

content/learning-paths/servers-and-cloud-computing/arm-soc-migration-learning-path/_index.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,5 @@
11
---
22
title: Migrate applications between Arm platforms using Kiro Arm SoC Migration Power
3-
4-
draft: true
5-
cascade:
6-
draft: true
73

84
minutes_to_complete: 60
95

content/learning-paths/servers-and-cloud-computing/arm-soc-migration-learning-path/graviton-development.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ tar -xzf sensor-monitor.tar.gz
2222
cd sensor-monitor
2323
```
2424

25-
The archive includes the complete source code, a Makefile, and platform-specific implementations. You will analyze and migrate this code using the Arm SoC Migration Power.
25+
The archive includes the complete source code, a Makefile, and platform-specific implementations. You will analyze and migrate this code using the Perform Migration between Arm SoC Power.
2626

2727
### Upload to the Graviton instance for testing
2828

@@ -89,4 +89,4 @@ In this section:
8989
- You confirmed the toolchain and build process work correctly on Arm64 Linux
9090
- You established your baseline for migration validation
9191

92-
In the next section, you'll use the Arm SoC Migration Power to analyze the codebase and migrate it to the target platform.
92+
In the next section, you'll use the Perform Migration between Arm SoC Power to analyze the codebase and migrate it to the target platform.

content/learning-paths/servers-and-cloud-computing/arm-soc-migration-learning-path/migration.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ weight: 4
66
layout: learningpathall
77
---
88

9-
## Use Arm SoC Migration Power for AI-guided migration
9+
## Use Perform Migration between Arm SoC Power for AI-guided migration
1010

11-
In this section, you use the Arm SoC Migration Power to migrate your application between Arm-based platforms. The example demonstrates migration from:
11+
In this section, you use the Perform Migration between Arm SoC Power to migrate your application between Arm-based platforms. The example demonstrates migration from:
1212

1313
- **Source:** AWS Graviton3 (Neoverse-V1, Arm64 Linux, cloud deployment)
1414
- **Target:** Raspberry Pi 5 (BCM2712, Cortex-A76, edge deployment)
@@ -19,11 +19,11 @@ For each step below, an example prompt for the Graviton-to-Pi-5 scenario is prov
1919

2020
### Initiate migration
2121

22-
Open Kiro and describe your migration clearly using the Arm SoC Migration Power.
22+
Open Kiro and describe your migration clearly using the Perform Migration between Arm SoC Power.
2323

2424
Example prompt:
2525
```
26-
I want to use the Arm SoC Migration Power to migrate my sensor monitoring
26+
I want to use the Perform Migration between Arm SoC Power to migrate my sensor monitoring
2727
application from AWS Graviton3 to Raspberry Pi 5 (BCM2712). The application
2828
currently uses simulated sensors on Graviton and needs to work with real
2929
GPIO and SPI hardware on the Pi 5.
@@ -184,7 +184,7 @@ add_executable(sensor_monitor ${COMMON_SOURCES} ${PLATFORM_SOURCES})
184184

185185
In this section:
186186

187-
- You used the Arm SoC Migration Power to analyze architecture differences between Graviton3 and BCM2712
187+
- You used the Perform Migration between Arm SoC Power to analyze architecture differences between Graviton3 and BCM2712
188188
- You designed a HAL that abstracts platform differences and preserves portability
189189
- You generated platform-specific code for the target device
190190
- You updated the build system for multi-platform support

content/learning-paths/servers-and-cloud-computing/arm-soc-migration-learning-path/setup.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -36,15 +36,14 @@ The Arm SoC Migration Power extends Kiro with specialized knowledge and tools fo
3636

3737
- Open Kiro IDE
3838
- Navigate to the **Powers** panel. Press Cmd + Shift + P (Mac) or Ctrl + Shift + P (Windows)
39-
- Select the Arm SoC Migration Power in the **Recommended** section
39+
- Select the Perform Migration between Arm SoC in the **Recommended** section
4040
- Select **Install**
4141

42-
### Verify installation
43-
44-
After installation, enter the following prompt in Kiro:
42+
### Verify install
43+
After installation, you can either click on the "Try power" button or enter the following prompt in Kiro:
4544

4645
```text
47-
I just installed the Arm SoC Migration Power and want to use it.
46+
I just installed the arm-soc-migration power and want to use it.
4847
```
4948
The Power should respond and guide you through any additional setup steps.
5049

@@ -58,7 +57,7 @@ It supports migrations across a wide range of Arm-based platforms, including:
5857

5958
### Install prerequisites
6059

61-
The Arm SoC Migration Power uses the Arm MCP (Model Context Protocol) server to provide specialized Arm migration capabilities. The Arm MCP server runs via Docker.
60+
The Perform Migration between Arm SoC uses the Arm MCP (Model Context Protocol) server to provide specialized Arm migration capabilities. The Arm MCP server runs via Docker.
6261

6362
Install Docker on your local development machine (required for ARM MCP server):
6463

@@ -87,7 +86,7 @@ docker --version
8786
```
8887

8988
{{% notice Note %}}
90-
Ensure Docker is running before using the Arm SoC Migration Power. The Power will automatically pull and run the Arm MCP server container when needed.
89+
Ensure Docker is running before using the Perform Migration between Arm SoC. The Power will automatically pull and run the Arm MCP server container when needed.
9190
{{% /notice %}}
9291

9392
### Launch AWS Graviton3 instance (source platform)
@@ -170,7 +169,7 @@ sudo dnf install -y gcc make wget tar
170169

171170
In this section:
172171

173-
- You installed Kiro IDE and the Arm SoC Migration Power
172+
- You installed Kiro IDE and the Perform Migration between Arm SoC Power
174173
- You provisioned an AWS Graviton3 instance as your source platform
175174
- You installed the build tools needed for the migration example
176175

content/learning-paths/servers-and-cloud-computing/arm-soc-migration-learning-path/validation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ layout: learningpathall
1010

1111
Migration is not complete until the application is validated on both source and target platforms under realistic conditions.
1212

13-
In this section, you will use the Arm SoC Migration Power's testing recommendations to:
13+
In this section, you will use the Perform Migration between Arm SoC Power's testing recommendations to:
1414

1515
- Verify functional correctness
1616
- Confirm platform compatibility
@@ -114,6 +114,6 @@ The Power will analyze platform-specific characteristics. Example analysis:
114114

115115
## What you've accomplished
116116

117-
You've completed the full migration workflow: you validated the source platform build, cross-compiled for the target, ran platform-specific tests, and compared performance between Graviton3 and Raspberry Pi 5. The Arm SoC Migration Power guided each step with architecture-aware recommendations rather than generic advice.
117+
You've completed the full migration workflow: you validated the source platform build, cross-compiled for the target, ran platform-specific tests, and compared performance between Graviton3 and Raspberry Pi 5. The Perform Migration between Arm SoC Power guided each step with architecture-aware recommendations rather than generic advice.
118118

119119
The Discovery → Analysis → Planning → Implementation → Validation workflow you followed here applies to any Arm SoC migration, whether cloud-to-edge, edge-to-edge, or between any pair of Arm-based platforms. The HAL pattern preserves your application's business logic across different Arm SoCs so you can adapt the same codebase without starting from scratch.

0 commit comments

Comments
 (0)