-
Notifications
You must be signed in to change notification settings - Fork 77
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
Add temporary workaround for the reboot issues #564
Conversation
126ea5e
to
8c63326
Compare
+ 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo?
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.
Corrected.
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.
Rather a debug left-over 😉
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.
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]>
8c63326
to
ce45f46
Compare
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"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]>
ce45f46
to
84dc8df
Compare
Approved since this need customer side debugging info, let's have a final version after getting any feedback. |
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.