Hi! On Mon, Sep 4, 2017 at 10:31 PM, Paul Barker <[email protected]> wrote:
> On Fri, Aug 25, 2017 at 6:27 PM, Khem Raj <[email protected]> wrote: > > On Fri, Aug 25, 2017 at 10:14 AM, Bill Jenkins <[email protected]> wrote: > >> > >> On Aug 25, 2017, at 9:42 AM, Khem Raj <[email protected]> wrote: > >> > >> > >> On Fri, Aug 25, 2017 at 9:39 AM Bill Jenkins <[email protected]> wrote: > >>> > >>> I am trying to just get the simple 64-bit rpi-basic-image to work, but > the > >>> Raspberry Pi 3 seems to hang with the rainbow screen at startup. > >> > >> > >> Can you plugin a serial cable and see if that worked or try to add ssh > >> daemon on target and try to ssh into pi > >>> > >>> > >> > >> That was a good call. I can login with the ssh daemon, so it does > >> successfully boot. I just > >> cannot access it from the HDMI port. (I do not have the hardware for a > >> serial connection > >> at the moment) > >> > >> Any ideas on how to get the HDMI port to function the same way as it > does > >> for the > >> 32-bit case? > >> > > > > Readding the mailing list. > > > > what you have is exactly what I had when I submitted the port to > > meta-raspberrypi. Haven;t had a chance to revisit it. but this could > > be related to device tree files we are using here. I have had reports > > from other devs of having been able to boot into graphics using older > > kernels but I never got > > that far myself. > > I'm seeing the same issue on builds from both pyro and master > branches. I've confirmed this isn't a HW issue by trying out an > OpenSUSE Leap 42.2 64-bit build for Raspberry Pi 3. > > Khem, are you saying this is the current expected state of Raspberry > Pi 3 64-bit support? If so I'd really like us to document this in the > readme and open a bug so we don't lose track of it. > Reading this thread made me curious to get back to building/testing for raspberrypi3-64 myself as I used to do for a while till a few months ago. Not really in the need for that now, but, it would be nice to help keeping the support healthy if possible. Then tonight I added back MACHINE=raspberrypi3-64 bitbake myimage to the builds I run daily with master branches of poky and meta-raspberrypi and felt into a even earlier showstopper than the boot issue described here. My kernel build fails with: Build Configuration: BB_VERSION = "1.35.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "raspberrypi3-64" DISTRO = "poky" DISTRO_VERSION = "2.3+snapshot-20170908" TUNE_FEATURES = "aarch64" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "HEAD:8b4f16a9cbbaf521461f699b7264fac2ac872581" meta-raspberrypi = "HEAD:e59132bdcc092597ed5f08a77e7160b0f3bb3547" Initialising tasks: 100% |#####################################################################################################################################################################################################| Time: 0:00:11 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0 do_compile: oe_runmake failed ERROR: linux-raspberrypi-1_4.9.41+gitAUTOINC+4153f509b4-r0 do_compile: Function failed: do_compile (log file is located at /workdir/bsl/build-poky/tmp-poky/work/raspberrypi3_64-poky-linux/linux-raspberrypi/1_4.9.41+gitAUTOINC+4153f509b4-r 0/temp/log.do_compile.8392) ERROR: Logfile of failure stored in: /workdir/bsl/build-poky/tmp-poky/work/raspberrypi3_64-poky-linux/linux-raspberrypi/1_4.9.41+gitAUTOINC+4153f509b4-r0/temp/log.do_compile.8392 Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 8 HOSTCC=gcc HOSTCPP=gcc -E uImage CC=aarch64-poky-linux-gcc -fuse-ld=bfd --sysroot=/workdir/bsl/build-poky/tmp-poky/work/raspberrypi3_64-poky-linux/linux-raspberrypi/1_4.9.41+gitAUTOINC+4153f509b4-r0/recipe-sysroot - ffile-prefix-map=/workdir/bsl/build-poky/tmp-poky/work-shared/raspberrypi3-64/kernel-source=/kernel-source/ LD=aarch64-poky-linux-ld.bfd --sysroot=/workdir/bsl/build-poky/tmp-poky/work/raspberrypi3_64-poky-linux/linux-raspberrypi/1_4. 9.41+gitAUTOINC+4153f509b4-r0/recipe-sysroot LOADADDR=0x00008000 | make[2]: *** No rule to make target 'uImage'. Stop. | Makefile:150: recipe for target 'sub-make' failed | make[1]: *** [sub-make] Error 2 | Makefile:24: recipe for target '__sub-make' failed | make: *** [__sub-make] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at /workdir/bsl/build-poky/tmp-poky/work/raspberrypi3_64-poky-linux/linux-raspberrypi/1_4.9.41+gitAUTOINC+4153f509b4-r0/temp/log.do_compile.8392) ERROR: Task (/workdir/bsl/build-poky/conf/../../layers/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 4764 tasks of which 4763 didn't need to be rerun and 1 failed. The only particular configuration I have here (and probably did not have when testing it a while ago) as you can guess by the missing target name is that i boot to U-Boot with KERNEL_IMAGETYPE = "uImage". Does this ring a bell to anyone?
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
