How To Test Applications on MCUs

Updating locations of MCU tools and drivers

After Squish for MCU is installed, the paths to MCU tools can be adjusted using two techniques, explained in the next 2 sections.

Updating MCU tools (Squish for MCU) and drivers with squishrunner

The squishrunner command can be used to change the locations of the MCU tools. This approach requires a currently running squishserver process.

The current configuration can be viewed with the following command:

$ ./squishrunner --info mcuSettings
St-Link Programmer      /usr/local/st/stm32cubeclt_1.18.0/STM32CubeProgrammer/bin/STM32_Programmer_CLI
St-Link GDBServer       /usr/local/st/stm32cubeclt_1.18.0/STLink-gdb-server/bin/ST-LINK_gdbserver
NXP     LinkServer      /usr/local/LinkServer_25.7.33
Esp     EnvScriptPath   /usr/local/esp/esp-idf/export.sh

The configuration can be changed through squishrunner with the --config command.

$ ./squishrunner --config mcuSettings <vendor>:<tool>=<value>

These vendor/tool settings are supported:

• St-Link:GDBServer
• St-Link:Programmer
• NXP:LinkServer
• Esp:EnvScriptPath

For example:

$ ./squishrunner --config mcuSettings NXP:LinkServer=/usr/local/LinkServer_25.7.33

Updating locations of MCU tools and drivers in qul.ini

You can edit the qul.ini file to update, add or remove paths. This file is located in the Squish User Settings ver1/ Directory.

The following is an example qul.ini file. Please be aware that the backward slash \ on Windows must be escaped with a preceding backward slash.

[St-Link]
GDBServer=C:\\MCUTools\\STM\\STLink-gdb-server\\bin\\ST-LINK_gdbserver.exe
Programmer=C:\\MCUTools\\STM\\STM32CubeProgrammer\\bin\\STM32_Programmer_CLI.exe

[LinkServer]
InstallPath=C:\\MCUTools\\NXP\\LinkServer