STLink Gnuk is not getting detected

Abhijith PA abhijith at disroot.org
Thu Oct 17 10:10:34 CEST 2024


Hi NIIBE,

Thank you for looking in to my issues.

On 17/10/24 10:28 AM, NIIBE Yutaka wrote:
> Hello,
> 
> Abhijith PA wrote:
> > But after flashing, system is not recognizing gnuk usb device. May be
> > 1 in 10 times, it get recognized, but most of the time its not.
> 
> Firstly, please check the physical hardware for USB DP pull up.

Sorry, I have no experience with inspecting physical hardware and identifying
components. My device look exactly like this.

https://raw.githubusercontent.com/Zelmoghazy/st-link-v2-clone/refs/heads/main/Images/A611cf33089f74830b00823becb2412c8A.webp

Perhaps can you point to any tutorial on how to do it.

> There are multiple ST-Link implementations; There would be more for
> ST-Link clones.
> 
> 
> Did you configure with --target=ST_DONGLE (it means the ST-Link V2-1 in
> Nucleo F103)?

Yes. I configured with --target=ST_DONGLE

> Secondly.... another problem would be... I wonder if the chip on your
> board is STM32F103 or one of its variants.  If its not STM32F103, sleep
> support of the chip would have different behavior.  (I encounter a
> symptom of USB enumeration sometime works, but not all the times, for
> CH32V203 for sleep support of chip.)  If it might be the case, please
> modify the function chx_idle in
> 
> 	chopstx-STABLE-2/mcu/chx-stm32f103.c
> 
> into:
> 
> ==========================
> void __attribute__((naked))
> chx_idle (void)
> {
>   for (;;)
>     ;
> }
> ==========================
> 
> That is, no use of sleep support of the chip.  Try and see if things
> improved.

I tried this and unfortunely there isn't any difference.

I could say its one of 'STM32F103' by looking at
https://github.com/Zelmoghazy/st-link-v2-clone . I have exactly
same inscription on MCU as the above image 'MH2103A CBT6'


--abhijith



More information about the Gnuk-users mailing list