STM32F407ZGT6 / STM32F042K6: unknown chip id - RESET 0x5fa0004

[goog]

When submitting a feature request, try to reuse the list and add/remove what is appropriate.
Place a X between the brackets [X] to mark the list item.

• Programmer/board type: Stlink/v2
• Programmer firmware version: e.g STSW-LINK007 2.27.15
• Operating system: Linux
• Stlink tools version and/or git commit hash: v1.5.1-21-gc6836b4
• Stlink commandline tool name: st-flash

ubuntu12.04 64bit STM32F407ZGT6

A as-detailed description possible of the problem with debug output when available.

Output:

cheng@ubuntu:~/stlink/build/Release$ ./st-flash write /home/cheng/stm32f4/arm-rtems4.11/c/stm32f4/testsuites/samples/hello/hello.bin 0x8000000
st-flash 1.5.1-21-gc6836b4
2019-04-07T23:22:21 INFO common.c: Loading device parameters....
2019-04-07T23:22:21 WARN common.c: unknown chip id! 0x5fa0004

[set321go]

I'm seeing the same issue when trying to program STM32F042K6, which was talking to st-info --chipid initially. I do notice that that 0x5fa0004 is the reset command.

Edit:
Here is the output of of st-util --verbose=99

st-util 1.5.1
2019-05-26T11:56:47 DEBUG common.c: stlink current mode: debug (jtag or swd)
2019-05-26T11:56:47 DEBUG common.c: stlink current mode: debug (jtag or swd)
2019-05-26T11:56:47 DEBUG common.c: *** looking up stlink version
2019-05-26T11:56:47 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2019-05-26T11:56:47 DEBUG common.c: stlink pid     = 0x3748
2019-05-26T11:56:47 DEBUG common.c: stlink version = 0x2
2019-05-26T11:56:47 DEBUG common.c: jtag version   = 0x1f
2019-05-26T11:56:47 DEBUG common.c: swim version   = 0x7
2019-05-26T11:56:47 DEBUG common.c: *** stlink_jtag_reset ***
2019-05-26T11:56:47 DEBUG common.c: *** stlink_reset ***
2019-05-26T11:56:47 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2019-05-26T11:56:47 INFO common.c: Loading device parameters....
2019-05-26T11:56:47 DEBUG common.c: *** stlink_core_id ***
2019-05-26T11:56:47 DEBUG common.c: core_id = 0x00000000
2019-05-26T11:56:47 DEBUG common.c: *** stlink_read_debug32 5fa0004 is 0xe0042000
2019-05-26T11:56:47 WARN common.c: unknown chip id! 0x5fa0004
2019-05-26T11:56:47 DEBUG common.c: *** set_swdclk ***
2019-05-26T11:56:47 DEBUG common.c: *** stlink_close ***

Update: Turns out it was my fault, i had two issues, the debug cables were not connected securely & the swdio was on the wrong pin

[Nightwalker-87]

Resolved by either #715 (swapped SWDIO and SWCLK lines) or #832 (firmware).