On Mon, Jul 27, 2020 at 12:03:12PM +0200,
b...@elektron.ikp.physik.tu-darmstadt.de wrote:
> > I'm surprised I get no constructive feedback on this ticket. Now that
> > it's trivial to try a firmware with patched-out IDCODE check why isn't
> > anybody trying that?
>
> This is caused probably by di
Paul Fertser writes:
> On Mon, Jul 27, 2020 at 11:21:00AM +0200,
> b...@elektron.ikp.physik.tu-darmstadt.de wrote:
> > Rejecting non-ST MCU probably has also a deeper impact. The need to
> > read the MCUID! This has often problems when in sleep or even when in
> > reset. Even with stprog, STLINKV3
On Mon, Jul 27, 2020 at 11:21:00AM +0200,
b...@elektron.ikp.physik.tu-darmstadt.de wrote:
> Rejecting non-ST MCU probably has also a deeper impact. The need to
> read the MCUID! This has often problems when in sleep or even when in
> reset. Even with stprog, STLINKV3 often does to to a board the
>
Paul Fertser via OpenOCD-devel writes:
> ---
>
> [tickets:#275] ST-Link v3 refuses to work with non-ST targets, RE help needed
>
> Status: new
> Milestone: 0.9.0
> Created: Fri Jul 24, 2020 04:26 PM UTC by Paul Fertser
>
---
** [tickets:#275] ST-Link v3 refuses to work with non-ST targets, RE help
needed**
**Status:** new
**Milestone:** 0.9.0
**Created:** Fri Jul 24, 2020 04:26 PM UTC by Paul Fertser
**Last Updated:** Fri Jul 24, 2020 04:26 PM UTC
**Owner:** Paul Fertser
For the reasons yet to be discovered
