Hi.I use the ARM Development Studio. And I tried to run the Corstone SSE-300 (MPS3) simulator on the Cortex-M55 but an error occurs.Blog where possible hints would not open yet (community.arm.com/.../software-development-for-corstone-300Possible problems: maybe I use the wrong model parametersI tried "-C fvp_mps2.DISABLE_GATING=1 -C cpu0.FPU=1 -C cpu0.MVE=2"
or
"-C cpu0.enable_helium_extension=1 -C cpu0.vfp-present=1 -C cpu0.vfp-enable_at_reset=1".Who managed to run the simulator? Please help me if it is possible to run the simulator? Thanks!
I don't see anything obviously wrong from those screenshots.
Can you start with a known good example, perhaps the Blinky project supplied with the CMSIS pack. Are you using the latest version of the pack (1.2.0)?
Hi Ronan,Yes, I am using the latest version of the pack (1.2.0).The simulator on the Blinky project has started. Thank you!But now an error (pending mode like in the previous screenshot) occurs when there is the "printf" function in the code.Can you please tell me what could be the problem?Thanks!
If the issue is specifically with printf, the issue is likely semihosting. Add the following to the Model Parameters when you launch the model:
-C cpu0.semihosting-enable=1
(you can see all parameters and their default settings by running the model with --list-params (-o list.txt))
You will want to use the models own semihosting system, so also disable this in the debugger, with a target initialization script (so it runs immediately upon connection) with
set semihosting enabled off
Hi Ronan, When I add the "-C cpu0.semihosting-enable=1" to the model parameters, the "printf" function does not print any text to the console.
I have tried "fwrite(..., stdout)" and the output to the console appeared.
Are there any other ways to output text to the console?
Thanks.
If using model semihosting, the output will appear in Target Console (same pane as you see "Iris server starting on port..." messages, and other model output.
The Blinky example uses the UART for printf, which will show up in a separate telnet pane.