Skip to main content
S
spider87
Visitor II
April 23, 2025
Solved

Programming problems with STM32F103C8 and ST-LINK V2

  • April 23, 2025
  • 3 replies
  • 701 views

Good morning everyone,


We bought a STM32F103C8T6 Evaluation Board ADS1256 (https://www.amazon.it/Lodokdre-STM32F103C8T6-acquisition-Industrial-Control/dp/B0C582B33D), after writing the firmware I am trying to debug it with the ST-LINK V2 programmer (https://www.digikey.it/it/products/detail/adafruit-industries-llc/2548/6827110). When loading the STM32CUBE IDE firmware I get the error:

Error in final launch sequence:

Failed to start GDB server
Failed to start GDB server
Error in initializing ST-LINK device.
Reason: (18) Could not verify ST device! Abort connection.

Reading some forums they advise me to use OpenOCD as a debugger, but even with this setting I can't communicate.

STM32CubeProggrammer allows me to communicate with the board, but at this stage of work I need the debugger.
Can someone kindly give me some advice?
Thank you very much
Gian

    This topic has been closed for replies.
    Best answer by Peter BENSCH

    ST resources are only dedicated to supporting genuine ST products. We are not committed to ensuring that clones/fakes products work properly with the firmware we provide.

    As suggested by @Andrew Neil we recommend to purchase genuine products and purchase them from known and trusted distributors.

    This thread will now be locked. However, if you face difficulties while using genuine ST products, we’re here to assist you. Please feel free to start a new thread, and our team, along with community members, will be ready to help you with any issues/questions you encounter.

    Good luck!
    /Peter

    3 replies

    A
    Andrew Neil
    Super User
    April 23, 2025
    @spider87 wrote:

    We bought a STM32F103C8T6 Evaluation Board ADS1256 (https://www.amazon.it/Lodokdre-STM32F103C8T6-acquisition-Industrial-Control/dp/B0C582B33D),

    That's a 3rd-party board - not an ST board - so you'll need to contact the supplier for support.

    Probably a high risk that it's not a genuine STM32.

     

    @spider87 wrote:

    I am trying to debug it with the ST-LINK V2 programmer (https://www.digikey.it/it/products/detail/adafruit-industries-llc/2548/6827110). Gian

    That's definitely not a genuine ST-Link - see:

    https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/tac-p/703663/highlight/true#M965

     

    @spider87 wrote:

    Reason: (18) Could not verify ST device! Abort connection.

    See above - most likely a fake chip on your board.

    For best results, get a Nucleo board - which gives a genuine STM32, includes a genuine ST-Link, and is fully supported by ST.

     

    PS:

    The Nucleo is actually cheaper than just that Clone ST-Link at Digikey!

    AndrewNeil_1-1745398376985.png

     

    PPS:

    Some more on fake/clone STM32 chips:

    https://community.st.com/t5/others-stm32-mcus-related/black-pill-debugging-stm32f103rct6-in-keil-fails-to-enter-main/m-p/789880/highlight/true#M6162

      A
      Andrew Neil
      Super User
      April 23, 2025
      @Andrew Neil wrote:

      That's definitely not a genuine ST-Link 

      It even says so on the Digikey listing!

      AndrewNeil_0-1745398092953.png

       

      S
      spider87Author
      Visitor II
      April 23, 2025

      Thanks for the reply @Andrew Neil 
      Yes I understand for the programmer, I also have original programmers that I will try as soon as I am in the office.
      For our application, the core board is not ideal because we are looking for a board that integrates both the high precision ADC and the MCU.
      Is there no way to make the microcontroller recognized, not even with an original programmer? Possible solutions? A last chance is to replace the microcontroller, do you think I will solve the problem?

      A
      Andrew Neil
      Super User
      April 23, 2025
      @spider87 wrote:

      Is there no way to make the microcontroller recognized

      No - It's a fake chip.

      You might be able to find some 3rd-party tools which don't care - but, obviously, they're not supported by ST.

      Again, you should contact the board manufacturer for support.

      And again, see:

      https://community.st.com/t5/others-stm32-mcus-related/black-pill-debugging-stm32f103rct6-in-keil-fails-to-enter-main/m-p/789880/highlight/true#M6162

       

      @spider87 wrote:

      A last chance is to replace the microcontroller, do you think I will solve the problem?

      Sure - if you successfully fit a genuine chip, then it is a genuine chip!

       

      But is that less work than adding an ADC to a known-good board?

      Also, remember that getting actual high-precision results takes more than just fitting a "high-precision" chip; it requires a lot of careful analogue design - does this board have that?

      Can you even get a schematic?

      P
      Peter BENSCHAnswer
      Technical Moderator
      April 23, 2025

      ST resources are only dedicated to supporting genuine ST products. We are not committed to ensuring that clones/fakes products work properly with the firmware we provide.

      As suggested by @Andrew Neil we recommend to purchase genuine products and purchase them from known and trusted distributors.

      This thread will now be locked. However, if you face difficulties while using genuine ST products, we’re here to assist you. Please feel free to start a new thread, and our team, along with community members, will be ready to help you with any issues/questions you encounter.

      Good luck!
      /Peter

      Terms & ConditionsAccessibility statement