STM32 MCUs Boards and hardware tools

Posted on October 19, 2014 at 23:20Hello,I'm having issue to connect to my newly bought STM32F4 discovery board with the- STM32 ST-LINK Utility v3.4.0- StlinkUSB Driver V4.3.3.0When I try to connect it's always failing with any parameter in the settings box.https://sites.google.com/site/levequejerome/_/rsrc/1413753212515/home/version.jpghttps://sites.google.com/site/levequejerome/home/connect1.jpg?attredirects=0https://sites.google.com/site/

Posted on September 12, 2014 at 05:26Used St-link 3.4.0 to read the boards demo program the wrote back, demo does not work anymore, same for 407 and 401 models. do I need to set options different maybe.  #st-link

Posted on August 25, 2014 at 10:55I am using STM32L100 MCU with STLink v2 for debug and flash/eeprom programming thru SWD. This is a device with soldered battery - i.e. it is permanently supplied. If I want to reprogram e.g. EEPROM I connect STLink and with STLink utility reprogram the Eeprom with ''connect under reset'' setting. However from that time on, the device is consuming ~240uA even thou the STLink is disconnected. The only way to avoid it is to disconnect and reconnect the battery. It looks like some programming/debug logic is activated by STLink, but is not shut down when external nRST is pulled. How should one avoid this? Is there any code to execute at devices restart to disable this logic consumption. I do only ''disable'' the SWD pins byt switching them to GPIO atm. #stm32l1 #stlink

Posted on August 28, 2014 at 12:08Hi, I was uploading programs to Standard STM32F051R8 development board. While trying to upload the code, suddenly I have started getting an error message ''ST link No MCU Device found''. After I click on OK I got another message ''failed to load flash loader: C:\ProgramFiles\IAR-------Flashloader\ST\flashSTM32F05xx8.h''. Then click on OK will generate another error ''A fatal error has occurred, The debugger will terminate'' . I have removed and reinstalled the driver for STlink. I have used a pin near to BOOT0. Accidentally, if a high or low to BOOT0 will make any issues?????? Also I am able to upload the program with one condition. Hold the reset key, then upload the program and then release the reset button. This will upload program. can anybody share any solution????? #st-link-no-mcu-device-found

Posted on November 07, 2012 at 20:24I'm trying to verify that I can program an STM32L on the Discovery board using an external ST-Link V2 debugger. As far as I know, I only need the SWDIO and SWCLK pins (7 and 9 respectively) and ground. The SWDIO line goes to PA13 and the SWCLK goes to PA14. I have the jumpers on CN3 disconnected in hopes that cuts the built-in SWD debugger off from the STM32L. I've powered it on externally, not through USB to avoid contention. However I either get an ''Internal Command Error'' when I try to ping the STM32L or the core is stuck in reset (it depends on how I power it up). Is there any way I can actually use an external debugger to talk to the STM32L on the Discovery board? I would like to verify I can do this before we spin a prototype CCA. #st-link #stm32l-discovery

Posted on July 29, 2014 at 01:49Hi i'm new using ARM architecture i bought the STM32F4 Discovery Evaluation Card, it stop working after trying to load my first program, the demostration code no longer runs, the only thing is doing when i plug the USB cable is, LD2(PWR), LD4 and LD8, my pc does not detect the device it says USB Device Not Recognized, i'm using MDK-ARM it no longer detects the device, glad someone could help me, i couldn't even load my first program :/, Sorry for my bad english #st-link-not-working #st-link

Posted on July 24, 2014 at 12:08 Hi, I'm trying to program http://andybrown.me.uk/wk/wp-content/images//awreflow/schematic.pdf with a stm32f0308-disco st-link but it only works if I power the board with the 3v from the disco board if I power the board from an external 3.3V it gives this error: ze@ze-VGN-CS11S-W:~/Development/openocd-code$ openocd -f tcl/interface/stlink-v2.cfg -f tcl/target/stm32f0x_stlink.cfg Open On-Chip Debugger 0.9.0-dev-00093-g518ce9e (2014-07-09-16:15) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : This adapter doesn't support configurable speed Info : STLINK v2 JTAG v17 API v2 SWIM v0 VID 0x0483 PID 0x

Posted on June 24, 2014 at 08:36  I am downloading file to chip with stlink/V2, the command line tool works fine for me.However, if the chip is on protect statue, the command line tool failed with below log:>>> Erasing PROGRAM MEMORYThe device is protectedOperation abortedCould anyone give me some clue on how to unlock the protection?BTW, if the chip is protected by Jlink's ''secure chip'', can stvp unlock it? #st-link/v2-stvp #stm32

Posted on June 12, 2014 at 06:50Hi,I am planning to use STM32 series microcontroller (http://www.st.com/web/catalog/mmc/FM141/SC1169/SS1031/LN1565/PF164476) in my project. Wondering if anyone has footprint library for LQFP48 package. I am designing the PCB in KiCAD.  #stm32-kicad-eda #pcb-design

Posted on May 10, 2014 at 01:24I have no problem using Utility v3.1.0 and firmware V2.J17.S0 with a Discovery-F3. I'm having a problem with v3.3.0 (the latest) with firmware V2.J19.S0. Most everything works except that the MCU Core Panel dialog fails to show register values. That dialog can still halt, reset, start okay -- just no register values. Has anyone else tried this? Do the register values show using the latest (v3.3.0) ST-Link Utility together with any ST-LINK/V2, not just the one embedded on a Discovery-F3, like say one on another EVAL or DISCOVERY board or when using the standalone adapter that comes in a finished enclosure? -Gary #st-link-utility-discovery-f3

Posted on April 19, 2014 at 16:52Hi there, I've designed a board on stm32f407zgt6 earlier and succeeded to connect my board with st link. All SWD connections were directly taken out from controller with no external pull-ups or pull-downs. Now again I've designed a board on stm32f429igt6 (176 pin package). On this board I've successfully programmed my code once. But after that I could not connect my board with st-link anymore. I'd also tried with new boards and new controllers but failed in doing so. I am using on board st-link debugger (one which comes with discovery boards). Boot0 pin is directly ground (I've also tried to pull it down through 1k resistor) Boot1 is floating. Any kind of help/suggestion will be appreciated. Thanks #st-link-not-connected-stm32f4

Posted on March 24, 2014 at 02:43Hi all, I am using the STM32's ITM to output log messages to my PC via SWO.  However, I have run into issues with losing characters (as has been noted elsewhere; e.g., /5056d518).  Apparently ST-LINK fw V2.J19.S0 improves the situation somewhat, so I updated the firmware on my STM32F3DISCOVERY board to this version.  However, with the v19 firmware, I only ever receive 24 characters from the ST-LINK, after which point I have to unplug/replug the device in order to be able to restart tracing. I wrote a simple application to test this further:int main(void) {     while (1)         ITM_SendChar('x'); } With ST-LINK fw V2.J17.S0 this outputs a continuous stream of x characters as expected (viewed using the Serial Wire Viewer component of the STM32 ST-LINK Utilit

Posted on June 18, 2012 at 20:59Hi to all STM guys here. Thank for all the great eval boards you do.We just had a sparks-generating discussion on a forum from where camse an idea that we miss an interaction with PC capability on the discovery boards. I just had a look at F4 board and confirmed that there's USART2 unoccupied on STM32F103C8T6 chip. That means that it is feasible to hack the board a bit to connect an USART on the main chip with USART2 on the debugger chip. The debugger chip would serve than as both ST-Link (for debugging) and as VCP for interaction with a terminal on PC. That would greatly help to have this possibility outside of IDE.To do so what we need is either sources of firmware of the debugger (so the community could modify it to implement the needed functionality) or the firmware with amplemented functionality from ST so we could flash that ourselves.Please let us know if that is possibl

Posted on April 19, 2013 at 18:11Hi, for an automatic test, i need to Halt and Run a STM32. It works without problems with the STM32 ST-LINK Utility, but not (program is  still running) when I use the CLI (st-link_cli.exe) in this way:st-link_cli.exe -c SWD -Halt the answer for this statement is:  STM32 ST-LINK CLI v1.5.1  STM32 ST-LINK Command Line Interface    Connected via SWD.  Connexion mode : Normal.  ST-LINK Firmware version : V2J17S4  Device ID:0x416   Device family :STM32L1xx medium density All other statements give a message that the statment were accepted Can anyone check this, maybe with older firmware? What tool can I use alternati

Posted on January 23, 2014 at 14:00Hi All, I've ported the VCP to F3DISCOVERY ([DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Discovery/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Discovery/STM32F3DISCOVERY%20USB%20CDC%20%28Virtual%20COM%20port%29%20Example&FolderCTID=0x01200200770978C69A1141439FE559EB459D75800084C20D8867EAD444A5987D47BE638E0F&TopicsView=https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/AllItems.aspx&currentviews=1013]taken from here) board but the one problem has been raised - application has broken SWD. As fact reprogramming (from Keil) and debug is impossible. I'm getting error ''Cannot access target. Shutdown debug session'' when I'm trying start the application in debug mode. And I'm getting ''Internal communication error'' for any other attempts. After it any other deals with board via ST-LINK are impossible due to following error: Target DLL has been cancelled. Debugger

Posted on January 21, 2014 at 23:03Hi, I've been using the STM32F429 disco for a month or so and never had any problems. I connected my disco board via usb to my pc today and I keep getting the ''No target connected'' message when I try to download compiled code to the board. I've checked the debug settings and no SW link device is found and similarly in the ST-LINK Utility I cannot get the disco board to connect. The program that I downloaded onto the board a couple of days ago still runs with no problems. Please could someone help me with problem as I've never come across this before? Cheers :) #stm32f429 #discovery #st-link

Posted on January 11, 2014 at 12:01How can I debug stm32 apps by st-link/v2 on Macintosh?Where are drivers of st-link/v2 for OS X Mavericks? #stlink-macintosh-st-link/v2-ma

Posted on January 09, 2014 at 15:39Hi, I have bought: 1)a STM32F4DISCOVERY board (with on-board ST-LINK/V2 programmer/debugger) http://www.st.com/web/en/catalog/tools/PF252419 2)a separate ST-LINK/V2 programmer/debugger. http://www.st.com/web/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168   I have downloaded and installed on my PC (windows XP) the following tools: 1) STSW-LINK003 (ST-LINK/V2 USB driver for Windows 7, Vista and XP) http://www.st.com/web/en/catalog/tools/PF258167 2) STSW-LINK004 (STM32 ST-LINK utility)

Posted on December 20, 2013 at 21:23I'm using a recently purchased ST-LINK/V2 programmer to try and connect to a STM32F105 chip, and following the driver download link on the page http://www.st.com/web/en/catalog/tools/PF258167 gives me a Page not found - 404 Server Error.  Luckily I was able to find an outdated driver that came with the IAR embedded workbench IDE I am using, however I would like to update to the latest driver if possible.  Is there another link or location for this download that I am missing?The exact same issue occurs when I try and download the ST Visual Programmer at http://www.st.com/web/catalog/tools/FM147/CL1794/SC961/SS1533

Posted on November 18, 2013 at 19:18Hello community,I just got my beautiful STM32L board. I am moving from arduino to something more complex. However, the new info has been really overwhelming. Since morning I have been trying to figure out how to upload a simple blinking program into the board, with no luck. It seem that everything is much more complicated than what I am used to (arduino). Anyway, I got Keil IDE,and have been trying to prog the board but it seems that I need ST Linker for that, is that right? Cannot I just connect the board to USB port? Also how would I load a blinking instruction into uC? Any tutorial or suggestion? I just want to know if I am in right track? #stm32l #st-linker #how-to-start

Posted on October 31, 2013 at 01:27Hi,I am using the ST-Link/v2 for the first time.  I tried loading firmware and when I select ''Program Verify'' and then select the .hex file, I immediately get a pop up window with the following message, ''Encountered an Improper Argument''.  What does this mean? #st-link

Posted on October 24, 2013 at 10:30When I run the CLI tool for programming including a verify, this is not working:R:\Shared\Evertz\Automatic ST-link program>ST-LINK_CLI.exe -P ''SYGDR scripts/Boo tloaderSTM32F0xx-v02.bin'' -V 0x08000000 STM32 ST-LINK CLI v1.4.0 STM32 ST-LINK Command Line InterfaceConnected via SWD. Device ID:0x440 Device family :STM32F05x Flash Programming:   File : SYGDR scripts/BootloaderSTM32F0xx-v02.bin   Address : 0x00000000 [0x00000000]:Invalid address! When I only do a program it works fine, Does anyone has any idea what is going on? #st-link-cli-verify

Posted on August 10, 2013 at 23:28I have tried to use serial wire viewer capability in St Link utility. See attached file for source code. This simple code emits sequence ''012345689'' of char but seems the ST-Link 2 is loosing the sync with the output stream. Can anybody comment this ? Probably bug inside ST Link firmware ? #swv-st-link/v2 #st-link-utility

Posted on August 22, 2013 at 23:25       Dear forum members,     I am using OPENOCD under Ubuntu(Linux distro).   What should i do ,to solve following error:   ''This adapter does not support variable speed.''    #stm32 #linux #linux #st-link #openocd #debugger #debug-stm32-using-st-link/v2 #stm32-discovery #openocd-stlink-linux

Posted on July 25, 2013 at 16:17Hi all, I am using STM32L151CBU6 and STM32L151C8U6 with 128KB and 64KB Flash, respectively. However, Atollic Truestudio (via ST-Link) is able to flash 88KB to the one with 64KB Flash and it seams working correctly. My own bootloader also flashes 88KB and it works. It seems that C8U6 is just a ''renamed'' CBU6. The only thing is that ST-Link utility sees C8U6 as 64KB target and does not allow to flash it over 64KB, but it reads full 128KB. Does anyone have some experience about this? Is it just the batch of C8U6 I have in hand? Would it reliable enough? I guess ST can't guarantee it. #st-link #flash-size