Skip site navigation (1)Skip section navigation (2) 
Date:      Tue, 17 Mar 2020 07:22:21 +0100
From:      Andrew Stevenson <andrew@ugh.net.au>
To:        bmelo <bmelo@protonmail.com>
Cc:        "freebsd-embedded@freebsd.org" <freebsd-embedded@freebsd.org>
Subject:   Re: STM32 not identified
Message-ID:  <48199592-44DA-424E-A181-6E8761485598@ugh.net.au>
In-Reply-To: <QwJZLRGmm-vtlHgrmPGcFwE22tEh0UTXAotqoy5zrTnf6dIa-eis7RG4zXklfnop082ZU3yt2pmXz0Rcg6J-cRXoTWOSa2z6KaJkseagWps=@protonmail.com>
References:  <QwJZLRGmm-vtlHgrmPGcFwE22tEh0UTXAotqoy5zrTnf6dIa-eis7RG4zXklfnop082ZU3yt2pmXz0Rcg6J-cRXoTWOSa2z6KaJkseagWps=@protonmail.com>
index | next in thread | previous in thread | raw e-mail 



> On 16. Mar 2020, at 23:42, bmelo <bmelo@protonmail.com> wrote:
> 
> idVendor = 0x0483
> idProduct = 0x3752
> 
> You mean debug stlink code?

I do but as your PID doesn’t match I theorise you might have a new device that the code isn’t been updated for yet? You could check there is no newer version upstream or just hack in another ’|| pid == 0x3752’ and see if it magically works. 

HTH

Andrew
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48199592-44DA-424E-A181-6E8761485598>