STM32L452: st-flash can flash once then fail once then flash once #1054
Comments
joseph-cb
changed the title
|
Use a different Rpi, another dev board. Apply fix of #981. Observed the same symptom. Fail once then succeed once, forever. |
|
I still need the fix of #981 for this to work; i.e. BOTH #981 fix AND |
Nightwalker-87
changed the title
Nightwalker-87
changed the title
|
I declared victory too early. The flash tool always says " Flash written and verified! jolly good!" after I added On the other hand, I git clone openocd source tree and compiled my openocd. I can use it to reliably flash my L452RE openocd does not give error message and I check behavior after flashing with openocd. My L452RE is reflashed and boot up every time. |
|
The observation that |
|
I think I'm running into the same problem on my F429ZI Nucleo using the on board ST Link, running 4bfaab0. One attempt to flash will output and the next will output However, the first attempt did actually successfully flash and reset. On the second attempt, the STM32 resets and begins to execute the new code, but for some reason crashes after a few lines. I've tested this with this bash line |
|
@joseph-cb |
|
I tested it on an STM32F072 which is having the same issue. Every other time I try to flash, I get this: I can test it on the F429 as well if you want. |
|
Sorry, ignore my last comment. Adding |
|
@sambazley Yes, I test it with |
Nightwalker-87
moved this from Review in progress
to Reviewer approved
in Release v1.7.0
Thank you for giving feedback to the stlink project.
NOTICE: Please read and follow instructions in #906 before submitting a ticket. This feature request will be deleted without notice when not enough information is provided! So please ensure that all fields are filled out.
In order to allow developers and other contributors to isolate and target your respective issue, please take some time to fill out each of the following items appropriate to your specific problem:
st-info,st-flash,st-util)Futher we kindly ask you to describe the detected problem as detailed as possible and to add debug output if available, by using the following template:
Commandline-Output:
I run into the error shown in #981 I follow the solution by increasing WAIT_ROUNDS to extremely large value.
Now, I find that flashing will work one time, fail next, work again, fail again. i.e. alternate between succeeding and failing. This strange behavior is very consistent.
The following screenshot captures one success followed by a failure followed by another success. Same linux binary and same target STM32 binary were used in these three invocations.
Furthermore, I use
./st-utiland a remote gdb to flash the elf file produced by the same code.st-util+ remote gdb can consistently flash my binary reliably. The binaries (elf and bin) were compiled using STM32CubeIDE 1.4.0. I also tested Release build and Debug build. Same strange behavior is observed.What will be the next step for debugging
st-flash? I can usest-utilin the meantime, but we will needst-flashwhen we hit production.Expected/description:
short description of the expected valueThank you for your support.
The stlink project maintainers
The text was updated successfully, but these errors were encountered: