2018-08-17 07:44 AM
I Previously used V4.0.0 (At least I think so) but sometime ago upgraded to V4.2.0. Now every second time I read a .hex from disk it crashes (having programmed the chip between file openings). The .hex is for a stm32H7 (doesn´t know if it makes a difference). I´m using Windows 7 64 bits. How can I report this back to ST?
Solved! Go to Solution.
2019-01-04 08:10 AM
Hello @Daniel Fernandes ,
The reading and flashing of .Hex file with STM32H7 is fixed using ST-Link Utility v 4.3.0 .
Thanks,
Imen.
2018-08-17 08:32 AM
@STOne-32 @Imen DAHMEN could someone create an incident report and get the offending .HEX files to the respective teams.
Have you tried the Cube STM Programmer? The Utilities seems to have been deprecated in favour of the new tools.
https://www.st.com/en/development-tools/stm32cubeprog.html
2018-08-17 09:21 AM
Hello @Daniel Fernandes ,
We will raise and check this issue internally.
I recommend you, as Clive said, to use the new STM32CubeProgrammer software tool.
With Regards,
Imen
2019-01-04 08:10 AM
Hello @Daniel Fernandes ,
The reading and flashing of .Hex file with STM32H7 is fixed using ST-Link Utility v 4.3.0 .
Thanks,
Imen.