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

Are chip IDs 482 and 497 known and should be supported? #1301

Closed
victor-dryad opened this issue Apr 6, 2023 · 1 comment · Fixed by #1300
Closed

Are chip IDs 482 and 497 known and should be supported? #1301

victor-dryad opened this issue Apr 6, 2023 · 1 comment · Fixed by #1300

Comments

@victor-dryad
Copy link

Found 2 stlink programmers
1.
version: V3J12S1
serial: 003000215553500920393256
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0482
2.
version: V3J12S1
serial: 004C00293331510833323639
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0497

For example:

$ st-flash --area=optcr1 read
st-flash 1.7.0
2023-04-06T16:52:05 INFO usb.c: Unable to match requested speed 1800 kHz, using 1000 kHz
2023-04-06T16:52:05 WARN common.c: unknown chip id! 0x497
Failed to connect to target

@Nightwalker-87
Copy link
Member

Nightwalker-87 commented Apr 6, 2023

Three steps to answer your question:

  1. Please follow the guidelines and make use of prepared issue templates next time.
  2. You need to make use of the development branch.
  3. Refer to header stm32.h to check for supported device IDs. --> Yes both are supported.

@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 6, 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

Successfully merging a pull request may close this issue.

2 participants