STM32 not identified

[bmelo]

idVendor = 0x0483
idProduct = 0x3752

You mean debug stlink code?


Sent from ProtonMail, Swiss-based encrypted email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, 16 de March de 2020 às 19:18, Andrew Stevenson <andrew at ugh.net.au> wrote:

>
>
> > On 16. Mar 2020, at 22:01, bmelo bmelo at protonmail.com wrote:
> >
> > > Are you sure its permission problem? Doesn’t st-util search via the USB VID/PID? Maybe running in verbose mode might give some idea of where it's failing. Do you see your device when you rub usbconfig? Do the VID/PID match whatever st-util is expecting?
> >
> > Yes, usbconfig see the device: ugen0.6: <STMicroelectronics STM32 STLink> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (300mA)
> > st-util's verbose mode is useless, never returns verbosed output :P
>
> Looking at the source it is using libusb and searching for devices with VID == 0x0483 and PID == 0x3748 or 0x374b. Usbconfig dump_device_desc will show you the details of your device.
>
> If they do match I’m not sure where you would go from there without debugging the code but I think the permissions of your serial devices is a red herring.
>
> Andrew