ok, came back to this for another go…
given the kernel version your using is 3.14, Im guessing you must have used the 3.14 LTS… which is not incorrectly linked on the above dev site (to 3.10)
so Ive compiled the latest 3.14 from solid run, which is this:
following the instructions from your link above, with the 3.14 LTS , with
builds, and boots, but it gets stuck waiting for mmcblk0p1
(this is the same issue I had before when upgrading to a 4.x kernel, so kind of useful if I can get to the bottom of, might enable a much newer kernel)
basically on a normal console you see:
[ 1.953073] RAMDISK: Couldn't find valid RAM disk image starting at 0.
[ 1.964744] EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities
[ 1.965438] EXT4-fs (mmcblk0p1): couldn't mount as ext2 due to feature incompatibilities
[ 1.981761] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
but with this it says, after RAMDISK above
waiting for root device /dev/mmcblk0p1
so… seems like either:
a) something wrong with mmc setup… DTB?
b) cant read the EXT4-fs
(fyi: I’m using the existing u-boot/SPL, I could rebuild, but I suspect that wont make any difference)
is this something you came across when you built the kernel?
is there a way I can attach a serial UART cable to get a console log?
perhaps there is an error earlier that I’m not seeing, that might be enlightening
(over HDMI, theres a screen refresh, so you dont see early part, and some of it zooms off to fast to see)
EDIT: hmm, also seeing the same mmc -110 device error
a search on this says the SD card is corrupt, but its not, I can mount it on another Linux system, change /boot back to old kernel, and it works fine.