-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boards/frdm: fix flashing from invalid state #12261
Conversation
When flashing some applications the flasher sometimes gets stuck which prevents flashing after. It may be from a specific firmware or operation but do not have one yet. Connect with reset asserted fix flashing from this state.
I do not see any reason why the added command could affect flashing or resetting the device, At worst it wouldn't change the base behavior. I do not have the hardware(
There was one before right? Maybe you can provide a patch that reverts the change that fixed that app? If I remember correctly it was a driver test application, but I don't remember which one... If it is not reproducible I will ACK once I test it isn't breaking anything (The only reason I do not ACK right away is that in #12158 there were some issues). |
You can put a kinetis board into an unflashable state by using #11789 and calling |
@fjmolinas no the @benemorius oh nice I will try it. Does this PR fixes flashing for you? and which board are you using. |
I can confirm that definitely I do need But I don't have a board that can flash using |
Tested on OPENOCD_RESET_USE_CONNECT_ASSERT_SRST=0 make -C tests/periph_pm BOARD=frdm-k64f flash -j3
OPENOCD_RESET_USE_CONNECT_ASSERT_SRST=1 make -C tests/periph_pm BOARD=frdm-k64f flash -j3
NOTE: my diff
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to test this fixes the issue for frdm-kw41z
and frdm-k64f
. Changes are good ACK.
Thanks @benemorius for your feedback and giving the perfect test for this. |
I also cross-checked locally with |
Contribution description
When flashing some applications the flasher sometimes gets stuck which
prevents flashing after.
It may be from a specific firmware or operation but do not have one yet.
Connect with reset asserted fix flashing from this state.
Testing procedure
I do not have an application that cannot flash anymore to really show the fix.
But I have been using a fix like this for several month and had no flashing issue in my test machine.
Flashing boards that use
common/frdm
sofrdm-kw41z
and other similar boards,frdm-k22f
andfrdm-k64f
keep flashing correctly. (theThey now use
connect_assert_srst
when flashing instead ofconnect_deassert_srst
as it was in `masterPR:
srst_only separate srst_nogate srst_open_drain connect_assert_srst
master
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Both appear with this PR as the
deassert
is the value in the configuration which is then changed by command line option.frdm-k64f
frdm-kw41z
Issues/PRs references