20-11-2024, 01:46 PM
Ok, I managed to extract the error-code. But I was still testing with 5.20. I will install 5.30 and also try it. Maybe it fixes the problem as well.
But with 5.20, most of the times, eblink reports an error -102 which is probably INTERFACE_ERROR?
Do we have more methods available to check where this INTERFACE_ERROR stems from?(Verbose Levels/Logs?)
Is it maybe correlated to the occurences of STLINK_SWD_AP_WDATA_ERROR?
EBLink-Log with verbose 8:
I got it to run one time past that error, but then it hung somewhere later in the process.
But I could not reproduce that one time.
The 533 and the 56x/57x share the same manual, so yes, they both store the flash size in that register.
I confirmed it with the stm32Cubeprogrammer, the flash size is stored in that register.
But with 5.20, most of the times, eblink reports an error -102 which is probably INTERFACE_ERROR?
Do we have more methods available to check where this INTERFACE_ERROR stems from?(Verbose Levels/Logs?)
Is it maybe correlated to the occurences of STLINK_SWD_AP_WDATA_ERROR?
EBLink-Log with verbose 8:
Code:
"C:/Program Files (x86)/EBlink/win32/eblink.exe" -I stlink -S stm32 -P "C:/Program Files (x86)/EBlink/scripts" -G s,nc -v 8
EBlink version 5.20-[197] by Gerard Zagema
Using EB_SCRIPT_PATH = C:\Program Files (x86)\EBlink\scripts
Interface : STlink
Device found at bus 2:16
Interface USB# : 005100333133511635333335
Interface at 2:16 - <BUS>:<ADDR>
Interface type : STlink/V3
STlink Frmware : V3.J13.M4
Target voltage : 3.29V
Interface speed: 24000KHz
Try DAP_AP 0.
STlink open DAP_AP 0
Read CPU id on DAP_AP 0
STLINK_SWD_AP_WDATA_ERROR
STlink close DAP_AP 0
Try DAP_AP 1.
STlink open DAP_AP 1
Read CPU id on DAP_AP 1
CPU id found (0x410FD214)
Target selected: Cortex-M
Target detected: Cortex-M33 (r0p4) with FPv5_SP
HW breakpoints : 8
HW watchpoints : 4
Fault unwind : Active break (level 2)
Search script stm32.script in path: C:/Program Files (x86)/EBlink/scripts
Script found: stm32.script
STLINK_SWD_AP_WDATA_ERROR
STLINK_SWD_AP_WDATA_ERROR
STmicro device : 0x478
STmicro cpu : M33
STmicro device : 0x478
STmicro script : h5
Required script load: stmicro/stm32h5.script
Search script stmicro/stm32h5.script in path: C:/Program Files (x86)/EBlink/scripts
Script found: stmicro/stm32h5.script
STLINK_SWD_AP_WDATA_ERROR
unknown error -102 //I added this line in stm32.script main() to read the value of e.
Error: Can't access target device!
If reset is disabled ("dr" option), try with reset.STlink close DAP_AP 1I got it to run one time past that error, but then it hung somewhere later in the process.
But I could not reproduce that one time.
The 533 and the 56x/57x share the same manual, so yes, they both store the flash size in that register.
I confirmed it with the stm32Cubeprogrammer, the flash size is stored in that register.