You're right that we don't document this at all (and the board models don't have any way of restricting the set of things that '-cpu help' lists to only what they support). As a rule of thumb, for any ARM board except 'virt' don't try to use anything except the default CPU. They all model embedded boards which don't have any kind of support for unplugging and replugging CPUs.
The particular problem with trying to use cortex-m3 on the integratorcp is that there is no NVIC on the integratorcp so if you try to do anything involving the M3's interrupt controller it is likely to blow up or otherwise misbehave. Our two M3 boards are the lm3s6965evb and lm3s811evb (they're Stellaris boards). -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1636126 Title: qemu-system-arm segfaults on "smulbb r7, r5, r5" Status in QEMU: New Bug description: I'll attach a binary that runs fine with qemu-system-arm V2.2.0 but V2.7.0 segfaults. By stepping through with gdb I found that the segfaults happens when executing the line "smulbb r7, r5, r5" (where r7=0x1, r5=0x12). I'll also attach a debugger screenshot. call and output: /opt/qemu-system-arm -M integratorcp -cpu cortex-m3 -semihosting -nographic -monitor null -serial null -no-reboot -kernel 0MFW_SafetyFunctions_ParameteruP1_CUNIT.elf ------------ CUnit_MFW_SafetyFunctions_Parameter ------------ CUnit - A Unit testing framework for C - Version 2.1-0 http://cunit.sourceforge.net/ Suite: Suite_MFW_SafetyFunctions_Parameter Test: MFW_SafetyFunctions_Parameter_PositionLimiter ... Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1636126/+subscriptions
