2022-11-30 08:52 AM
I'm using the board SPIN3202. When but I can't flash. When acces to stlink info it displays
Found 1 stlink programmers
version: V2J39S27
serial: 0670FF545551677867033851
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0000
descr: unknown device
And when I wan't to connect to the board
st-flash read dummy.bin 0 0xFFFF
st-flash 1.7.0
2022-11-30T13:48:06 ERROR common.c: Can not connect to target. Please use 'connect under reset' and try again
Failed to connect to target
So I tried to connect to it using connect under reset it displays
st-flash --connect-under-reset
invalid command line
command line: ./st-flash [--debug] [--reset] [--connect-under-reset] [--hot-plug] [--opt] [--serial <serial>] [--format <format>] [--flash=<fsize>] [--freq=<KHz>] [--area=<area>] {read|write} [path] [addr] [size]
command line: ./st-flash [--debug] [--connect-under-reset] [--hot-plug] [--freq=<KHz>] [--serial <serial>] erase
command line: ./st-flash [--debug] [--freq=<KHz>] [--serial <serial>] reset
<addr>, <serial> and <size>: Use hex format.
<fsize>: Use decimal, octal or hex (prefix 0xXXX) format, optionally followed by k=KB, or m=MB (eg. --flash=128k)
<format>: Can be 'binary' (default) or 'ihex', although <addr> must be specified for binary format only.
<area>: Can be 'main' (default), 'system', 'otp', 'optcr', 'optcr1', 'option' or 'option_boot_add'
print tool version info: ./st-flash [--version]
example read option byte: ./st-flash --area=option read [path] [size]
example write option byte: ./st-flash --area=option write 0xXXXXXXXX
On selected targets:
example read boot_add option byte: ./st-flash --area=option_boot_add read
example write boot_add option byte: ./st-flash --area=option_boot_add write 0xXXXXXXXX
example read option control register byte: ./st-flash --area=optcr read
example write option control register1 byte: ./st-flash --area=optcr write 0xXXXXXXXX
example read option control register1 byte: ./st-flash --area=optcr1 read
example write option control register1 byte: ./st-flash --area=optcr1 write 0xXXXXXXXX
I used STM32Cube Programmer however can't connect to it and it says.
Can anyone help me, please?
2022-11-30 09:12 AM
Check the schematic.
Make sure the JP8 reset jumper is present, so that "connect under reset" mode might function.
And perhaps use JP9 to put the STM32 into the System Loader.
Use STM32 Cube Programmer, little support here for third-party tools.
2022-12-02 06:12 AM
Thanks! I did but still can’t connect it. I’ve used STM32 Cube Programmer but can’t connect to the board either it shows
11:01:23 : STM32CubeProgrammer API v2.11.0 | Linux-64Bits
11:01:24 : ST-LINK SN : 0670FF545551677867033851
11:01:24 : ST-LINK FW : V2J39M27
11:01:24 : Board : --
11:01:24 : Voltage : 1,93V
11:01:24 : Error: No STM32 target found!
Also I’ve noticed that as soon as I connect it LD1 blinks and then turn red and when I checked
STM32_Programmer_CLI -l usb appears
-------------------------------------------------------------------
STM32CubeProgrammer v2.11.0
-------------------------------------------------------------------
===== DFU Interface =====
No STM32 device in DFU mode connected
2024-02-07 10:59 PM
I had this problem after a couple of re-flashing my test-programm:
st-flash refused to connect
however
"st-info --probe" still worked
After a "st-flash --connect-under-reset erase" while keeping the boot0 = 0, st-flash worked again.
I presume, the bootloader vector got corrupted, and a full erase did the job.