11-22-2019, 02:12 PM
(This post was last modified: 11-25-2019, 09:43 PM by SuburbanDad.)
(11-20-2019, 02:21 PM)martinayotte Wrote:(11-20-2019, 01:05 AM)SuburbanDad Wrote: So I have been operating under the assumption this was a software only problem.
Maybe ... I don't know since my PineH64 is equipped with eMMC yet, I've asked @tllim if he could provide me a sample so I can narrow the issue.
Thanks for looking into it. In the interim, does anybody have any pointers for repairing the u-boot install on eMMC? The furthest I have gotten is getting u-boot installed and attempting to find the kernel/root partition (I am not sure which is failing). There aren't specific offsets that u-boot is using to find root partition right? My understanding is that it should just check the target partition for Image or zImage in `/` or `/boot`. any old ext4 or btrfs partition should work?
TIA
edit: after some more iterating on various configs, it is pretty clear that it is a kernel build issue. Android 9 starts from mmc fine, AOSC 02-16-19 also. But AOSC 07-09-19 and the armbian images do not boot. They seem to load the kernel, then go awry when they need to read from mmc. However, in AOSC 02-16 the neither the NIC nor the wifi work. Seriously tedious. When I boot Armbian from SD, everything works. Except the eMMC.
I will make a pass at building a new kernel from the 5.90 kernel sources, but I am just throwing darts at this point.