Skip to main content
L
LucaLauro
Visitor II
September 3, 2024
Solved

Unable to connect BlackPill via ST-link

  • September 3, 2024
  • 1 reply
  • 3697 views

Hi,

When trying to connect the board via ST-link in CubeProgrammer i get the error: "No STM32 target found!..."; can't figure out what problem is preventing ST-link from finding the target.

BlackPill is working properly, i can use it via DFU, but I would like to use debug.

I tested the ST-link dongle with a NUCLEOF303RET6 and it works fine.

Then i tried using the onboard ST-link of the NUCLEO to connect the BlackPill (with the correct configuration) and had the same problem; so i think the problem may be in the BlackPill (could it be an incorrect code in the identification registers?).

I also tried different bootloaders, although i don't think they can make a difference in this case.

Board: WeAct BlackPill V3.0, MCU: F411CEU6 (original), SWDIO and SWCLK correctly configured on pins PA13 and PA14 (SWD configuration), target voltage 3.28V.

ST-link: V2 dongle, MCU: F103C8T6 (original), tried with reset pin connected, tried with various firmware versions (now v2J45S7).

CubeProgrammer: no mode and reset mode works, tried various versions (now v2.17.0). (ST-link Utility too).

BlackPill_ST-link_Issue.png

What am I missing?

Thanks for your time.

    This topic has been closed for replies.
    Best answer by LucaLauro

    Some time ago, after checking the board, I noticed two pads not soldered correctly, coincidentally they were pin 36 (VDD) and pin 34 (PA13 of the UFQFPN48 package); but I left the hardware work as a last try, being the most risky.

    LucaLauro_1-1725712948482.jpeg

    Having considered all possible causes of malfunction not strictly hardware-related I decided to check this case too, trying to add solder where it was missing.

    After adding it... surprise! it works flawlessly in every mode.
    Seems that it was just a faulty solder, despite it being an original WeAct BlackPill.

    LucaLauro_2-1725713474130.png

    Thanks so much for your time.

    1 reply

    T
    Tesla DeLorean
    Graduate II
    September 3, 2024

    That the part is not actually authentic?

    Perhaps un-powered? Perhaps wrong pins?

    Does it present as a DFU "STM32 BOOT DEVICE" if connected via USB and BOOT0=HIGH ?

    L
    LucaLauroAuthor
    Visitor II
    September 4, 2024

    Thanks for your attention,

    it seems an original F411 to me, maybe i'm wrong, it seems to have UFQFPN48 package correct marking layout at least.

    https://www.st.com/resource/en/technical_note/tn1433-reference-device-marking-schematics-for-stm32-microcontrollers-and-microprocessors-stmicroelectronics.pdf

    When connected to the ST-link it is correctly powered and the ST-link reset pulse signal works.

    When connected via USB with DFU mode selected (BOOT0=HIGH) it's shown as "STM32 BOOTLOADER", a serial number is recognized too.

    LucaLauro_4-1725447288796.jpeg

    LucaLauro_1-1725447126165.jpeg

    LucaLauro_2-1725447194454.jpeg

    LucaLauro_3-1725447221118.png

     

    T
    Tesla DeLorean
    Graduate II
    September 4, 2024

    Ok, can you use the DFU method to program it?

    On the ST-LINK side there's either a power or connectivity issue. If this is an ST-LINK off a NUCLEO, make sure the local target is disconnected.

    Power the Black-Pill from same USB host as ST-LINK.

    3V3 to Pin 1 (of 20-pin header)

    GND to Pin 4 (or other EVEN GND pins)

    SWCLK to Pin 9

    SWDIO to Pin 7

    Double check connectivity too PA13/PA14

     

    Terms & ConditionsAccessibility statement