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

Sudden unknown chip id for stm32f103 #568

Open
tcurdt opened this Issue Mar 13, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@tcurdt

tcurdt commented Mar 13, 2017

  • Programmer/board type: Stlink/v2
  • Programmer firmware version: e.g STSW-LINK007 2.27.15
  • Operating system: macOS 10.12.3
  • Stlink tools version: v1.3.1
  • Stlink commandline tool name: st-flash and st-util
  • Target chip: generic STM32F103C8

I was flashing without problems, suddenly I am getting "unknown chip id".

Output:

$ st-flash write main.bin 0x8000000
st-flash 1.3.1
2017-03-13T01:22:48 INFO src/common.c: Loading device parameters....
2017-03-13T01:22:48 WARN src/common.c: unknown chip id! 0xe0042000

Did I somehow fry my board? Or what does that mean?

@tcurdt

This comment has been minimized.

tcurdt commented Mar 13, 2017

This happens on an erase:

$ st-flash erase
st-flash 1.3.1
2017-03-13T01:49:32 INFO src/common.c: Loading device parameters....
2017-03-13T01:49:32 WARN src/common.c: unknown chip id! 0xe0042000

When I hold the reset button while calling the erase I get:

$ st-flash erase
st-flash 1.3.1
2017-03-13T01:49:40 INFO src/common.c: Loading device parameters....
2017-03-13T01:49:40 INFO src/common.c: Device connected is: F1 Medium-density device, id 0x20036410
2017-03-13T01:49:40 INFO src/common.c: SRAM size: 0x5000 bytes (20 KiB), Flash: 0 bytes (0 KiB) in pages of 1024 bytes
Mass erasing

0 bytes?

@tcurdt

This comment has been minimized.

tcurdt commented Mar 13, 2017

Setting boot0 to 1, then st-flash erase, then setting it back to 0 and all was working again.
I am fine to close the issue - but still would love to hear how/why that happened.

@xor-gate xor-gate changed the title from sudden unknown chip id to Sudden unknown chip id for stm32f103 Mar 15, 2017

@iglooom

This comment has been minimized.

iglooom commented Apr 9, 2017

@tcurdt are you using SWDIO/SDCLK as GPIO in your firmware? It may be like #577

@tcurdt

This comment has been minimized.

tcurdt commented Apr 9, 2017

@iglooom not by choice at least. I would need to check if any of the GPIO pins I am using are somehow connected to the SWDIO/SDCLK but according to this http://wiki.stm32duino.com/index.php?title=Blue_Pill they are not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment