21-11-2024, 01:42 PM
Yes, I already used printf's to track it down to the read on 0x08fff80c. I also didn't identify any relevant errata.
But today, I cant reproduce it to fail anymore like it did yesterday...
To me, it seems like an error depending on some weird interaction.
I don't think you need to put extra effort into getting your hands on such a device, it will probably be very difficult to reproduce this on your end.
CubeProgrammer was always getting somehow through. I have not tried CubeIDE.
I will try to reproduce the error and try to get my hands on a wireshark protocol of the error.
But until I think we can regard this issue as solved until I am able to reproduce it.
The new scripts look good and the remaining issue is probably not an issue with the scripts.
But today, I cant reproduce it to fail anymore like it did yesterday...
To me, it seems like an error depending on some weird interaction.
I don't think you need to put extra effort into getting your hands on such a device, it will probably be very difficult to reproduce this on your end.
CubeProgrammer was always getting somehow through. I have not tried CubeIDE.
I will try to reproduce the error and try to get my hands on a wireshark protocol of the error.
But until I think we can regard this issue as solved until I am able to reproduce it.
The new scripts look good and the remaining issue is probably not an issue with the scripts.