You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> st-flash erase
st-flash 1.7.0
2023-11-20T20:17:44 WARN common.c: unknown chip id! 0x90
Failed to connect to target
Target information from STM32CubeProgrammer (on Windows 10):
20:19:37 : ST-LINK SN : 066BFF485671664867182946
20:19:37 : ST-LINK FW : V2J43M28
20:19:37 : Board : NUCLEO-G0B1RE
20:19:37 : Voltage : 3.24V
20:19:37 : SWD freq : 4000 KHz
20:19:37 : Connect mode: Normal
20:19:37 : Reset mode : Software reset
20:19:37 : Device ID : 0x467
20:19:37 : Revision ID : Rev A
Description:
The chip id is incorrect.
This problem only happens on this nucleo_g0b1 board, I have other boards (F411RE / LoRaWAN boards, etc..) and the chip id is read properly. I unfortunately doesn't have access to other G0 boards to probe if the problem happens on other Cortex-M0+ cores.
I've tested this only with the lastest release (v1.7.0), on multiple machines (Windows 10/11, Arch Linux) and got the same problem everywhere.
PR #1126 doesn't seem to fix my issue as it should be the v1.7.0 Release
I've ensured that the STLink is properly updated, and I can also program the board properly using STM32CubeProgrammer or STM32CubeIDE.
Is there anything else that I can do to help solve this issue ?
Thanks for your support,
/samy
The text was updated successfully, but these errors were encountered:
Commandline output:
Target information from STM32CubeProgrammer (on Windows 10):
Description:
The chip id is incorrect.
This problem only happens on this nucleo_g0b1 board, I have other boards (F411RE / LoRaWAN boards, etc..) and the chip id is read properly. I unfortunately doesn't have access to other G0 boards to probe if the problem happens on other Cortex-M0+ cores.
I've tested this only with the lastest release (v1.7.0), on multiple machines (Windows 10/11, Arch Linux) and got the same problem everywhere.
PR #1126 doesn't seem to fix my issue as it should be the v1.7.0 Release
I've ensured that the STLink is properly updated, and I can also program the board properly using STM32CubeProgrammer or STM32CubeIDE.
Is there anything else that I can do to help solve this issue ?
Thanks for your support,
/samy
The text was updated successfully, but these errors were encountered: