This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3358: Yocto kernel fragments issue



Hello

We are using a bbappend on linux-ti-staging (master branch) based on this page (https://processors.wiki.ti.com/index.php/MUSB_Linux_Driver_Configuration). For some reason musb_am335x.ko, musb_dsps.ko and musb_hdrc.ko are still being built despite the fragment. Below is a copy of the fragment and also the bbappend file.

fragment_MUSB.cfg

# MUSB
CONFIG_USB_MUSB_HDRC=y
CONFIG_USB_MUSB_HOST=n
CONFIG_USB_MUSB_GADGET=n
CONFIG_USB_MUSB_DUAL_ROLE=y
CONFIG_USB_MUSB_TUSB6010=n
CONFIG_USB_MUSB_OMAP2PLUS=n
CONFIG_USB_MUSB_AM35X=n
CONFIG_USB_MUSB_DSPS=y
CONFIG_USB_MUSB_UX500=n
CONFIG_USB_TI_CPPI41_DMA=y
CONFIG_MUSB_PIO_ONLY=n
CONFIG_AM335X_PHY_USB=y

# MISC to avoid prompt
CONFIG_USB_SISUSBVGA=n



linux-ti-staging_4.19.bbappend


FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

SRC_URI += "file://am335x-customboard.dts;subdir=git/arch/arm/boot/dts"
SRC_URI += " \
file://fragment_CONFIG_RTC_DRV_PCF8563.cfg \
file://fragment_ETHERNET.cfg \
file://fragment_MISC.cfg \
file://fragment_MUSB.cfg \
file://fragment_TOUCHSCREEN.cfg \
file://fragment_SOUND.cfg \
file://fragment_REGULATORS.cfg \
file://fragment_I2C.cfg \
"

#FILESEXTRAPATHS_append := ":${THISDIR}/files"


#PACKAGE_ARCH = "${MACHINE_ARCH}"

KERNEL_CONFIG_FRAGMENTS_append=" \
${WORKDIR}/fragment_CONFIG_RTC_DRV_PCF8563.cfg \
${WORKDIR}/fragment_MISC.cfg \
${WORKDIR}/fragment_TOUCHSCREEN.cfg \
${WORKDIR}/fragment_SOUND.cfg \
${WORKDIR}/fragment_REGULATORS.cfg \
${WORKDIR}/fragment_I2C.cfg \
${WORKDIR}/fragment_MUSB.cfg \
"