Add temporary workaround for the reboot issues #564
+176
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
huaqianli
force-pushed
the
lee/upstream-qspi-workaround
branch
from
126ea5e
to
8c63326
Compare
BaochengSu
reviewed
Oct 22, 2024
| + mmc = find_mmc_device(i); | ||
| + if (mmc && !mmc_init(mmc)) { | ||
| + mmc_available = 1; | ||
| + printf("Lee: mmc %d is availbe!\n", i); |
There was a problem hiding this comment.
Rather a debug left-over 😉
There was a problem hiding this comment.
This is a temporary workaround, so I want to have this log for potential debugging.
After approximately 2 months of operation, the device may fail to check the QSPI idle status. Here is the strange phenomenon: The QSPI remains busy when checking the idle status, becoming idle once stop checking. This commit provides a temporary workaround to bypass the QSPI idle checking. TODO: Implement a permanent solution for QSPI idle checking issue. Related to #440. Signed-off-by: Li Hua Qian <[email protected]>
huaqianli
force-pushed
the
lee/upstream-qspi-workaround
branch
from
8c63326
to
ce45f46
Compare
jan-kiszka
reviewed
Oct 22, 2024
| After approximately 2 months of operation, the device may fail to detect | ||
| the eMMC when rebooting. This commit provides a temporary workaround to | ||
| reset the eMMC if detection issues occur. | ||
|
|
There was a problem hiding this comment.
Is this issue likely related to how the board is wiring the eMMC, or is this a generic problem that should be addressed at eMMC driver level in U-Boot?
There was a problem hiding this comment.
"For backward compatibility reason, RST_n signal is temporary disabled in device by default." - eMMC standard.
Therefore, this feature is not mandatory. If the workaround proves effective, we'll consider incorporating it into the eMMC driver.
After approximately 2 months of operation, the device may fail to detect the eMMC when rebooting. This commit provides a temporary workaround to reset the eMMC if detection issues occur. TODO: Implement a permanent solution for eMMC detection issues. Related to #440. Signed-off-by: Li Hua Qian <[email protected]>
huaqianli
force-pushed
the
lee/upstream-qspi-workaround
branch
from
ce45f46
to
84dc8df
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
u-boot-iot2050: Add temporary workaround for the QSPI issue:
After approximately 2 months of operation, the device may fail to check
the QSPI idle status. Here is the strange phenomenon: The QSPI remains
busy when checking the idle status, becoming idle once stop checking.
Providing a temporary workaround to bypass the QSPI idle checking.
u-boot-iot2050: Reset the eMMC when it isn't reachable:
After approximately 2 months of operation with above workaround, the device
may fail to detect the eMMC when rebooting. Providing a temporary workaround
to reset the eMMC if detection issues occur.
Related to #440.