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.

Sign up for GitHub

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

Jump to bottom

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
Assignees
@Nightwalker-87
Labels
programmer/STLINK/V3 V3SET / V3MODS / V3MINI / V3MINIE / V3E / V3EC question status/resolved status/resolved-verified target/stm32u5 target/stm32wl
Projects
Release v1.8.0
Milestone
v1.8.0

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 Nightwalker-87 added this to the v1.8.0 milestone Apr 6, 2023
@Nightwalker-87 Nightwalker-87 self-assigned this Apr 6, 2023
@Nightwalker-87 Nightwalker-87 added this to To do in Release v1.8.0 via automation Apr 6, 2023
@Nightwalker-87 Nightwalker-87 added the programmer/STLINK/V3 V3SET / V3MODS / V3MINI / V3MINIE / V3E / V3EC label Apr 6, 2023
@Nightwalker-87
Copy link
Member

Nightwalker-87 commented Apr 6, 2023 •
edited

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.

Release v1.8.0 automation moved this from To do to Done Apr 6, 2023
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 6, 2023
@Nightwalker-87 Nightwalker-87 linked a pull request Apr 6, 2023 that will close this issue
Initial support for STM32 L5 & U5 devices and minor changes #1300
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Nightwalker-87 Nightwalker-87

Labels
programmer/STLINK/V3 V3SET / V3MODS / V3MINI / V3MINIE / V3E / V3EC question status/resolved status/resolved-verified target/stm32u5 target/stm32wl
Projects
No open projects
Release v1.8.0
Done
Release v1.8.0
Status: Done
Milestone
v1.8.0
Development

Successfully merging a pull request may close this issue.

Initial support for STM32 L5 & U5 devices and minor changes stlink-org/stlink
2 participants
@Nightwalker-87 @victor-dryad