# AM5708 tisdk mender add **URL:** \ **Category:** General Discussions\ **Tags:** yocto\ **Created:** [July 14, 2021, 9:25am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874 "2021-07-14T09:25:05Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![vimalltts](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@vimalltts](https://hub.mender.io/u/vimalltts)\ **Post date:** [July 14, 2021, 9:25am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/1 "2021-07-14T09:25:05Z")
Hi, i am facing the Issue when i was add meta-mender-core and demo file in arago project. but i got compiler error error: ERROR: Task do\_patch in /home/admins/40012121\_backup/Ti\_AM5708/mender-fota/sources/meta-mender/meta-mender-core/recipes-bsp/u-boot/u-boot-fw-utils-mender-auto-provided\_1.0.bb depends upon non-existent task do\_mender\_tar\_src in /home/admins/40012121\_backup/Ti\_AM5708/mender-fota/sources/meta-ti/recipes-bsp/u-boot/u-boot-ti-staging\_2019.01.bb ERROR: Command execution failed: 1 ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [July 14, 2021, 1:33pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/2 "2021-07-14T13:33:24Z")
You need to do an integration with u-boot-ti-staging. See [this link](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot) for details. Drew ---
**Author:** ![vimalltts](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@vimalltts](https://hub.mender.io/u/vimalltts)\ **Post date:** [July 14, 2021, 2:12pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/3 "2021-07-14T14:12:56Z")
```auto # CONF_VERSION is increased each time build/conf/ changes incompatibly CONF_VERSION = "1" # # Where to place downloads # # During a first build the system will download many different source code # tarballs from various upstream projects. This can take a while, particularly # if your network connection is slow. These are all stored in DL_DIR. When # wiping and rebuilding you can preserve this directory to speed up this part # of subsequent builds. This directory is safe to share between multiple builds # on the same machine too. DL_DIR = "/home/admins/40012121_backup/Ti_AM5708/mender-fota/downloads" # # Where to place shared-state files # # BitBake has the capability to accelerate builds based on previously built # output. This is done using "shared state" files which can be thought of as # cache objects and this option determines where those files are placed. # # You can wipe out TMPDIR leaving this directory intact and the build would # regenerate from these files if no changes were made to the configuration. # If changes were made to the configuration, only shared state files where the # state was still valid would be used (done using checksums). SSTATE_DIR = "${OEBASE}/build/sstate-cache" # # Shared-state files from other locations # # As mentioned above, shared state files are prebuilt cache data objects which # can be used to accelerate build time. This variable can be used to configure # the system to search other mirror locations for these objects before it # builds the data itself. # # This can be a filesystem directory, or a remote url such as http or ftp. # These would contain the sstate-cache results from previous builds (possibly # from other machines). This variable works like fetcher MIRRORS/PREMIRRORS # and points to the cache locations to check for the shared objects. #SSTATE_MIRRORS ?= "\ #file://.* http://someserver.tld/share/sstate/ \n \ #file://.* file:///some/local/dir/sstate/" # # Where to place the build output # # This option specifies where the bulk of the building work should be done and # where BitBake should place its temporary files and output. Keep in mind that # this includes the extraction and compilation of many applications and the toolchain # which can use Gigabytes of hard disk space. TMPDIR = "${OEBASE}/build/arago-tmp" # # Machine Selection # # You need to select a specific machine to target the build with. There are a selection # of emulated machines available which can boot and run in the QEMU emulator: # MACHINE ?= "arago" # # Package Management configuration # # This variable lists which packaging formats to enable. Multiple package backends # can be enabled at once and the first item listed in the variable will be used # to generate the root filesystems. # Options are: # - 'package_deb' for debian style deb files # - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) # - 'package_rpm' for rpm style packages # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" # We default to ipk: PACKAGE_CLASSES ?= "package_ipk" # # SDK/ADT target architecture # # This variable specified the architecture to build SDK/ADT items for and means # you can build the SDK packages for architectures other than the machine you are # running the build on (i.e. building i686 packages on an x86_64 host._ # Supported values are i686 and x86_64 SDKMACHINE ?= "x86_64" # # Extra image configuration defaults # # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated # images. Some of these options are added to certain image types automatically. The # variable can contain the following options: # "dbg-pkgs" - add -dbg packages for all installed packages # (adds symbol information for debugging/profiling) # "dev-pkgs" - add -dev packages for all installed packages # (useful if you want to develop against libs in the image) # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) # "tools-debug" - add debugging tools (gdb, strace) # "tools-profile" - add profiling tools (oprofile, exmap, lttng valgrind (x86 only)) # "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) # "debug-tweaks" - make an image suitable for development # e.g. ssh root access has a blank password # There are other application targets that can be used here too, see # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. # We default to enabling the debugging tweaks. EXTRA_IMAGE_FEATURES = "debug-tweaks" # # Additional image features # # The following is a list of additional classes to use when building images which # enable extra features. Some available options which can be included in this variable # are: # - 'buildstats' collect build statistics # - 'image-mklibs' to reduce shared library files size for an image # - 'image-prelink' in order to prelink the filesystem image # - 'image-swab' to perform host system intrusion detection # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended USER_CLASSES ?= "buildstats image-mklibs image-prelink" # By default disable interactive patch resolution (tasks will just fail instead): PATCHRESOLVE = "noop" # Qemu 0.12.x is giving too much problems recently (2010.05), so disable it for users ENABLE_BINARY_LOCALE_GENERATION = "0" # By default the machine configuration file sets the IMAGE_FSTYPES. But if you # would like to add additional file system types you can uncomment the # following line and add the additional IMAGE_FSTYPES you want created # as part of the build flow. Some common types are listed below and you # can remove the ones you do not want. # IMAGE_FSTYPES += "jffs2 cramfs ext2.gz ext3.gz squashfs ubi tar.gz tar.bz2 cpio" # # Parallelism Options # # These two options control how much parallelism BitBake should use. The first # option determines how many tasks bitbake should run in parallel: # BB_NUMBER_THREADS ?= "3" # # The second option controls how many processes make should run in parallel when # running compile tasks: # PARALLEL_MAKE ?= "-j 3" # # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would # be appropriate for example DISTRO = "arago" # Set branding policy for Processor SDK ARAGO_BRAND ?= "processor-sdk" # Set terminal types by default it expects gnome-terminal # but we chose xterm TERMCMD = "${XTERM_TERMCMD}" TERMCMDRUN = "${XTERM_TERMCMDRUN}" # Don't generate the mirror tarball for SCM repos, the snapshot is enough BB_GENERATE_MIRROR_TARBALLS = "0" # Uncomment this to remove work directory after packaging to save disk space #INHERIT += "rm_work" # Keep one set of images by default RM_OLD_IMAGE = "1" MENDER_ARTIFACT_NAME = "release-1" INHERIT += "mender-full" ARTIFACTIMG_FSTYPE = "ext4" DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" VIRTUAL-RUNTIME_initscripts = "" #MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules" #MENDER_UBOOT_AUTO_CONFIGURE = "0" #MENDER_FEATURES_ENABLE_append = " mender-uboot" MENDER_FEATURES_ENABLE_append = " mender-uboot" MENDER_FEATURES_ENABLE_append = " mender-grub mender-image-uefi" MENDER_FEATURES_DISABLE_append = " mender-uboot mender-image-sd" PREFERRED_PROVIDER_u-boot = "u-boot-my-fork" ``` \*\*[quote=“drewmoseley, post:2, topic:3874, full:true”] You need to do an integration with u-boot-ti-staging. See [this link](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot) for details. Drew [/quote] its my local.conf its correct or not\*\* /edit: @drewmoseley added formatting. ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [July 14, 2021, 2:47pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/4 "2021-07-14T14:47:33Z")
It looks like you are using ‘u-boot-ti-staging’ but are literally specifying ‘u-boot-my-fork’. At a minimum the `PREFERRED_PROVIDER_u-boot` needs to be updated. But you also need to modify the `u-boot-ti-staging` recipe to implement the Mender integration. Drew ---
**Author:** ![vimalltts](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@vimalltts](https://hub.mender.io/u/vimalltts)\ **Post date:** [July 14, 2021, 8:19pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/5 "2021-07-14T20:19:06Z")
ERROR: core-image-base-1.0-r0 do\_image\_tar: Function failed: do\_image\_tar (log file is located at /home/admins/40012121\_backup/Ti\_AM5708/mender-fota/build/arago-tmp-external-arm-toolchain/work/am57xx\_evm-linux-gnueabi/core-image-base/1.0-r0/temp/log.do\_image\_tar.32070) ERROR: Logfile of failure stored in: /home/admins/40012121\_backup/Ti\_AM5708/mender-fota/build/arago-tmp-external-arm-toolchain/work/am57xx\_evm-linux-gnueabi/core-image-base/1.0-r0/temp/log.do\_image\_tar.32070 Log data follows: | DEBUG: Executing python function set\_image\_size | DEBUG: 76228.000000 = 76228 \* 1.000000 | DEBUG: 221184.000000 = max(76228.000000, 221184)[221184.000000] + 1 | DEBUG: 221184.000000 = int(221184.000000) | DEBUG: 221184 = aligned(221184) | DEBUG: returning 221184 | DEBUG: Python function set\_image\_size finished | DEBUG: Executing shell function do\_image\_tar | md5sum: core-image-base-am57xx-evm-20210714195726.rootfs.tar.xz: No such file or directory | WARNING: /home/admins/40012121\_backup/Ti\_AM5708/mender-fota/build/arago-tmp-external-arm-toolchain/work/am57xx\_evm-linux-gnueabi/core-image-base/1.0-r0/temp/run.do\_image\_tar.32070:1 exit 1 from ‘md5sum core-image-base-am57xx-evm-20210714195726.rootfs.tar.xz \> core-image-base-am57xx-evm-20210714195726.rootfs.tar.xz.md5’ | ERROR: Function failed: do\_image\_tar (log file is located at /home/admins/40012121\_backup/Ti\_AM5708/mender-fota/build/arago-tmp-external-arm-toolchain/work/am57xx\_evm-linux-gnueabi/core-image-base/1.0-r0/temp/log.do\_image\_tar.32070) ERROR: Task (/home/admins/40012121\_backup/Ti\_AM5708/mender-fota/sources/oe-core/meta/recipes-core/images/core-image-base.bb:do\_image\_tar) failed with exit code ‘1’ ```auto type or paste code here ``` I got one more error above mentioned ---
**Author:** ![vimalltts](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@vimalltts](https://hub.mender.io/u/vimalltts)\ **Post date:** [July 16, 2021, 8:22am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/6 "2021-07-16T08:22:47Z")
How to change U-boot-ti-staging. can you explain ---
**Author:** ![vimalltts](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@vimalltts](https://hub.mender.io/u/vimalltts)\ **Post date:** [July 16, 2021, 8:27am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/7 "2021-07-16T08:27:05Z")
u-boot-ti-staging.inc file or u-boot-stagining.bbappend file ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 16, 2021, 11:09am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/8 "2021-07-16T11:09:15Z")
require u-boot-ti.inc require recipes-bsp/u-boot/u-boot-mender.inc PROVIDES += “u-boot” RPROVIDES\_${PN} += “u-boot” #PR = “r32” #BRANCH = “ti-u-boot-2019.01” #SRCREV = “350f3927b89bc06ce1c9ddb618280d298c418b94” i changed in my u-boot-ti-staging\_2019.01.bb file ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [July 16, 2021, 7:56pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/9 "2021-07-16T19:56:41Z")
That’s a minimal first step. You also need to determine if automatic patching works for your fork or if you need [manual patching](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot/manual-u-boot-integration). Drew ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 17, 2021, 7:43am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/10 "2021-07-17T07:43:05Z")
admins@admins-OptiPlex-7050:~/40012121\_backup/Ti\_AM5708/mender-fota/build$ MACHINE=am57xx-evm bitbake -e u-boot | grep ‘^MENDER\_UBOOT\_AUTO\_CONFIGURE=’ MENDER\_UBOOT\_AUTO\_CONFIGURE=“0” i set in auto patch see above line ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 17, 2021, 7:44am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/11 "2021-07-17T07:44:35Z")
next step i apply this command bitbake -c save\_mender\_auto\_configured\_patch u-boot After i got the below Error ERROR: Task do\_save\_mender\_auto\_configured\_patch does not exist for target u-boot (/home/admins/40012121\_backup/Ti\_AM5708/mender-fota/sources/meta-ti/recipes-bsp/u-boot/u-boot-ti-staging\_2019.01.bb:do\_save\_mender\_auto\_configured\_patch) ERROR: Command execution failed: 1 Summary: There were 7 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 17, 2021, 7:49am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/12 "2021-07-17T07:49:34Z")
iam following manual patch. ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 18, 2021, 4:03pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/13 "2021-07-18T16:03:08Z")
ERROR: Task do\_save\_mender\_auto\_configured\_patch does not exist for target u-boot (/home/admins/40012121\_backup/Ti\_AM5708/mender-fota/sources/meta-ti/recipes-bsp/u-boot/u-boot-ti-staging\_2019.01.bb:do\_save\_mender\_auto\_configured\_patch) ERROR: Command execution failed: 1 its my last updated Error ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [July 18, 2021, 8:38pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/14 "2021-07-18T20:38:13Z")
I think that means you are missing [step 1 from here](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot#forks-of-u-boot). Drew ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 19, 2021, 6:27am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/15 "2021-07-19T06:27:48Z")
i have mention below clearly what i did Step 1: git clone meta-mender in current build source directory Step 2: Added bblayer.conf /home/admins/40012121\_backup/Ti\_AM5708/am57xx-evm/sources/meta-mender/meta-mender-core /home/admins/40012121\_backup/Ti\_AM5708/am57xx-evm/sources/meta-mender/meta-mender-demo \ Step 3: in local,conf below Parameters added INHERIT += “mender-full” MENDER\_ARTIFACT\_NAME = “starship-discovery” #MENDER\_FEATURES\_ENABLE\_append = " mender-uboot" #DISTRO\_FEATURES\_append = " systemd" #VIRTUAL-RUNTIME\_init\_manager = “systemd” #DISTRO\_FEATURES\_BACKFILL\_CONSIDERED = “sysvinit” #VIRTUAL-RUNTIME\_initscripts = “” MENDER\_FEATURES\_ENABLE\_append = " mender-uboot mender-image-sd" MENDER\_FEATURES\_DISABLE\_append = " mender-grub mender-image-uefi" # Example: Memory card storage MENDER\_STORAGE\_DEVICE = “/dev/mmcblk0” # Example: Memory card with 2GiB of storage. MENDER\_STORAGE\_TOTAL\_SIZE\_MB = “2048” step 4: Below Mentioned Error I got ERROR: Task do\_patch in /home/admins/40012121\_backup/Ti\_AM5708/am57xx-evm/sources/meta-mender/meta-mender-core/recipes-bsp/u-boot/u-boot-fw-utils-mender-auto-provided\_1.0.bb depends upon non-existent task do\_mender\_tar\_src in /home/admins/40012121\_backup/Ti\_AM5708/am57xx-evm/sources/meta-ti/recipes-bsp/u-boot/u-boot-ti-staging\_2019.01.bb ERROR: Command execution failed: 1 Summary: There were 13 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. @drewmoseley for your ref ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [July 19, 2021, 12:53pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/16 "2021-07-19T12:53:11Z")
Yes, and you need to follow the instructions for a [custom u-boot fork.](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot#forks-of-u-boot) You are using the u-boot-ti-staging\_2019.01.bb recipe which has not been integrated with Mender. Drew ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 19, 2021, 1:11pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/17 "2021-07-19T13:11:33Z")
Next Step I did below Mentioned step 1: MACHINE=am57xx-evm bitbake -e core-image-base | egrep ‘^PREFERRED\_PROVIDER\_(virtual/bootloader|u-boot)=’ PREFERRED\_PROVIDER\_u-boot=“u-boot-ti-staging” PREFERRED\_PROVIDER\_virtual/bootloader=“u-boot-ti-staging” step 2: u-boot-ti-staging\_2019.01.bb file Added Below require u-boot-ti.inc require recipes-bsp/u-boot/u-boot-mender.inc PROVIDES += “u-boot” RPROVIDES\_${PN} += “u-boot” PREFERRED\_PROVIDER\_u-boot = “u-boot-my-fork” PR = “r32” BRANCH = “ti-u-boot-2019.01” SRCREV = “350f3927b89bc06ce1c9ddb618280d298c418b94” Note: Iam set Auto patch Enabled set “1” in u-boot-ti-staging\_2019.01.bb MENDER\_UBOOT\_AUTO\_CONFIGURE = “1” In Local.conf file added below Line MENDER\_FEATURES\_ENABLE\_append = " mender-uboot" But iam Facing Error below ERROR: Task do\_patch in /home/admins/40012121\_backup/Ti\_AM5708/am57xx-evm/sources/meta-mender/meta-mender-core/recipes-bsp/u-boot/u-boot-fw-utils-mender-auto-provided\_1.0.bb depends upon non-existent task do\_mender\_tar\_src in /home/admins/40012121\_backup/Ti\_AM5708/am57xx-evm/sources/meta-ti/recipes-bsp/u-boot/u-boot-ti-staging\_2019.01.bb ERROR: Command execution failed: 1 @drewmoseley for you ref ---
**Author:** ![vimal](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@vimal](https://hub.mender.io/u/vimal)\ **Post date:** [July 19, 2021, 1:14pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/18 "2021-07-19T13:14:50Z")
Note: Iam set Auto patch Enabled set “1” in u-boot-ti-staging\_2019.01.bbappend MENDER\_UBOOT\_AUTO\_CONFIGURE = “1” ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [July 21, 2021, 11:19am UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/19 "2021-07-21T11:19:26Z")
Try setting ```auto PREFERRED_PROVIDER_u-boot = “u-boot-ti-staging” ``` Drew ---
**Author:** ![vimalltts](https://avatars.discourse-cdn.com/v4/letter/v/e47c2d/32.png) [@vimalltts](https://hub.mender.io/u/vimalltts)\ **Post date:** [July 21, 2021, 3:01pm UTC](https://hub.mender.io/t/am5708-tisdk-mender-add/3874/20 "2021-07-21T15:01:12Z")
Yes I did in Machine/conf/am57xx.conf file added ```auto PREFERRED_PROVIDER_u-boot = “u-boot-ti-staging” ``` After getting below Eror ERROR: ExpansionError during parsing /home/admins/40012121\_backup/Ti\_AM5708/mender-fota/sources/meta-arago/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5\_2019.01.bb- Traceback (most recent call last): bb.data\_smart.ExpansionError: Failure expanding expression ${@mender\_feature\_is\_enabled(“ti-u-boot-2019.01”,“u-boot-mender-helpers.inc”,"",d)} which triggered exception NameError: name ‘mender\_feature\_is\_enabled’ is not defined [Next page](https://hub.mender.io/t/am5708-tisdk-mender-add/3874.md?page=2)