Hi Peter! Thank you for your help, it works fine with "-M integratprcp -cpu cortex-m4" but I might choose another board as you suggested. I didn't have in mind that we switched to M4 instruction set.
Where do I get the information that integratorcp is not good for cortex-M3? Or better question: where do I get information which machine is good for it? Actually "-M help" doesn't give me any with M3 (already tried "none" and "virt" without success). On the other hand I see all cortex variants in the output of "-M integratorcp -cpu help" so I had a good feeling about it... -- 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
