Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/stlink-org/stlink/pull/1084 below:

st-flash terminates unexpectedly when trying to read the chip · Issue #1084 · stlink-org/stlink · GitHub

Hi

The st-flash unexpectedly terminates when trying to read from the device in subject.

• Programmer/board type: st-link v2-clone
• Windows 7 sp1
• st-link 1.6.1
• st-flash
• Target chip (and board if applicable): [enter here] (e.g STM32F103C8T6)

st-info runs without problem:

C:\Users\user1>st-info --probe
Found 1 stlink programmers
 serial:     400030001000004150514e4e
 hla-serial: "\x40\x00\x30\x00\x10\x00\x00\x41\x50\x51\x4e\x4e"
 flash:      65536 (pagesize: 1024)
 sram:       20480
 chipid:     0x0410
 descr:      F1xx Medium-density

st-flash program returns with error:

C:\Users\user1>st-flash --debug --reset --area=option read > option_byte
2020-12-30T09:27:06 DEBUG common.c: *** looking up stlink version
2020-12-30T09:27:06 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-12-30T09:27:06 DEBUG common.c: stlink pid     = 0x3748
2020-12-30T09:27:06 DEBUG common.c: stlink version = 0x2
2020-12-30T09:27:06 DEBUG common.c: jtag version   = 0x1d
2020-12-30T09:27:06 DEBUG common.c: swim version   = 0x7
2020-12-30T09:27:06 DEBUG common.c: *** looking up stlink version
2020-12-30T09:27:06 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-12-30T09:27:06 DEBUG common.c: stlink pid     = 0x3748
2020-12-30T09:27:06 DEBUG common.c: stlink version = 0x2
2020-12-30T09:27:06 DEBUG common.c: jtag version   = 0x1d
2020-12-30T09:27:06 DEBUG common.c: swim version   = 0x7
2020-12-30T09:27:06 DEBUG common.c: stlink current mode: mass
2020-12-30T09:27:06 DEBUG usb.c: JTAG/SWD freq set to 0
2020-12-30T09:27:06 DEBUG common.c: *** set_swdclk ***
2020-12-30T09:27:06 DEBUG common.c: stlink current mode: mass
2020-12-30T09:27:06 DEBUG common.c: *** stlink_enter_swd_mode ***
2020-12-30T09:27:06 DEBUG common.c: *** stlink_jtag_reset ***
2020-12-30T09:27:06 DEBUG common.c: *** stlink_reset ***
2020-12-30T09:27:06 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-12-30T09:27:06 DEBUG common.c: Loading device parameters....
2020-12-30T09:27:06 DEBUG common.c: *** stlink_core_id ***
2020-12-30T09:27:06 DEBUG common.c: core_id = 0x1ba01477
2020-12-30T09:27:06 DEBUG common.c: *** stlink_read_debug32 20036410 is 0xe0042000
2020-12-30T09:27:06 DEBUG common.c: *** stlink_read_debug32 ffff0040 is 0x1ffff7e0
2020-12-30T09:27:06 INFO common.c:
C:\Users\user1>st-flash --version
v1.6.1

ST-Link drivers were installed from latest stmcubprogrammer v2.5.0.
The cubeprogrammer doesn't recognize the st-link so it wasn't possible to establish connection.
To workaround the problem programmer was uninstalled and drivers were deleted, and ST's ST-Link utility was installed (and its drivers too) then.
Installed st-link utility v4.6.0.0, driver version - v5.1.2.0. Nothing changed on st-flash side.
Note that the st-link utility could read the chip without problem. Didn't test write yet.

Previous versions of st-link (older than 1.6.1) were not tried.

Regards
/A

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4