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

add support for STM32F412 #537

Closed
5 tasks done
Androude opened this issue Jan 2, 2017 · 2 comments · Fixed by #538
Closed
5 tasks done

add support for STM32F412 #537

Androude opened this issue Jan 2, 2017 · 2 comments · Fixed by #538

Comments

@Androude
Copy link
Contributor

Androude commented Jan 2, 2017

  • Programmer/board type: Stlink/v2-onboard
  • Operating system: Linux Ubuntu 16.04
  • Stlink tools version and/or git commit hash: st-util 1.2.0-155-gecc31f7-dirty
  • Stlink commandline tool name: st-flash, st-util
  • Target chip (and optional board): 32F412 (32F412GDISCOVERY)

The STM32F412 micro-controller line is not supported.

Output:

st-util 1.2.0-155-gecc31f7-dirty
2017-01-02T18:57:39 INFO /home/androude/apps/stlink/src/stlink/src/common.c: Loading device parameters....
2017-01-02T18:57:39 WARN /home/androude/apps/stlink/src/stlink/src/common.c: unknown chip id! 0x30006441

Expected/description:

I have fixed the issue locally by adding appropriate chipid-params structure and if-condition to flash loader. Using the 32F412GDISCOVERY device I successfully entered debug mode with gdb from eclipse.

I have never made a pull-request so fixing this issue could be the first one for me.

@xor-gate
Copy link
Member

xor-gate commented Jan 2, 2017

Best way is to fork the project, create a feature branch and the send a pull request:
https://help.github.com/articles/proposing-changes-to-your-work-with-pull-requests/

@xor-gate
Copy link
Member

xor-gate commented Jan 2, 2017

Thanks for your contribution with PR #538 !

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants