Part Number: SK-AM68
Other Parts Discussed in Thread: AM68, AM69
Hi,
I had a previous issue here https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1223446/sk-am68-bootloader-only-works-with-hs-version-and-gpu-crashing-when-running-glmark2-with-yocto,
In which tiboot3-j721s2-gp-evm.bin will not boot up the device but tiboot3-j721s2-hs-fs-evm.bin would. I have been told it would not work with the `gp` bootloader however I have not seen any definitive documentation regarding this. The SDK from 08/06 mentions uboot CAN be built for hs, but mentions no need to do so.
Now, 4 months later I have pulled the latest kirkstone branch and I am unable to boot with either bootloader, the board acts effectively dead with no output to the terminal on ttyUSB2.
So the details are the same, here is my local.conf:
IMAGE_INSTALL:append = " vim glmark2" MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules" DISTRO_FEATURES:remove = "x11 vulkan" DISTRO_FEATURES:append = " wayland egl gles2" DISTRO_FEATURES:append = " pam opencv openmp" PACKAGECONFIG:append:pn-glmark2 = " drm-gles2 wayland-gles2" PACKAGECONFIG:append:pn-libsdl2 = " kmsdrm" PACKAGECONFIG:append:pn-weston = " egl wayland" PACKAGECONFIG:append:pn-cairo = " egl glesv2" KERNEL_DEVICETREE_PREFIX:append = " k3-am68 ti/k3-am68" KERNEL_DEVICETREE:append = " ti/k3-am68-sk-base-board.dtb" MACHINE ??= "j721s2-evm"
And my bblayers.conf:
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/rich/Yocto/poky-kirkstone/meta \
/home/rich/Yocto/poky-kirkstone/meta-poky \
/home/rich/Yocto/poky-kirkstone/meta-yocto-bsp \
/home/rich/Yocto/poky-kirkstone/meta-arm/meta-arm-toolchain \
/home/rich/Yocto/poky-kirkstone/meta-arm/meta-arm \
/home/rich/Yocto/poky-kirkstone/meta-ti/meta-ti-bsp \
/home/rich/Yocto/poky-kirkstone/meta-openembedded/meta-oe \
/home/rich/Yocto/poky-kirkstone/meta-openembedded/meta-python \
/home/rich/Yocto/poky-kirkstone/meta-openembedded/meta-networking \
/home/rich/Yocto/poky-kirkstone/meta-freescale-distro \
"
I build the image e.g. `bitbake core-image-weston` and now I get a new folder now in build/deploy-ti/images/j721s2-evm. Flash it onto my SD card, place it into the starter kit and use picocom to read TTYUSB2, and I get no output.
Details of the boot partition on the SD card (defaults to gp bootloader, but neither will work):
rich@rich-Precision-3660:/media/rich/boot$ ls -lh total 24M drwxr-xr-x 3 rich rich 2.0K Apr 5 2011 EFI -rw-r--r-- 1 rich rich 21M Apr 5 2011 Image -rw-r--r-- 1 rich rich 463K Apr 5 2011 tiboot3.bin -rw-r--r-- 1 rich rich 463K Apr 5 2011 tiboot3-j721s2-gp-evm.bin -rw-r--r-- 1 rich rich 466K Apr 5 2011 tiboot3-j721s2-hs-fs-evm.bin -rw-r--r-- 1 rich rich 1004K Apr 5 2011 tispl.bin -rw-r--r-- 1 rich rich 1.3M Apr 5 2011 u-boot.img rich@rich-Precision-3660:/media/rich/boot$ ls EFI BOOT rich@rich-Precision-3660:/media/rich/boot$ ls EFI/BOOT bootaa64.efi grub.cfg rich@rich-Precision-3660:/media/rich/boot$
Regarding the SDK documentation here: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am68/09_00_00_06/exports/docs/devices/J7_Family/linux/Release_Specific_Yocto_layer_Configuration.html
The default config hasn't even been setup correctly, so you will get an error.
ERROR: Layer 'meta-arago-extras' depends on layer 'openembedded-layer', but this layer is not enabled in your configuration
I have been told from customer support previously that SDK9 will feature the following updates:
For SDK 9.0 – Make uboot would build HS-FS, GP and HS-SW with the correct names and GP being default.
For SDK 9.0 – Add documentation around which uboot image to use for which Board.
For SDK 9.0 - WIC image to have only relevant Uboot images.
It isn't made clear at all what bootloader is needed from https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am68/09_00_00_06/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html#build-u-boot as there isn't a specific table documenting what the AM68 is. However https://www.ti.com/product/AM68 the product page describes it as a "General Purpose SoC" so I would assume it is a GP device. But again the GP bootloader has never worked for me. There are so many acronyms that are poorly explained across the SDK, for example K3 you won't find defined as Keystone 3 as there is no glossary. I also found that the default image had no output on DisplayPort.
I have the exact same issues with booting on the AM69-SK.
Regardless, could someone explain which bootloader is needed and additionally why it is not working? Thank you
