The IAR C-SPY Debugger
C-SPY batch files
In earlier versions, C-SPY automatically generated these batch files when C-SPY was started in the IDE:
projectname.buildconfiguration.cspy.batproject.buildconfiguration.general.xclwith options specific tocspybatproject.buildconfiguration.driver.xclwith options specific to the C-SPY driver
These files could be used to start cspybat from the command line.
In version 10.x, C-SPY generates these files instead in the directory $PROJ_DIR$\settings:
project.buildconfig.cspy_launch_json.batlaunch.jsonwith options specific tocspybatand the C-SPY driver you are using
Invoke the .bat file on the command line to start cspybat. The files contain the same settings as the IDE uses, and provide hints about additional options that you can use.
Unsafe semihosting
In version 9.x, all semihosting commands were allowed, including unsafe commands that might alter or leak information about the host system.
In version 10.x, unsafe semihosting commands that might alter or leak information about the host system are by default disabled. The debugger will block calls to such functions, and print a message in the debug log. These include reading from and writing to stdin, stdout, and stderr. Reading from or writing to the host file system is considered unsafe, and is disabled by default. This includes the IAR proprietary variant of semihosting (IAR breakpoint).
To enable the unsafe calls, choose Project>Options>General>Library Configuration and select the Enable unsafe semihosting commands option, or specify the cspybat command line option ‑‑unsafe_semihosting to the debugger backend.