Robot(real firmware) can not be built in System Workbench for STM32. about p2im HOT 6 CLOSED

I fixed this issue in RiS3-Lab/p2im-real_firmware@32993e5

from p2im.

Thanks! it can be built now.Howerver,when i run the "../../../model_instantiation/fuzz.py -c fuzz.cfg", it throws the error:
"PROGRAM ABORT : Test case 'id:000000,orig:random' results in a crash"


I have found that i set the wrong mcu in the fuzz.cfg.Does the mcu have the only following choices?
board = STM32F429I-Discovery
mcu = STM32F429ZI
board = NUCLEO-F103RB
mcu = STM32F103RB
board = Arduino-Due
mcu = SAM3X8E
board = FRDM-K64F
mcu = MK64FN1M0VLL12

from p2im.

The emulator only supports 4 MCUs. You can either recompile your firmware to use one of the MCUs supported, or add your own MCU to the emulator following the instructions in https://github.com/RiS3-Lab/p2im/blob/master/docs/add_mcu.md

from p2im.

Thanks!When i want to test a new firmware, and i use the same board and mcu as yours,it throws an error,how can i solve it?

from p2im.

The firmware hangs when running with the seed input. You may want to dump the execution trace to see where the firmware hangs.

Please append -d exec,int -D qemu.log option to the command below and run it.

The firmware execution trace is dumped to qemu.log.

from p2im.

Thank you very much! I want to know where the code crashes, i run the "run_fw.py".however, i only get the address(like 0x08003658),can i get the line number where the code crashes?

from p2im.