![]() ![]() I read the API documentacion, 'Enable_STM32_Discovery.pdf' and make all the changes that I've to. Please refer to Connecting JTAG/SWD for debug and Connecting UART port for standalone external ST-LINK.I am using de STM32DiscoveryF4 in my project and the CC2564MODN bluetooth module with the adapter kit to make a bluetooth serial port profile with the API's that TI brings (SPPLE), but once the code is flashed and the board programmed I can't make the COM port appear, even connecting the micro-usb to the PC too. Bypassing the embedded ST-LINK signals and connecting an external hardware probeĬonnect the relevant signals depending on the interface available on the new hardware probe.Please refer to the board description and schematic for how to put the embedded ST-LINK in reset mode if available. To use a newest version of ST-LINK standalone probe or another debug probe, ST-LINK can be bypassed for ST boards that already embed it. The firmware update application embeds the latest firmware version, so do not hesitate to get the latest version of the executable STSW-LINK007 software packageĤ.2 How to bypass the embedded ST-LINK Refer to Hardware versions for connection details.Ĥ To go further 4.1 Updating the embedded firmware Īll information are given in the STSW-LINK007 software package available from Warning Pins are available on the ST-LINK to connect the Rx/Tx and GND signals. The USB device is mounted on the host PC and ready to be used. 3.3 Connecting UART port (from ST-LINK/V2-1) Ī UART serial port is available from the USB link provided by the ST-LINK. SWD: VCC, SWCLK, SWDIO, NRST, SWO and GND signals must be connected to the JTAG/ SWD connector (on some ST-LINK hardware version, a dedicated SWD port can also be available). JTAG: VCC, JTDI, JTMS, JCLK, JRCLK, JTDO, NRST and GDN signals must be connected to the JTAG/ SWD connector. Refer to Hardware versions for connection details. Pins are available on the ST-LINK to connect the JTAG/ SWD signals. Rules must then be added into /etc/udev/rules.d.Īll information and files for installing the udev rules are provided in the STSW-LINK007 package available from (see stsw-link007\AllPlatforms\StlinkRulesFilesForLinux\Readme.txt file).ģ.2 Connecting JTAG/ SWD for debugging Ī JTAG/ SWD link is available from the USB link provided by the ST-LINK. Users must be granted with rights for accessing ST-Link USB devices. The driver is automatically installed by the toolsets supporting ST-LINK. The USB driver for the debugger can differ depending of the PC operating system:Ī driver must be installed before connecting ST-LINK to a Windows® 7, Windows® 7 8, or Windows® 10 PC via the USB. The serial communication port uses standard CDC ACM USB Class, which is usually present by default on all PC operating systems. Two USB drivers are associated to ST-LINK, depending of ST-LINK version: one for the debugger itself, and one for the serial communication port from ( ST-LINK/V2-1). To find out the ST-LINK version that is embedded in your ST board, refer to the Category:STM32 MPU boards page, and then select your hardware board.ģ Getting started 3.1 Installing the USB driver įor details about the different versions, please refer to technical note of ST-LINK derivatives. Several versions of ST-LINK exist: ST-LINK/V1, ST-LINK/V2, ST-LINK/V2-A, ST-LINK/V2-B, ST-LINK/V2-1 and STLINK-V3SET. SWD/ JTAG: debug protocol for STM32 microcontrollers and microprocessors.SWIM: debug protocol for STM8 microcontrollers.ST-LINK can support different debug protocols depending on ST-LINK hardware version and on its embedded firmware version: It can be either embedded on ST boards or provided as standalone dongle. ST-LINK is a USB device and has to be connected to a PC host. The ST-LINK is an in-circuit debugger and programmer for the STM8 and STM32 microcontroller families. 3.3 Connecting UART port (from ST-LINK/V2-1). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |