Date: Mon, 16 Mar 2020 21:01:47 +0000 From: bmelo <bmelo@protonmail.com> To: Andrew Stevenson <andrew@ugh.net.au> Cc: "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org> Subject: Re: STM32 not identified Message-ID: <BfjqeQjiK9TyzWlepviEZYd2hxQJJpMkaxgnFyedZrJvSNnCNc27CCXWeUiv6SpnZMXgHd5OpAIIuMYaj9YEJmosVhhbK4091vD9H6ELZsw=@protonmail.com> In-Reply-To: <4A28D043-960F-465F-AC1A-9B6AD839783E@ugh.net.au> References: <bCyCGMfT-ROSVe2TXJJdJeOI3UkecbyDDrz8CTIcXPAoZwyKvYS4ZkgaQxMiXgvT7VNOTARJ0PLmbcvLU_WNxPPd578NDl0ZyZ7h_m8xSb0=@protonmail.com> <4A28D043-960F-465F-AC1A-9B6AD839783E@ugh.net.au>
index | next in thread | previous in thread | raw e-mail
> 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 :Phelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BfjqeQjiK9TyzWlepviEZYd2hxQJJpMkaxgnFyedZrJvSNnCNc27CCXWeUiv6SpnZMXgHd5OpAIIuMYaj9YEJmosVhhbK4091vD9H6ELZsw=>