Built core-image-minimal for meta-ti (a345e0c2) and current yocto 2.7.1 (38d5c8e): Build Configuration: BB_VERSION = "1.42.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "linuxmint-19.1" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "beagleboard" DISTRO = "poky" DISTRO_VERSION = "2.7.1" TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard" TARGET_FPU = "hard" meta meta-poky meta-yocto-bsp = "warrior:38d5c8ea98cfa49825c473eba8984c12edf062be" meta-ti = "master:a345e0c20596d4a7924143aead795510d14381fc" No custom patches/configurations were added. I appended lines similar to the lines immediately below to my conf/local.conf. MACHINE = "beagleboard" DL_DIR = "PathToMyDlsDir" SSTATE_DIR = "PathToMySsDir" Only the meta-ti (a345e0c2) layer was added to conf/bblayers.conf. The resulting Linux kernel and device tree (omap3-beagle-xm.dtb) fails to boot on a Beagleboard-xM (rev C). No console output appears after the u-Boot generated "Starting kernel ..." message. A similar 4.19 Linux kernel does boot on the same hardware. That 4.19 Linux kernel was build per the instructions at https://www.digikey.com/eewiki/display/linuxonarm/BeagleBoard. Note: I will create a similar bug report for meta-ti (a345e0c2) created U-Boot since it also fails to boot on on Beagleboard-xM (rev C).
meta-ti is not tracked in this bugzilla. Please contact the BSP owner. Such info may be in the layer README or just look at the git logs.
(In reply to comment #1) > meta-ti is not tracked in this bugzilla. Please contact the BSP owner. Such > info may be in the layer README or just look at the git logs. When I google 'report +"meta-ti" bug', the first result is: https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking I tried to follow the Yocto Project described bug reporting process. After reviewing the URL above, I don't understand your actions (e.g. comment and status change). This was assigned to "Denys Dmytriyenko". The https://lists.yoctoproject.org/listinfo/meta-ti URL says "meta-ti list run by denis at denix.org, denys at ti.com".
Hi Kevin, I can see how you would be lead to believe that the YP bugzilla should be used to file meta-ti bugs. Unfortunately, from what I know, this is not the case. Hopefully Denys can response to confirm the situation. Looking that the meta-ti/README: ... Send pull requests, patches, comments or questions to meta-ti@yoctoproject.org Please note - meta-ti mailing list requires subscription for posting: https://lists.yoctoproject.org/listinfo/meta-ti Maintainers: Denys Dmytriyenko <denys@ti.com> ----- so it would appear that the email list should be used. Once this is confirmed, we will update the wiki and the YP Bugzilla categories so that other people are not lead to a similar conclusion. Oh and sorry for my initial terse response, I was responding during the YP bug review meeting so time was short. -- Randy
reopening
The defect was re-opened because Richard Purdie explained that there is an understanding with the Ti rep (Denys) that ti bugs can be added to the YP bugzilla but the bug review team will not triage or assign them. No change to the wiki and the YP Bugzilla categories is needed. Sorry for the noise. ../Randy
Based on information from Denys, I confirmed the mainline and meta-ti beagleboard builds work when used with a kernel configuration (i.e. .config) compatible with the Beagleboard-xM. A recent defconfig from the URL below allowed a meta-ti (44a979c52659ac997fc2ed4602a82b7bb97d33f2) Linux kernel build to run on a Beagleboard-xM. https://github.com/RobertCNelson/armv7-multiplatform/blob/v4.19.x/patches/defconfig
This has been fixed 5 years ago in meta-ti.