-
Notifications
You must be signed in to change notification settings - Fork 33
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
SD timeout #16
Comments
Another user reported this issue in the 0x64 discord, but it has not been root caused. In that case, the failure was board specific. So likely you didn't do anything wrong, but there is some bug that's causing sdhci init to be non-deterministic. |
If you comfortably with a bit of kernel hacking please join us in the #ox64-nutcracker channel at pine64 (https://wiki.pine64.org/wiki/Main_Page#Chat_Platforms) |
For anyone who wants to provide your own debug information from your example of this issue, if you flash these binaries with BLDevCube, and then use the normal SD card image, you'll find it starts spewing a whole ton of debug information regarding exactly what the SDHCI controller is doing at any given time, including errors and retries: |
This with a SanDisk Class 2 8GB microSD card and the Kernel 6.2-rc5 release of buildroot. I had similar issues with a 4GB card (can't find it to check the specs) but not with a PNY Elite-X 64GB card. |
I tried out my other boards and turns out I picked the only one of them which has issues with SDs. Here's the logs of all 5. 01 is the one with issues. I labelled the boards, so if you need to test something, just reach out and ask :) I'll look into possible assembly-issues soon, so if something is wrong with the soldering or alike, I will tell you. |
Adding this datapoint. I have 3 boards, 1 has the problems described above. People have reported the SDK works fine on the bad boards getting back to software. I ran U-Boot on the bad board and got an error not seen on the good boards:
Which makes me think this is more hardware than software. Annoyingly, the same U-Boot program only succeeds on 1 of the two boards that have been running buildroot. However the failing board recognizes the device but does nothing with any mmc operation. It does not report the error above. |
Little more information. Was using one of my Ox64 boards this evening to test something completely unrelated, and it just stopped working. Was working one moment, removed the SD card to add some more files, reinserted and reset the board and it just started getting IO errors and timing out. Rewrote my buildroot to the card from scratch, same issue. Tried the card in another board, worked fine. |
I am also having this issue but only with one of my SD cards. I am using The SD card on the left is the problematic one. It was causing the exact same issue. I got that Netac SD card from the Enter 3D printer. The problem has disappeared when I have put the OS into the Verbatim one. Same OS, same board, different SD card. |
Thanks for the info! looks like it is basically impossible to specifically get that Netac card for me, only higher capacity Netac cards. All information like this is helpful though! |
I am having a similar issue with a PNY 4GB microSD. Here is the output using the mmc debug binaries and 0.0.5 sdcard image: |
I am also getting these errors (
|
Hi everybody, |
I have found the same. In my post above I used a very old 2gb card (Sandisk). A much more recent 32gb (Kingston Canvas Select) card works absolutely fine. |
We are facing at least two separate problems here. Some have problems with specific SD-cards. Changing them will result in a working device. But others have problems with specific boards with all SD-cards. Changing the SD-card doesn't seem to help in those cases, changing the board does. I'm not saying that these are not related, but it might be good to differentiate between those. The workaround "Just use a different SD-Card" only applies to the former case... |
I'm having similar issues, which manifest differently since the 1.0 build that loads the uBoot config and kernel from the SD card. I usually see a Boot Logs
|
I had the same error. |
Hi,
I'm trying to run it on my Ox64. I flashed the low-load fw and the image, and dd'd the sdcard.img to two different sd-cards.The bootloader and the kernel start without a problem, but the rootfs doesn't get mounted and linux stops booting.
Here is my bootlog:
The SDHCI register dump continues several times afterwards.
This is the parted-output for one of the SD's:
Am I missing something, or is there something going on with the SDHCI?
The text was updated successfully, but these errors were encountered: