Add new learning path: Arm SoC migration #2817
Conversation
| --- | ||
| title: Migrate applications between ARM platforms with AI assistance | ||
|
|
||
| minutes_to_complete: 150 |
There was a problem hiding this comment.
For me this was about an hour, just as a data point.
| - Validate migrations with automated analysis | ||
|
|
||
| prerequisites: | ||
| - Kiro IDE installed |
There was a problem hiding this comment.
This is not a prerequisite, since the learning path guides the user to install Kiro.
There was a problem hiding this comment.
This should just be a stub file created by hugo, it shouldn't have any actual content and minimal formatting, like this:
---
# ================================================================================
# FIXED, DO NOT MODIFY THIS FILE
# ================================================================================
weight: 21 # Set to always be larger than the content in this path to be at the end of the navigation.
title: "Next Steps" # Always the same, html page title.
layout: "learningpathall" # All files under learning paths have this same wrapper for Hugo processing.
---
|
|
||
| recommended_path: "/learning-paths/servers-and-cloud-computing/intro/" | ||
|
|
||
| further_reading: |
There was a problem hiding this comment.
Further reading should go in further_reading in the _index.md: https://learn.arm.com/learning-paths/cross-platform/_example-learning-path/write-2-metadata/
| @@ -0,0 +1,32 @@ | |||
| --- | |||
| next_step_guidance: > | |||
| Download the sensor-monitor application to your local machine where Kiro IDE is running. This allows you to inspect the code and use Kiro's migration tools. | ||
|
|
||
| ```bash | ||
| wget https://github.com/ArmDeveloperEcosystem/arm-learning-paths/raw/main/content/learning-paths/servers-and-cloud-computing/arm-soc-migration-learning-path/projects/sensor-monitor.tar.gz |
There was a problem hiding this comment.
Would it be possible to put this code into a dedicated public repo? Ideally we don't want zip files in this repo even if they're small, given the current size of the learning path repo.
There was a problem hiding this comment.
ideally everything in the projects directory would go into a dedicated public repo.
| The ARM SoC Migration Power extends Kiro with specialized knowledge and tools for migrating applications between ARM platforms. | ||
|
|
||
| 1. Open Kiro IDE | ||
| 2. Navigate to Powers panel (View → Powers) |
There was a problem hiding this comment.
These instructions do not work on my just-downloaded version of Kiro (0.8.140). Can you please change to View -> Open View -> Powers
|
|
||
| 1. Open Kiro IDE | ||
| 2. Navigate to Powers panel (View → Powers) | ||
| 3. Search for "ARM SoC Migration Power" |
There was a problem hiding this comment.
In my version of Kiro (0.8.140) there is no way to search for a Kiro power. I've attached a screenshot of what comes up when I click "Add Custom Power". The only other place in the interface to add Powers is the "Recommended" tab, but there's no search there either.
|
|
||
| The power will guide you through any additional setup needed and supports migrations between various ARM SoCs including AWS Graviton, Raspberry Pi, NVIDIA Jetson, NXP i.MX, and more. | ||
|
|
||
| ### Install Prerequisites |
There was a problem hiding this comment.
Ideally this section is not needed and we can use the dockerhub version of the Arm MCP Server armlimited/arm-mcp:latest
- Reduce minutes_to_complete from 150 to 60 - Remove Kiro IDE from prerequisites (installed during learning path) - Convert _next-steps.md to minimal stub format - Move further_reading from _next-steps.md to _index.md - Update navigation path to View → Open View → Powers - Remove Power search instructions (not available in Kiro 0.8.140)
Review feedback addressedThanks for the detailed review! I've addressed the following items: ✅ minutes_to_complete: Reduced from 150 to 60 minutes |
3 participants
Before submitting a pull request for a new Learning Path, please review Create a Learning Path
Please do not include any confidential information in your contribution. This includes confidential microarchitecture details and unannounced product information.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the Creative Commons Attribution 4.0 International License.