Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[STM32G0B1RE / Nucleo G0B1RE]: False chip id reading #1359

Closed
SamyFrancelet opened this issue Nov 20, 2023 · 2 comments
Closed

[STM32G0B1RE / Nucleo G0B1RE]: False chip id reading #1359

SamyFrancelet opened this issue Nov 20, 2023 · 2 comments

Comments

@SamyFrancelet
Copy link

  • Programmer/board type: [Stlink V2-onboard]
  • Operating system and version: [Windows 10 / Windows 11 / Arch Linux]
  • Stlink tools version and/or git commit hash: [v1.7.0]
  • Stlink commandline tool name: [st-util / st-info / st-flash]
  • Target chip (and board if applicable): [STM32G0B1RE / nucleo_g0b1re]

Commandline output:

> st-util
st-util
2023-11-20T20:18:32 WARN common.c: unknown chip id! 0x90
2023-11-20T20:18:32 INFO gdb-server.c: Listening at *:4242...
> st-info --probe
Found 1 stlink programmers
  version:    V2J43S28
  serial:     066BFF485671664867182946
  flash:      0 (pagesize: 0)
  sram:       0
  chipid:     0x0090
> 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

@73jn
Copy link

73jn commented Nov 23, 2023

Hi, I have the same problem on a custom board with a STM32G0B0RE using an ST-Link V2, STLink tools version 1.7.0 on Windows 10 64-bits:

Found 1 stlink programmers
  version:    V2J43S7
  serial:     38FF6D06304E4B3029341243
  flash:      0 (pagesize: 0)
  sram:       0
  chipid:     0x0467
st-util
2023-11-23T15:16:12 WARN common.c: unknown chip id! 0x467
2023-11-23T15:16:12 INFO gdb-server.c: Listening at *:4242...

I don't have this problem on any other board. The chip id is correct but STLink tools version 1.7.0 doesn't recognise it.

Thanks for your support !

@Nightwalker-87
Copy link
Member

Fixed in #1140.

@Nightwalker-87 Nightwalker-87 self-assigned this Dec 23, 2023
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Dec 23, 2023
@Nightwalker-87 Nightwalker-87 changed the title STM32G0B1RE / nucleo_g0b1re: False chip id reading [STM32G0B1RE / Nucleo G0B1RE]: False chip id reading Dec 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants