RN0093 About this release note - STMicroelectronics

1 About this release noteThis release note contains information About the latest firmware versions for ST-LINK, ST-LINK/V2, ST-LINK/V2-1, and STLINK-V3 boards. It can be used to identify the version of the firmware currently running and, if necessary, upgrade firmware throughthe USB is the part number of the firmware upgrade application for ST-LINK, ST-LINK/V2, ST-LINK/V2-1, and 1. ST-LINK board firmware upgrade release summaryTypeSummaryMajor and : STLINK-V3: Fix data loss on VCP-RX (ST-LINK UART Tx) at baud rate lower than 2400 Bd Update of drag-and-drop programming feature for new or near-future STM32 targets Improvement of power off sequence Support for future STLINK-V3E hardware evolutionCustomer supportFor more information or help concerning ST-LINK, ST-LINK/V2, ST-LINK/V2-1 and STLINK-V3 boards, contact the nearestSTMicroelectronics sales office. For the complete list of STMicroelectronics offices and distributors, refer to the updatesSoftware updates and all the latest documentation can be downloaded from the STMicroelectronics support webpage upgrade for ST-LINK, ST-LINK/V2, ST-LINK/V2-1and STLINK V3 boardsRN0093 release noteRN0093 - Rev 28 - June 2022 For further information contact your local STMicroelectronics sales PC system requirementsPC and compatible running with: Windows 10 , Linux , and macOS 64-bit operating systemsThe application requires to install the Java Runtime Environment 7u51 (or more recent).

2 On the Windows operating system, the ST-LINK board requires to install a dedicated USB driver (STSW-LINK009). In case theSTSW-LINK009 driver is not installed by the used toolset, it can be downloaded from the web Linux , the application relies on , which must be installed separately. For instance, on Ubuntu ,this is done through the command sudo apt-get install Linux , users must be granted rights for accessing the ST-LINK USB devices. To do that, it might benecessary to install one of the packages (depending on the Linux version) provided into :STLINK-V3 boards can be recognized by Windows 10 without any driver installation. However, ST-LINK driverinstallation is required for previous ST-LINK ST-LINK boards feature an STM32 32-bit microcontroller based on the Arm Cortex -M :macOS is a trademark of Apple Inc., registered in the and other countries and is a registered trademark of Linus is a registered trademark of Oracle and/or its is a registered trademark of Canonical is a trademark of the Microsoft group of is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or is delivered under the Mix Ultimate Liberty+OSS+3rd-party V1 software license agreement(SLA0048).

3 RN0093 Host PC system requirementsRN0093 - Rev 28page 2/192 Change in and On STLINK-V3 SET and STLINK-V3 MODS, upgrade firmware to the version V3J10M3B5S1. On STLINK-V3 boards, STLINK-V3 MINI, and STLINK-V3 MINIE, upgrade firmware to the version V3J10M3. On ST-LINK/V2-1 boards, upgrade firmware to the version V2J40M27 (STM32) or V2M27S7 (STM8). On ST-LINK/V2 boards, upgrade firmware to the version V2J40S7. On ST-LINK boards, upgrade firmware to the version and corrections On ST-LINK/V2-1 and STLINK-V3 boards: Added the support for drag-and-drop programming on new and near-future STM32 targets. Improved the power off sequence. Deinit the target pin inputs earlier during the power off sequence onboards where ST-LINK manages the target power. Added the support for the future STLINK-V3E hardware evolution. Clarified an STLinkUpgradeerror message from Unexpected device ID for ST-Link micro. Don't know how toupgrade. to STLink hardware probably too recent for this upgrade , use new tool version from.

4 On STLINK-V3 boards: Fix data loss on VCP-RX (ST-LINK UART Tx) at a baud rate lower than 2400 Bd. Data is no moretruncated when sending more than 65 bytes of data from the PC (USB) to the target (UART) at alow UART baud rate. Refer to the STLINK-V3 SET debugger/programmer for STM8 and STM32 usermanual (UM2448) for details on the UART baud rates supported by in and - Rev 28page 3/193 Known problems and limitations In some cases, the activation of the readout protection on the STM32 target might prevent the applicationfrom running. For instance on STM32G0316-DISCO, where the ST-LINK firmware is not able to generatea target power cycle when required. In this case, either do not activate the readout protection, or disablethe ST-LINK mass storage interface. This can be done by updating the firmware with STLinkUpgrade (firstactivate the [change type] checkbox, then select the firmware without mass storage, and ultimately launchthe update). The operation is reversible.

5 The ST-LINK mass storage interface (allowing the target application drag-and-drop programming) mightsometimes be problematic for the host PC (because of company policy or incompatibility with some hostapplication). It might also impact the target application startup because of the connection attempt by theST-LINK to identify the target (readout protection or secure initialization sequences for instance). In case ofissue, the ST-LINK mass storage interface can be disabled by updating the firmware with STLinkUpgrade(first activate the [change type] checkbox, then select the firmware without mass storage, and ultimatelylaunch the update). The operation is reversible. On targets running at low CPU frequencies (less than 250 kHz), the SWD clock frequency must also bereduced for correct communication. The SWD maximum clock frequency (4 MHz approximately) is not functional on targets powered V. Such targets must use a lower SWD clock frequency (to configure from the toolset using theST-LINK).

6 ST-LINK (V1) boards are not supported on the Linux and macOS operating systems. Only ST-LINK/V2,ST-LINK/V2-1, and STLINK-V3 boards can be updated from these operating systems. Applications programmed through the mass-storage interface (drag-and-drop to disk) must fulfill bothconstraints listed below. Applications not respecting one of these constraints are not programmed throughthe mass-storage interface but can be programmed through other tools, such as STM32 CubeProgrammer(STM32 CubeProg): A stack pointer value (first entry of the vector table) in the range of the microcontroller RAM range A reset vector value (second entry of the vector table) in the range of the microcontroller flash memoryrange On STLINK-V3 boards, high SWD and JTAG frequencies are sensitive to the target connection environment;In case of communication issues, firstly try to reduce such frequencies in the settings of the tool being used. The error message Unexpected device ID for ST-Link micro.

7 Don't know how toupgrade probably means an attempt to run on an STLINK-V3 board an STLinkUpgrade version too old forthe board . Try with a more recent version of STLinkUpgrade. On STLINK-V3 SET, STLINK-V3 MINIE, and STLINK-V3 MINI, the STM32 target flash memory programmingwith drag-and-drop action requires the target to be connected to the STLINK-V3 SET, STLINK-V3 MINIE,or STLINK-V3 MINI (SWD/JTAG link) before the STLINK-V3 SET, STLINK-V3 MINIE, or STLINK-V3 MINI isplugged to the host (USB cable). Moreover, this functionality is not available for STM8 targets. On STLINK-V3 SET and STLINK-V3 MODS, limitations on SPI bridge interface: STLINK as SPI slave: mode not supported SPI half duplex: mode not supported Limited full-duplex support (cannot simultaneously send and receive, but sequentially) On STLINK-V3 SET and STLINK-V3 MODS, limitations on I2C bridge interface: STLINK as I2C slave: mode not supported Digital Noise Filter (DNF): not tested 10-bit addressing: not tested On STLINK-V3 SET and STLINK-V3 MODS, limitations on CAN bridge interface: Only standard and loop-back modes supported On STLINK-V3 boards in high-performance mode, the minimum baud rate for Virtual COM port is2931 bauds.

8 STLINK-V3 boards do not function on USB FS ports, but require at least USB HS problems and limitationsRN0093 - Rev 28page 4/19 On ST-LINK/V2-1 and STLINK-V3 boards, the support of .hex files drag-and-drop programming relies on anartificial increase of the virtual mass storage disk , this size is made much bigger than the size of the real flash memory, making it possible todrop a file larger than the target flash memory without warning from the mass storage host driver. In thatcase, the whole flash memory can be programmed before the error is detected and reported by the .hex file format constraints for safe drag-and-drop programming are: max line byte count: 0x20 flash memory address in ascending order (ordered section) address range: flash memory base address 0x08000000 to 0x08000000 + flash memory size programing done by 128-byte blocks (0xFF is programmed in case of unaligned block address) Linux /macOS /Windows DOS line termination (LF, CR, CRLF) RN0093 Known problems and limitationsRN0093 - Rev 28page 5/194 release information for previous of changes in and On STLINK-V3 SET and STLINK-V3 MODS, upgrade firmware to the version V3J9M3B5S1.

9 On STLINK-V3 boards and STLINK-V3 MINI, upgrade firmware to the version V3J9M3. On ST-LINK/V2-1 boards, upgrade firmware to the version V2J39M27 (STM32) or V2M27S7 (STM8). On ST-LINK/V2 boards, upgrade firmware to the version V2J39S7. On ST-LINK boards, upgrade firmware to the version and corrections On ST-LINK/V2-1 and STLINK-V3 boards: Allowed read access to DBGMCU_DBG_AUTH_DEVICE register as required by the RDP regressionsequence on STM32U5xxxx devices Added support for drag-and-drop programming on new STM32 of changes in and On STLINK-V3 SET and STLINK-V3 MODS, upgrade firmware to the version V3J8M3B5S1. On STLINK-V3 boards and STLINK-V3 MINI, upgrade firmware to the version V3J8M3. On ST-LINK/V2-1 boards, upgrade firmware to the version V2J38M27 (STM32) or V2M27S7 (STM8). On ST-LINK/V2 boards, upgrade firmware to the version V2J38S7. On ST-LINK boards, upgrade firmware to the version and corrections On ST-LINK/V2-1 and STLINK-V3 boards: Added command providing information About SWV reachable frequencies to host applications Fixed drag-and-drop programming failure on STM32WB5xxx microcontrollers when the SP value is inSRAM2 memory ranges Modified target initialization sequence for mass storage disk configuration: after a failing first attempt,try a power-reset sequence On STLINK-V3 boards: Possibility to enable/disable the mass storage interface.

10 If the mass storage interface is disabled(through STLinkUpgrade GUI), the STLINK-V3 board enumerates as a new STLink USB device,which may not be recognized/usable by old tool versions (such as for IAR Systems IAR EmbeddedWorkbench , Keil MDK-ARM, or STMicroelectronics STM32 CubeIDE or STM32 CubeProgrammer(STM32 CubeProg)).In that case it is necessary to update to a more recent tool version or to enable back the mass support on Linux , the installation of updated ST-Link rules files must be done before disabling themass storage interface. The installation package is provided in subdirectory AllPlatforms/StlinkRulesFilesForLinux. Increased SWV buffer size Minor correction on USB descriptors On ST-LINK/V2 and ST-LINK/V2-1 boards: Changed access flags for better management of variables in cache through Cortex M7 AXI of changes in and On STLINK-V3 SET and STLINK-V3 MODS, upgrade firmware to the version V3J7M3B5S1. On STLINK-V3 boards and STLINK-V3 MINI, upgrade firmware to the version information for previous releasesRN0093 - Rev 28page 6/19 On ST-LINK/V2-1 boards, upgrade firmware to the version V2J37M27 (STM32) or V2M27S7 (STM8).