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

[STM32F4Discovery]: unknown chip id! 0x413 #1241

Closed
6 tasks done
Catherinecyj opened this issue Apr 9, 2022 · 2 comments
Closed
6 tasks done

[STM32F4Discovery]: unknown chip id! 0x413 #1241

Catherinecyj opened this issue Apr 9, 2022 · 2 comments

Comments

@Catherinecyj
Copy link

Catherinecyj commented Apr 9, 2022

  • Programmer/board type: Stlink /V2-onboard
  • Programmer firmware version: V2J37S26
  • Operating system: Linux (Ubuntu)
  • Stlink tools version and/or git commit hash: 1.7.0-186-gc4762e6
  • Stlink commandline tool name: st-flash, st-info
  • Target chip (and optional board): STM32F407VGT6U (STM32F4Discovery)

Commandline output:

st-flash write testvectors.bin 0x8000000
st-flash 1.7.0-186-gc4762e6
/usr/local/stlink/chip: No such file or directory
2022-04-09 WARN common.c: unknown chip id! 0x413
Failed to connect to target

Commandline output:

st-info --probe
/usr/local/stlink/chip: No such file or directory
Found 1 stlink programmers
    version: V2J37S26
    serial:    066DFF485157808667044350
    flash:     0
    sram:     0
    chipid:   0x413

Expected/description:
It seems like the device ID is 0x413 exactly, for I tried to use STM32 Cube Programmer and can recognized the device and the Device ID shown:
image
Also can program the .bin file successfully.

Catherine

@bsalha1
Copy link

bsalha1 commented Nov 22, 2022

I am also getting this on my STM32F407VET6

@Nightwalker-87
Copy link
Member

This is not a chip-specific issue.
The output message /usr/local/stlink/chip: No such file or directory indicates a compilation bug regarding the installation path of the .chip configuration files used to detect MCU devices.

This bug has been fixed in commit f93adb9.
The correct installation path is /usr/share/stlink/chips.
In order to resolve this, please clean-up your installation with make uninstall, then make clean, preferably check out the latest commit on the develop branch and proceed with make install.

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