# Use patched version of u-boot Ultrascale+ **URL:** \ **Category:** General Discussions\ **Created:** [August 6, 2021, 6:33am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975 "2021-08-06T06:33:55Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 6, 2021, 6:33am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/1 "2021-08-06T06:33:55Z")
Dear Forum, First of all this is my first topic, so excuse me in advance if I ask a simple question at the wrong place (the perfect fit for a forum 🙂 ). I am trying to integrate Mender on a ZynqMP Ultrascale+. The module we use is produced by Enclustra (XU8+ CG4). As some of you may know, the building process on the Ultrascale+ involves a special flavor of Yocto developed by Xilinx called Petalinux (it is in fact Yocto but with a supplementary layer that masks most of the bitbake operations). (One of) the nice thing(s) of Petalinux is that it uses u-boot as a bootloader. As this is supported by Mender, it should work 🥳 ! However, they created their own flavor of u-boot with a different name u-boot-xlnx. As soon as I try to integrate mender, it complains that we do not provide u-boot but u-boot-xlnx. Could someone point me towards the way to correct for this issue? Thank you, Pi-r ---
**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:** [August 6, 2021, 12:50pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/2 "2021-08-06T12:50:24Z")
Hi @P3Pierre [This link](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot#forks-of-u-boot) should help you out. Drew ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 9, 2021, 6:53am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/3 "2021-08-09T06:53:24Z")
Hi @drewmoseley , Thanks for the tip! I was able to move forward from there. The next issue I have is related to the patching of u-boot (from what I got reading the forum posts, this had to be expected for forked version of u-boot 🙂 ) First of all, I want to boot from an SD attached to the device. When I configure a Petalinux without Mender, I set my rootfs to /dev/mmcblk1p1. From what I read, I have to set a series of variables to ensure that the correct device block is targeted by Mender during the build process: _In my u-boot-xlnx\_%.bbappend:_ > MENDER\_UBOOT\_AUTO\_CONFIGURE=“0” > MENDER\_DTB\_NAME\_FORCE=“image.ub” > MENDER\_STORAGE\_DEVICE\_BASE=“/dev/mmcblk1” > MENDER\_ROOTFS\_PART\_A\_NUMBER=“p2” > MENDER\_ROOTFS\_PART\_B\_NUMBER=“p3” > > BOOTENV\_SIZE = “0x4000” I had to set _MENDER\_ROOTFS\_PART\_A\_NUMBER_ and _MENDER\_ROOTFS\_PART\_B\_NUMBER_ because the build was complaining about finding the correct names. However, even if it worked for one error, I got the exact same error later in another compilation. ‘MENDER\_ROOTFS\_PART\_A\_NUMBER=`get_part_number_from_device /dev/mmcblk0_0`’' What do I do wrong? Thank you in advance for any help!! ---
**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:** [August 9, 2021, 2:02pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/4 "2021-08-09T14:02:31Z")
I think the MENDER\_STORAGE\_DEVICE\_BASE, MENDER\_ROOTFS\_PART\_A\_NUMBER, and MENDER\_ROOTFS\_PART\_B\_NUMBER variables need to be global so should be in your local.conf or in a bbclass that is inherited by your local.conf. Putting it in the u-boot bbappend means that _only_ the U-Boot recipe will see those values but they are needed by other recipes as well. Drew ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 10, 2021, 6:27am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/5 "2021-08-10T06:27:06Z")
@drewmoseley Thanks again for the correction. As suggested elsewhere in the discussion, I put these parameters in my machine file. With all the other modifications I made, I now have this part within my machine file: > INHERIT += “mender-full-ubi” > > MENDER\_FEATURES\_ENABLE\_append = " mender-uboot mender-image-sd" > MENDER\_FEATURES\_DISABLE\_append = " mender-grub mender-image-uefi" > > # Memory card block device location > > # Memory card with 32GiB of storage. > > MENDER\_MTDIDS = “nand0=nand\_mtd” > MENDER\_IS\_ON\_MTDID = “nand\_mtd” > MENDER\_MTDPARTS = “mtdparts=nand\_mtd:0x100000@0x000000(uboot),0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs),-(ubi)” > IMAGE\_FSTYPES\_remove = “mtdimg” > > MENDER\_STORAGE\_DEVICE=“/dev/mmcblk1” > MENDER\_STORAGE\_DEVICE\_BASE=“/dev/mmcblk1p” > MENDER\_STOGE\_TOTAL\_SIZE\_MB = “30436” > MENDER\_ROOTFS\_PART\_A = “${MENDER\_STORAGE\_DEVICE\_BASE}1” > MENDER\_ROOTFS\_PART\_B = “${MENDER\_STORAGE\_DEVICE\_BASE}2” > MENDER\_DATA\_PART = “${MENDER\_STORAGE\_DEVICE\_BASE}3” From my understanding of the log file (log.do\_provide\_mender\_defines), it seems that now I do have an issue with a file that is not present (env/fw\_env.c) from which I extracted these parts: > DEBUG: Executing shell function do\_provide\_mender\_defines > + echo p3-image-dev > + fgrep mender-auto-provided > + true > + fgrep -A8 ‘skip\_chars(char \*s)’ /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/p3-image-dev/1.0-r0/p3-image-dev-1.0/tools/env/fw\_env.c > + fgrep -q ‘if (isblank(_s))’ > **grep: /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/p3-image-dev/1.0-r0/p3-image-dev-1.0/tools/env/fw\_env.c: No such file or directory** > + ‘[’ 0 -eq 0 ‘]’ > ++ expr 16769024 % ‘(’ 8384512 '_’ 2 ‘)’ > + ‘[’ 0 -ne 0 ‘]’ > + ‘[’ 16769024 -gt 16769024 ‘]’ > + ‘[’ -n ‘’ ‘]’ > + false > ++ get\_part\_number\_from\_device /dev/mmcblk1p1 > ++ dev\_base=unknown > ++ case “$1” in > +++ echo /dev/mmcblk1p1 > +++ cut -dk -f2 > +++ cut -dp -f2 > ++ dev\_base=1 > +++ printf %d 1 > ++ part=1 > ++ ‘[’ 0 = 1 ‘]’ > ++ echo 1 > + MENDER\_ROOTFS\_PART\_A\_NUMBER=1 > ++ get\_part\_number\_hex\_from\_device /dev/mmcblk1p1 > +++ get\_part\_number\_from\_device /dev/mmcblk1p1 > +++ dev\_base=unknown > +++ case “$1” in > ++++ echo /dev/mmcblk1p1 > ++++ cut -dk -f2 > ++++ cut -dp -f2 > +++ dev\_base=1 > ++++ printf %d 1 > +++ part=1 > +++ ‘[’ 0 = 1 ‘]’ > +++ echo 1 > ++ part\_dec=1 > +++ printf %X 1 > ++ part\_hex=1 > ++ ‘[’ 0 = 1 ‘]’ > ++ echo 1 > + MENDER\_ROOTFS\_PART\_A\_NUMBER\_HEX=1 From what I read googling for an explanation, this is related to the environment configuration of u-boot. So I guess that I have something else to change but I am a bit lost (again, sorry 😑) as I do not find a solution googling for it… Thank you again for the time you’ll take to read this reply (and hopefully to provide a solution) Pi-r PS: It seems however that the names I provided in the machine file are correctly propagated in the future-but-not-working-yet defines 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:** [August 10, 2021, 1:16pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/6 "2021-08-10T13:16:07Z")
My guess is that is part of the [U-Boot automatic patching](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot#enabling-u-boot-1). Presumably it relies on the contents of that file to determine the actual settings for your board. That may mean that your fork will need to use manual patching. @kacf any comments? Drew ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 10, 2021, 1:27pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/7 "2021-08-10T13:27:31Z")
I already disabled the automatic patching as advised in the u-boot fork part of the documentation… In fact enabling or disabling it doesn’t change the outcome… ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [August 11, 2021, 9:01am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/8 "2021-08-11T09:01:16Z")
Which version of U-Boot is this? Is there a public repository I could look at? ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 11, 2021, 10:40am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/9 "2021-08-11T10:40:09Z")
Hello @kacf, This is the version make by Xilinx. [GitHub - Xilinx/u-boot-xlnx at xilinx-v2020.2](https://github.com/Xilinx/u-boot-xlnx/tree/xilinx-v2020.2) Thank you for your help! ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [August 12, 2021, 11:48am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/10 "2021-08-12T11:48:41Z")
I assume you have followed Mender documentation and put this somewhere: ```auto require recipes-bsp/u-boot/u-boot-mender.inc ``` But is it in the wrong file? It looks like it’s trying to apply U-Boot steps to an image recipe. In which files have you added this? ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 12, 2021, 12:17pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/11 "2021-08-12T12:17:50Z")
Hello @kacf, I put it into my image definition file which is in a dedicated layer for our build… Grrrrr… I’ll move it into the forked bb recipe. Pierre ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 12, 2021, 12:29pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/12 "2021-08-12T12:29:22Z")
Hello again @kacf, It seems that the issue was exactly the one you suggested. The suspicious line was present in two files: 1. In the image file (from a previous attempt and I forgot to remove it) 2. In the recipe for the forked u-boot from xilinx. Once I removed the faulty line, the compilation is starting (still waiting to check that I can reach the end of the process without any issue). Yours, Pierre ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 12, 2021, 1:37pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/13 "2021-08-12T13:37:48Z")
Great! Thanks @kacf, now I can start the compilation. As prescribed in the documentation, I first tried with > MENDER\_UBOOT\_AUTO\_CONFIGURE=“1” But I had an error: > ERROR: u-boot-xlnx-v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0 do\_configure: U-Boot configuration xilinx\_zynqmp\_virt\_defconfig has setting: > CONFIG\_MTDIDS\_DEFAULT=“” > but Mender expects: > CONFIG\_MTDIDS\_DEFAULT=“nand0=nand\_mtd” However, when I looked in > u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/configs/xilinx\_zynqmp\_virt\_defconfig I can see that the patch has been applied: > CONFIG\_ENV\_SIZE=0x8000 > CONFIG\_MTDIDS\_DEFAULT=“nand0=nand\_mtd” > CONFIG\_MTDPARTS\_DEFAULT=“mtdparts=mtdparts=nand\_mtd:0x100000@0x000000(uboot),0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs),-(ubi)” > CONFIG\_ENV\_IS\_IN\_UBI=y > CONFIG\_SYS\_REDUNDAND\_ENVIRONMENT=y > CONFIG\_ENV\_UBI\_PART=“ubi” > CONFIG\_ENV\_UBI\_VOLUME=“u-boot-env-1” > CONFIG\_ENV\_UBI\_VOLUME\_REDUND=“u-boot-env-2” > CONFIG\_BOOTCOUNT\_LIMIT=y > CONFIG\_BOOTCOUNT\_ENV=y and the variable has been correctly set. Therefore, there is certainly something that I am missing. I extracted the patch as explained in the documentation. I has no error doing so and the extracted patch is: > diff -r -u /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/old-src/configs/xilinx\_zynqmp\_virt\_defconfig /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/configs/xilinx\_zynqmp\_virt\_defconfig > — /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/old-src/configs/xilinx\_zynqmp\_virt\_defconfig 2021-08-12 13:16:35.261127648 +0000 > +++ /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/configs/xilinx\_zynqmp\_virt\_defconfig 2021-08-12 13:17:02.182196631 +0000 > @@ -138,3 +138,36 @@ > CONFIG\_SPL\_GZIP=y > CONFIG\_OF\_LIBFDT\_OVERLAY=y > CONFIG\_EFI\_LOADER\_BOUNCE\_BUFFER=y > +CONFIG\_ENV\_SIZE=0x8000 > +CONFIG\_MTDIDS\_DEFAULT=“nand0=nand\_mtd” > +CONFIG\_MTDPARTS\_DEFAULT=“mtdparts=mtdparts=nand\_mtd:0x100000@0x000000(uboot),0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs),-(ubi)” > +# CONFIG\_ENV\_IS\_NOWHERE is not set > +# CONFIG\_ENV\_IS\_IN\_EEPROM is not set > +# CONFIG\_ENV\_IS\_IN\_FAT is not set > +# CONFIG\_ENV\_IS\_IN\_EXT4 is not set > +# CONFIG\_ENV\_IS\_IN\_FLASH is not set > +# CONFIG\_ENV\_IS\_IN\_MMC is not set > +# CONFIG\_ENV\_IS\_IN\_NAND is not set > +# CONFIG\_ENV\_IS\_IN\_NVRAM is not set > +# CONFIG\_ENV\_IS\_IN\_ONENAND is not set > +# CONFIG\_ENV\_IS\_IN\_REMOTE is not set > +# CONFIG\_ENV\_IS\_IN\_SPI\_FLASH is not set > +CONFIG\_MTD\_UBI=y > +CONFIG\_ENV\_IS\_IN\_UBI=y > +CONFIG\_SYS\_REDUNDAND\_ENVIRONMENT=y > +CONFIG\_ENV\_UBI\_PART=“ubi” > +CONFIG\_ENV\_UBI\_VOLUME=“u-boot-env-1” > +CONFIG\_ENV\_UBI\_VOLUME\_REDUND=“u-boot-env-2” > +CONFIG\_CMD\_UBIFS=y > +CONFIG\_MTD\_PARTITIONS=y > +# CONFIG\_BOOTCOUNT\_GENERIC is not set > +# CONFIG\_BOOTCOUNT\_EXT is not set > +# CONFIG\_BOOTCOUNT\_AM33XX is not set > +# CONFIG\_BOOTCOUNT\_RAM is not set > +# CONFIG\_BOOTCOUNT\_I2C is not set > +# CONFIG\_BOOTCOUNT\_AT91 is not set > +# CONFIG\_BOOTCOUNT\_BOOTLIMIT is not set > +# CONFIG\_BOOTCOUNT\_ALEN is not set > +CONFIG\_BOOTCOUNT\_LIMIT=y > +CONFIG\_BOOTCOUNT\_ENV=y > +# CONFIG\_BOOTCOMMAND is not set > Binary files /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/old-src/.git/index and /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/.git/index differ > diff -r -u /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/old-src/include/config\_defaults.h /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/include/config\_defaults.h > — /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/old-src/include/config\_defaults.h 2021-08-12 13:16:35.362127907 +0000 > +++ /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/include/config\_defaults.h 2021-08-12 13:17:02.008196185 +0000 > @@ -10,3 +10,5 @@ > #define _CONFIG\_DEFAULTS\_H_ > > #endif > +#define MTDIDS\_DEFAULT CONFIG\_MTDIDS\_DEFAULT > +#define MTDPARTS\_DEFAULT CONFIG\_MTDPARTS\_DEFAULT > diff -r -u /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/old-src/include/config\_distro\_bootcmd.h /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/include/config\_distro\_bootcmd.h > — /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/old-src/include/config\_distro\_bootcmd.h 2021-08-12 13:16:35.362127907 +0000 > +++ /home/pdaye/workspace/P3Lab/build/p3lab\_builder/petalinux/projects/p3-uz4cg\_kol\_2020.2/build/tmp/work/uz4cg\_kol-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.2+gitAUTOINC+bb4660c33a-r0/git/include/config\_distro\_bootcmd.h 2021-08-12 13:17:02.013196198 +0000 > @@ -486,7 +486,6 @@ > “done\0” > > #ifndef CONFIG\_BOOTCOMMAND > -#define CONFIG\_BOOTCOMMAND “run distro\_bootcmd” > #endif > > #endif /\* \_CONFIG\_CMD\_DISTRO\_BOOTCMD\_H \*/ I hope that this will help someone finds the issue! Thanks again for the very nice support! Pierre ---
**Author:** ![P3Pierre](https://avatars.discourse-cdn.com/v4/letter/p/a4c791/32.png) [@P3Pierre](https://hub.mender.io/u/P3Pierre)\ **Post date:** [August 26, 2021, 8:51am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/14 "2021-08-26T08:51:33Z")
@kacf @drewmoseley no Idea on the reason why I have this issue? ---
**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:** [August 26, 2021, 12:51pm UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/15 "2021-08-26T12:51:45Z")
No idea here. Sorry. ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [August 27, 2021, 6:43am UTC](https://hub.mender.io/t/use-patched-version-of-u-boot-ultrascale/3975/16 "2021-08-27T06:43:25Z")
This is a long shot, but could you try removing [this](https://github.com/mendersoftware/meta-mender/blob/dunfell-v2021.07/meta-mender-core/recipes-bsp/u-boot/files/uboot_auto_patch.sh#L370-L380) and [this](https://github.com/mendersoftware/meta-mender/blob/dunfell-v2021.07/meta-mender-core/recipes-bsp/u-boot/files/uboot_auto_patch.sh#L428-L430). I’m working on support for post-dunfell branches, and more recent versions of U-Boot do not work with this section. The reason I say it’s a long shot is that I would only expect this problem on v2020.10 and newer, but you never know.