Hi all, as others before me, I am trying to use poky and meta-ti to customize Yocto to run on the Beaglebone Black (and Green). The reason to use the meta-ti layer is to get the drivers for the PowerVR GPU and for the PRUs. At the moment I have used meta-ti zeus branch and I have been able to compile both core-image-minimal and core-image-base. Both compilations have been successful but when I try to load the generated wic.xz images in the beaglebone through the MMC the board does not boot. The same images using meta-yocto-bsp (instead of meta-ti) and setting the machine to beaglebone-yocto are booting fine. Therefore, before going further with the tests, I have decided to check if the initial assumptions/the current setup are correct. I have seen a few threads here in the mailing list with a similar topic, the last ones being: * [meta-ti] Getting Started with meta-ti "rocko" and beaglebone black (BBB) ( https://www.yoctoproject.org/pipermail/meta-ti/2018-August/011034.html ) * [meta-ti] Poky and meta-ti advice for Beaglebone Black ( https://www.yoctoproject.org/pipermail/meta-ti/2018-September/011179.html ) * [meta-ti] Building for AM335x with meta-ti and meta-qt5 ( https://www.yoctoproject.org/pipermail/meta-ti/2019-July/012020.html ) There is a nice presentation too Working with meta-ti - Yocto Project Wiki ( https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf ) , but it seems to be outdated. Even considering the documentation above I still have a few doubts: * I don't get which is the branch expected to work for every SOC (possibly different depending on the SOC). At the moment I am interested in the amx335 SOC used for both the beaglebone black and green. Is there in the repository a note in a readme explaining the combinations that are expected to work? * which are the differences between the machines am335-evm and beaglebone? "Only" the KERNEL_DEVICETREE setup? Are the differences summarized somewhere? * given that I can test the resulting distro on a beaglebone green should I try to set the machine to beaglebone or to am335-evm and customize the uEnv.txt? Which is the suggested/supported approach? I see that in the past it has been suggested to use the am335-evm, but probably that suggestion is outdated now. * when using meta-ti, is it suggested to add the meta-yocto-bsp layer in the bblayers.conf or not? There are threads and patches (added and reverted) about that, but I am not sue about the updated verdict As explained above I am not sure witch branch or tag is expected to work with MACHINE=beaglebone. I am currently using: * meta-ti: branch zeus, commit 1dd4558 * poky: branch zeus, commit ca9cc50 * meta-openembedded: branch zeus, commit 44e458f Anyway here you have the two boot log: * the first one is ok and has been obtained using meta-yocto-bsp * the second one is giving the error "## Error: "bootcmd_nand0" not defined" followed by others Log 1 U-Boot 2019.07 (May 05 2020 - 16:35:11 +0000) CPU : AM335X-GP rev 2.1 Model: TI AM335x BeagleBone Black DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment not set. Validating first E-fuse MAC Net: eth0: ethernet@4a100000 Warning: usb_ether MAC addresses don't match: Address in ROM is de:ad:be:ef:00:01 Address in environment is c8:fd:19:c6:c2:93 , eth1: usb_ether Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 119 bytes read in 2 ms (57.6 KiB/s) 1: Yocto Retrieving file: /zImage 4755816 bytes read in 305 ms (14.9 MiB/s) append: root=PARTUUID=00033363-02 rootwait console=ttyS0,115200 Retrieving file: /am335x-bonegreen.dtb 56060 bytes read in 6 ms (8.9 MiB/s) ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Device Tree to 8ffef000, end 8ffffafb ... OK Log 2 U-Boot 2020.01-gae8ceb7b6e (May 04 2020 - 18:55:25 +0000) CPU : AM335X-GP rev 2.1 Model: TI AM335x BeagleBone Black DRAM: 512 MiB WDT: Started with servicing (60s timeout) NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment not set. Validating first E-fuse MAC Net: eth0: ethernet@4a100000 Warning: usb_ether MAC addresses don't match: Address in ROM is de:ad:be:ef:00:01 Address in environment is c8:fd:19:c6:c2:93 , eth1: usb_ether Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... switch to partitions #0, OK mmc0 is current device SD/MMC found on device 0 switch to partitions #0, OK mmc1(part 0) is current device ** No partition table - mmc 1 ** switch to partitions #0, OK mmc1(part 0) is current device SD/MMC found on device 1 ** No partition table - mmc 1 ** ## Error: "bootcmd_nand0" not defined starting USB... Bus usb@47401800: Port not available. ethernet@4a100000 Waiting for PHY auto negotiation to complete.................................................................................. done link up on port 0, speed 100, full duplex BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 192.168.0.16 (900 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-c8-fd-19-c6-c2-91 link up on port 0, speed 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A80010 link up on port 0, speed 100, full duplex *** ERROR: `serverip' not set Retrieving file: pxelinux.cfg/C0A8001 link up on port 0, speed 100, full duplex Any suggestion would be very much appreciated. Luca