-
Notifications
You must be signed in to change notification settings - Fork 42
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
beagleboard XM doesn't boot on v3.19-rc7 #25
Comments
I have the same issue |
mmc0 error 110: use a different microsd card brand. |
Hi,
I replaced the spl and uboot with v2015.04.rc2.r2 and it works fine.
Thank you
|
@Nash-Strongman how you replace th spl and uboot.I am facing the same problem. |
@gurpartap007 Use the netinstall method from http://elinux.org/BeagleBoardUbuntu#Method_2:_Use_the_NetInstall_method. Download the required versions of spl and uboot from http://rcn-ee.com/repos/bootloader/omap3_beagle/ |
Can you recommend a brand that works? I've tried several now with the same issue |
@ndyer have you tried the latest image, i bump u-boot and the kernel: Right now i'm using Kingston 8GB (SDC10)'s, as all my SanDisk Ultra 8GB's fail... Regards, |
Hello, Somewhere around 3.10-3.14 a fixed delay in the mmc drivers was removed, that caused the problem. I wasn't aware of that delay before. If have another problem with the SanDisk on another omap3 platform. If I press the reset botton uboot still works and can access the SD Card, but the kernel says: |
Guys, some of my SanDisk ultra's are now working with v2015.07-rc2 + v4.1.0-rc7 on the xM.. Updated image from last week: Regards, |
It keeps happening with U-Boot 2015.10-rc1-00001-gb885963 and kernel 4.1.6-armv7-x2. |
A similar issue is hitting sunxi: haven't tested their patch to see if fixes ours... |
I tried appliying the "Setting the bus clock before the access mode switch fixed it" but after the second reboot the error is still there. |
I'm looking at the: |
Okay this looks to be a regression in v3.17.x Just built/installed v3.16.x and booted my xm: Will start bisecting the v3.17.x tomorrow.. |
Humm: (looking v3.16..v3.17) added: [ 11.463745] mmc0: card never left busy state Regards, |
Seems that i will have to modify that timeout mmc_delay(10) for something bigger or increase i variable to give it more time to left busy state. Thanks. |
Okay, git bisect is pointing too:
Starting verification...
|
So verification failed..
I'll start the bisect again, makeing sure to also include ^ patch... |
I applied 0002-mmc-retry-in-the-case-of-failing-to-switch-to-HS-mod.patch from sunxi to u-boot and after several reboots and reset pushes Kingston SD's boots correctly, from time to time it fails. Sandisk Ultra stil failing but no so many as before, maybe if the timeout in the patch is increased this problem will be solved. |
I want to count how many times Sandisk Ultra fails to leave busy state but I could't find how to enable debug messages for mmc.c. |
Not sure if was thanks to the patch or just a coincidence. |
Sorry, i was wrong. |
This might explain the issue I am having. I have Jessie working on my XM revC - no problems, except room. It is a 2GB Kingston card. Cloned the image onto a 4GB SanDisk, and before I expanded partition, fired it up. Boots fine, however it will only cold boot. Reboot, Shutdown -r, etc. bring the XM down, but it never comes back. Started from scratch with netinstall of Wiley and Xenial, and results are the same - cold boots and power on through 5V wall wart are only way to get the board up. This is all on the SanDisk 4GB. I have a SanDisk Ultra 8GB and the results are the same except that the card stopped working and boots to BusyBox and the '[8.921] never left busy state' along with the '110' error. I have just ordered both Kingston and PNY cards in various sizes to see if that solves reboot issue. Does it make sense this is all related? Am I too bleeding edge with kernel (4.4.1) and should go back to earlier ones? I remember years ago, I had Maverick running perfectly on this same board and it had GNOME and all the trimmings on a 4GB card - probably in some cell phone somewhere for photos since then. |
tried to install using the netinstall method, getting a kernel panic U-Boot SPL 2016.01-00001-g3f205b0 (Mar 01 2016 - 14:23:49) U-Boot 2016.01-00001-g3f205b0 (Mar 01 2016 - 14:23:49 -0600), Build: jenkins-github_Bootloader-Builder-337 OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz Beagle xM Rev C Hit any key to stop autoboot: 1 ��� 0 Installer for [trusty-armhf] is using the Serial Interface debug: [console=ttyO2,115200n8 root=/dev/ram rw] ... Flattened Device Tree blob at 88000000Booting using the fdt blob at 0x88000000 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 |
@code-struck actually that's a different issue.. trusty looks to be broken with 4.4.x kernel, it works with 4.1.x:
Or switch to either wily/xenial, as that boots fine with 4.4.x We are about a month away from xenial (16.04) being released, so I personally don't see any worth in fixing trusty (14.04).. But if you find something let me know. Regards, |
Ah okay then, thank you. I think I will just wait a month then to install 16.04. |
@code-struck xenial's an lts release, currently just past the beta point, it's pretty safe right now, you should only see fixes leading up to next month.. |
I have built a kernel from your tree using build_mainline.sh and am trying to boot it using the ubuntu-14.04.1-console-armhf-2015-01-06 system image as recommended on http://www.elinux.org/BeagleBoardUbuntu#Method_1:_Download_a_Complete_Pre-Configured_Image
I get the following output on console at boot, then it hangs:
The text was updated successfully, but these errors were encountered: