blob: 8fc267ca1ab3d89e11e52d0bb9e5a80fe088e1c5 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
|
<think>
Okay, so I'm trying to classify this bug report related to QEMU. The user mentioned that they're having trouble booting a Cortex-M55 image with qemu-system-arm version 7.1. Let me break down the information given.
First, the steps to reproduce involve running qemu-system-arm with specific parameters like -cpu cortex-m55 and -machine mps3-an547. They also mention using gdb for debugging. The issue seems related to booting an image, which makes me think about how QEMU handles machine types or CPUs.
Looking at the possible categories: there's 'boot' as one of them. Boot issues in QEMU often relate to problems during initialization, whether it's with the CPU type, machine setup, or kernel loading. Since the user specified a Cortex-M55 and mps3-an547 machine, which is an Arm development board, the problem could be with how QEMU initializes this configuration.
Other categories like 'device' or 'graphic' don't seem to fit because the issue isn't about hardware devices or graphical output. The user isn't mentioning any problems with peripherals or network issues either. Since it's a boot failure, it's more likely related to the initial setup rather than something else.
I also consider 'hypervisor' but that usually relates to virtualization management, which doesn't seem relevant here. The problem is about booting an image, so 'boot' seems the most appropriate category.
</think>
The issue is about not being able to boot a Cortex-M55 image with QEMU, specifically related to initialization and kernel loading during the boot process.
**Answer:**
boot
|