Improved Interface Between SCORE GUI and Third-party SCORECast Tools

Product Family: SCORE
Target CPU: Any
Language: Any
Host: Any

With Release 2.3 of SCORE, a new and improved interface has been implemented between the SCORE GUI and the SCORECast tools. When the AdaCast or CCast tools are invoked, SCORE automatically generates a configuration file that the SCORECast tools read during startup that contain the definition of environment variables key for the compile, link, debug, and load steps used by the SCORECast tools to test a particular module.

Now users define communication and build options all within the SCORE Tool Options dialog and that information gets automatically communicated to the SCORECast tools, eliminating the need for specification of the options again in the SCORECast tools.

AdaCast Configuration file
When AdaCast is run from within SCORE (Tools | SCORECast | AdaCast), a file called ADACAST_.CFG will be generated in the project directory. This file will contain the definition of six environment variables as shown by the following example:

TARGET_VARIANT: PPC_SCORE_BARE (For Native this is set to "HOST").

COMPILATION_SYSTEM: SCORE

LINKER_OPTIONS: -ucc "n:\score\integration\current\SCORE\ppc603e\ucc_excimer" (Motorola Excimer board from Tool Options | Ada Link | Target Link | UCC directory specification)

TARGET_COMMAND_VERB: _ppc603e

SCORE_EXECUTE_CMD: D:\SCORE_TEST\demo\lcj\ppc603e\run_prog.bat (Cross targets only)

SCORE_DEBUG_CMD: D:\SCORE_TEST\demo\lcj\ppc603e\debug_prog.bat (Cross targets only)

 

CCast Configuration file

When CCast is run from within SCORE (Tools | SCORECast | CCast), a similar file called CCAST_.CFG will be generated in the project directory. The environment variables needed are somewhat different than those for AdaCast, but the interface design is basically the same. This file will contain the definition of the environment variables as shown in the following example:

TARGET_VARIANT: PPC_SCORE_BARE (For Native this is set to "HOST").

C_COMPILER_NAME: SCORE Target

C_COMPILER_TAG: SCORE_TGT

C_DEFINE_LIST: VCAST_STDIO

C_PREPROCESS_CMD: tcc_ppc603e -E

C_COMPILE_CMD: tcc_ppc603e -c -g

C_LINK_CMD: tcc_ppc603e -g -Wl: "-U n:\score\integration\current\SCORE\ppc603e\ucc_excimer"

(Motorola Excimer board from Tool Options | C Link | Target Link | UCC directory specification)

C_EXECUTE_CMD: <<score>>

C_DEBUG_CMD: <<score>>

SCORE_EXECUTE_CMD: D:\SCORE_TEST\demo\lcj\ppc603e\run_prog.bat (Cross targets only)

SCORE_DEBUG_CMD: D:\SCORE_TEST\demo\lcj\ppc603e\debug_prog.bat (Cross targets only)

SCORE also generates the run_prog.bat and debug_prog.bat files to contain the proper load and debug options from the Tool Options | Run | Communications and Tool Options | Debug | Communications pages in the Tool Options dialog. In this way, all the various communication methods can be easily utilized by the SCORECast tools. These files are stored in the $PROJECT\$USER\$TARGET directory and executed by the AdaCast or CCast tools when running or debugging the test application.