@REM This bat file has been generated by the IAR Embeddded Workbench
@REM C-SPY interactive debugger,as an aid to preparing a command
@REM line for running the cspybat command line utility with the
@REM appropriate settings.
@REM
@REM After making some adjustments to this file, you can launch cspybat
@REM by typing the name of this file followed by the name of the debug
@REM file (usually an ubrof file). Note that this file is generated
@REM every time a new debug session is initialized, so you may want to
@REM move or rename the file before making changes.
@REM
@REM Note: some command line arguments cannot be properly generated
@REM by this process. Specifically, the plugin which is responsible
@REM for the Terminal I/O window (and other C runtime functionality)
@REM comes in a special version for cspybat, and the name of that
@REM plugin dll is not known when generating this file. It resides in
@REM the $TOOLKIT_DIR$\bin folder and is usually called XXXbat.dll or
@REM XXXlibsupportbat.dll, where XXX is the name of the corresponding
@REM tool chain. Replace the '<libsupport_plugin>' parameter
@REM below with the appropriate file name. Other plugins loaded by
@REM C-SPY are usually not needed by, or will not work in, cspybat
@REM but they are listed at the end of this file for reference.


"E:\Program Files\IAR\common\bin\cspybat" "E:\Program Files\IAR\ARM\bin\armproc.dll" "E:\Program Files\IAR\ARM\bin\armrdi.dll"  %1 --plugin "E:\Program Files\IAR\ARM\bin\<libsupport_plugin>" --backend -B "--endian" "little" "--cpu" "ARM7TDMI" "--fpu" "None" "--drv_verify_download" "all" "--rdi_driver_dll" "E:\Program Files\SEGGER\JLinkARM_V380a\JLinkRDI.dll" "--rdi_catch_exceptions" "0x000" "--proc_driver" "rdi" 


@REM loaded plugins:
@REM    armlibsupport.dll
@REM    E:\Program Files\IAR\common\plugins\CodeCoverage\CodeCoverage.dll
@REM    E:\Program Files\IAR\common\plugins\Profiling\Profiling.dll
@REM    E:\Program Files\IAR\common\plugins\stack\stack.dll