2018-05-14 04:41 AM
I am able to connect to the target:
14:35:49 : ST-LINK SN : 0674FF3836314B3457144034
14:35:49 : ST-LINK Firmware version : V2J29M18
14:35:49 : Connected via SWD.
14:35:49 : SWD Frequency = 4,0 MHz.
14:35:49 : Connection mode : Normal.
14:35:50 : Device ID:0x450
14:35:50 : Device flash Size : 2MBytes
14:35:50 : Device family :STM32H7xx
But when programming, it crashes with an error 'STM32 ST-LINK utility MFC Application has stopped working' and returned error code is equal to1073740940
.Please find hex file attached. It works when programming directly from KEIL using ST-link. Do you know what is going on here?
#hex #st-link-utility2018-05-15 02:54 AM
Hi
Zickus.Rimantas
,This issueis reported to our team for check , I will come back to you as soon as I have a feedback.
-Nesrine-
2018-05-23 11:10 AM
Hi Nesrine,
Is there any progress regarding the issue? It is quite urgent for us.
2018-05-23 11:18 AM
Use the STM32 Cube Programming Tool, the ST-LINK Utilities have been deprecated.
http://www.st.com/en/development-tools/stm32cubeprog.html
2018-05-23 11:33 AM
As long as cube version does not support all features that ST-LINK Utility has, I can not migrate to it. I expect that at least versions with bug fixes must be released until cube programming tool fully replaces the old one.
2018-05-23 11:44 AM
Don't get your hopes up, if you have urgent/critical paths don't tie them to a monolith you have no control over.
When failure is not an option, you come up with alternatives.
You could certainly determine if the Cube Prog will work with your .HEX files, and make some determination about what the Utilities don't like about yours. You could use .BIN files and see if that modifies the behaviour or success. Anything you can do to focus on the exact modes of failure/success will likely expedite a fix on ST's end.
2018-05-24 04:08 AM
It is the same with bin files. I attached hex file so ST should be able to reproduce the bug. I think it is more than enough.
2018-10-15 02:18 AM
Hello,
This issue of the .hex will be fixed in the coming release of ST-Link Utility v 4.3.0.
Kind Regards,
Imen.