F4DISCOVERY FAIL TO CONNECT

[E77TK]

Hi,

i have problem with f4discovery at connection start.
failure message was:

Open On-Chip Debugger 0.10.0 (2020-05-03) [https://github.com/sysprogs/openocd]

Licensed under GNU GPL v2

libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

WARNING: interface/stlink-v2.cfg is deprecated, please switch to interface/stlink.cfg

Info : auto-selecting first available session transport “hla_swd”. To override use ‘transport select <transport>’.

Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD

Info : clock speed 2000 kHz

Info : STLINK v2 JTAG v14 API v2 SWIM v0 VID 0x0483 PID 0x3748

Info : using stlink api v2

Info : Target voltage: 2.911335

Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints

Info : Listening on port 52598 for gdb connections

target halted due to debug-request, current mode: Thread

xPSR: 0x01000000 pc: 0x0800422c msp: 0x20000c80

SysprogsLogicAnalyzer_ReadyToConnect

Connecting to port 52598…

Successfully connected to OpenOCD.

——————————

Unexpected device type. Expected 0x00000413, read 0x00000411. Please double-check that you have selected the board type correctly. If you have several boards connected, please ensure you select the correct one.

…

Is there any solution for this connection problem??

 

Thanks, Haris

[support]

Hi,

It looks like your board revision is not supported. Please try using another board.

[E77TK]

Hi,

i have two but both are the same revision, is there any solution or forget about 🙁

[support]

Sorry, if a board revision is unsupported, Analyzer2Go will not work with it.

[Author]

Posts