When I try to target->connect in ST Link Utility I have an error ''unknown device'' with disco L4, disco F7 and nucleo L4. With nucleo L0, the connection is good, but I have the message ''Device family : unknown device''. With disco F0, disco F3 and disco F4 it's OK. The ...
2、解决方法：（1）首先安装"STM32 ST-LINK Utility"（见附件） 安装完毕后，建议使用管理员身份运...
使用ST-link Utility烧录引导程序出错问题描述:[tr]我的板子是STM32f427的板,我想在里面烧录bin文件!我以前烧进去过一次.后来那个bin文件不行.我现在想烧别的bin文件,可是我不管点什么我都出现一个Unknown device ID!;然而我选择的是Hot Plug,然我现在Normal模式我就出现Can't halt the core出现这个!还有一个模...
网上有说用按复位键后点setting 或者用st-link utility软件点连接的。两种我都试了。依旧不然。重新换...
Another case:Programming STM32F103ZET6 or STM32F105VCT6 for the VERY first time (using ST-LINK utility) Experiencing some issue with GD32F105RBT6. I was able to flash once, but I get unknown chip id! 0x4278b7 ever since then. ...
Error in initializing ST-Link device Reason:Unknown MCU found on target' On the other hand, when trying the ST-Link utility, when running from 'Normal' or 'Connect Under Reset' mode, the utility pops a message saying stating: '14:53:37 : Can not connect to target!
ST-LINK Utility says: Device ID:0x430 Device flash Size : 1 Mbytes Device family :STM32F10xx XL-density Member xor-gate commented Feb 15, 2019 • edited I think the GD32 microcontrollers are clones of real ST Microelectronics ones. It is nice to support them but we must not break...
The device should not be read as an unknown device when executingst-info --probe, and there should not be a gdb-server error when runningst-util. However, the board is able to be detected when running lsusb. Bus 001 Device 013: ID 0483:3744 STMicroelectronics ST-LINK/V1 ...
- STM32 ST-LINK Utility (Unknown version)- ST-LINK/V2- STM32F030C6T6- Windows 7 32bit But in the following environment, I can not connect with ST - LINK Utility. - STM32 ST-LINK Utility (latest version)- ST-LINK/V2 ISOL- STM32F030C6T6- Windows 10 64bit...
st-util 2020-08-21T10:51:22 WARN common.c: unknown chip id! 0x5fa0004 st-info --chipid 0x0004 ST-Link Utility correctly identify the chipid for both (STM32G070KBT6 / STM32G071KBT6) micro-controllers: Device ID:0x460 But st-util / st-info reports the wrong chipid: st-info ...