# Next steps

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/embedded-and-microcontrollers/linux-on-fvp/)
- [Introduction to Arm Fixed Virtual Platforms (FVPs)](https://learn.arm.com/learning-paths/embedded-and-microcontrollers/linux-on-fvp/intro/)
- [Configure Trusted Firmware-A build flags to include cpu_ops support](https://learn.arm.com/learning-paths/embedded-and-microcontrollers/linux-on-fvp/steps/)
- [Modify the device tree for CPU FVPs](https://learn.arm.com/learning-paths/embedded-and-microcontrollers/linux-on-fvp/modify/)
- [Run the Linux software stack on an FVP](https://learn.arm.com/learning-paths/embedded-and-microcontrollers/linux-on-fvp/run/)
- [Debug the software stack](https://learn.arm.com/learning-paths/embedded-and-microcontrollers/linux-on-fvp/debug/)
- [Next steps](https://learn.arm.com/learning-paths/embedded-and-microcontrollers/linux-on-fvp/_next-steps/)

## Explore related resources
Find more information about the topics in this Learning Path:
- [Fast Models Fixed Virtual Platforms Reference Guide](https://developer.arm.com/documentation/100966/)
- [Fixed Virtual Platforms Resources](https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms)
- [Fast Models Reference Guide](https://developer.arm.com/documentation/100964/1128/?lang=en)

## Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

### How do I know my Trusted Firmware-A build includes the correct `cpu_ops` support?
Enable the `cpu_ops` framework for your target CPU when building TF-A. If `cpu_ops` is missing, Linux might fail to start. Confirm that the build selects the CPU-specific implementation (for example, `cortex_a55` or `cortex_a53`) from `lib/cpus/aarch64`.

### What should I change in the device tree for an Arm CPU FVP?
Remove PCI and SMMU nodes and ensure CPU affinity values are set correctly. Leaving unsupported PCI or SMMU entries can cause a kernel panic during boot.

### What result should I expect in the build output before launching the FVP?
Expect an output directory such as `output/aemfvp-a/aemfvp-a` containing items such as `Image` and `Image.defconfig`, as shown by the `tree` command. Proceed when the expected files and symlinks are present.

### How do I capture and review the FVP boot log?
Use the provided run command with `<PATH_TO_LOG>` to save UART output. Review the log for normal Linux boot messages and confirm there are no PCI or SMMU-related panics.

### Which Arm Development Studio version should I use, and how do I start it?
Arm DS `v2022.2` or later is recommended to support DWARF 5 debug information used by GCC 11 and later. Start it with `/opt/arm/developmentstudio-2022.2/bin/armds_ide`, then create a debug configuration to debug Trusted Firmware-A and the Linux kernel.
