Thanks for the excellent work on the BBB builds.

I'm following:
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Mainline

Applying the patches results in several hunks failing:

pushd /src/u-boot
$ patch -p1 < 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch 
patching file arch/arm/include/asm/arch-am33xx/hardware_am33xx.h
patching file arch/arm/include/asm/arch-am33xx/sys_proto.h
patching file arch/arm/mach-omap2/am33xx/board.c
Hunk #1 succeeded at 394 (offset 11 lines).
patching file arch/arm/mach-omap2/am33xx/clock_am33xx.c
patching file arch/arm/mach-omap2/hwinit-common.c
Hunk #1 succeeded at 133 (offset 1 line).
patching file board/ti/am335x/board.c
Hunk #1 succeeded at 33 (offset 5 lines).
Hunk #2 succeeded at 91 (offset 6 lines).
Hunk #3 succeeded at 275 (offset 6 lines).
Hunk #4 succeeded at 306 (offset 6 lines).
Hunk #5 succeeded at 358 (offset 6 lines).
Hunk #6 succeeded at 495 (offset 6 lines).
Hunk #7 succeeded at 569 (offset 6 lines).
Hunk #8 succeeded at 712 (offset 6 lines).
Hunk #9 succeeded at 863 (offset 7 lines).
Hunk #10 succeeded at 873 (offset 7 lines).
Hunk #11 FAILED at 1043.
Hunk #12 FAILED at 1065.
Hunk #13 succeeded at 1017 (offset -92 lines).
2 out of 13 hunks FAILED -- saving rejects to file board/ti/am335x/board.c.rej
patching file board/ti/am335x/board.h
patching file board/ti/am335x/mux.c
Hunk #2 FAILED at 92.
Hunk #3 succeeded at 123 (offset 4 lines).
Hunk #4 succeeded at 315 (offset 4 lines).
Hunk #5 succeeded at 368 (offset 4 lines).
Hunk #6 succeeded at 383 (offset 4 lines).
Hunk #7 FAILED at 415.
Hunk #8 succeeded at 428 (offset 3 lines).
2 out of 8 hunks FAILED -- saving rejects to file board/ti/am335x/mux.c.rej
patching file configs/am335x_evm_defconfig
Hunk #1 FAILED at 4.
1 out of 1 hunk FAILED -- saving rejects to file configs/am335x_evm_defconfig.rej
patching file env/common.c
Hunk #1 succeeded at 206 (offset 5 lines).
Hunk #2 succeeded at 221 (offset 5 lines).
patching file include/configs/am335x_evm.h
Hunk #1 succeeded at 52 (offset -6 lines).
Hunk #2 succeeded at 88 (offset -6 lines).
Hunk #3 succeeded at 104 (offset -6 lines).
Hunk #4 succeeded at 134 (offset -6 lines).
Hunk #5 succeeded at 203 (offset -6 lines).
Hunk #6 succeeded at 218 (offset -6 lines).
patching file include/configs/ti_armv7_common.h
Hunk #1 succeeded at 114 (offset 12 lines).
patching file include/environment/ti/mmc.h
Hunk #2 succeeded at 89 with fuzz 1.

What is the purpose of these patches? Seems like they are adding support for capes and different boot modes.

Context

I am trying to build my own BBB image. I started with using u-boot v2021.04 and it booted quite fine. As I am trying to get the CTAG-2.4 cape to work, I am wondering if I need to apply something like these patches? Following this guide I tried to use v2019.04, but had no success:

Are there any plans to release a patch for v2021.04, etc. ?

The u-boot SPL working in falcon mode after flashing it using dfu-util and then reset the board, but when the board is set ON, the u-boot SPL showing following message and after 7 seconds the board automatically powering off.

U-Boot SPL 2019.07-rc4-dirty (Mar 27 2020 - 01:04:53 +0430)

DRA752-GP ES2.0

Trying to boot from MMC2_2

no pinctrl state for default mode

no pinctrl state for default mode

Loading Environment from MMC... OK

If I press c and set ON the board, it goes to u-boot and the board state is stable.
How to fix it?

I have a cape that I would like to use with capemanager disabled. I have the appropriate am335x-boneblack-evb.dtb file working the way I want. I would like to be able to just set cape=evb in /uEnv.txt. This worked on 2015.01 if the file was at /dtbs/am335x-boneblack-evb.dtb. On 2016.01, fdtdir is no longer set to a default value, so the file has to be at /am335x-boneblack-evb.dtb. So, question 1: Was this change intentional?

Later on, in uname_boot, it looks for fdtfile in about 7 different places. It seems like the search for ${fdtbase}-${cape}.dtb ought to be looking in all of these same places instead of just one place.

Question 2: Is this a reasonable thing to do or am I going about this all wrong?

Following the instructions here:
https://www.digikey.com/eewiki/display/linuxonarm/SAMA5D27-SOM1-EK1#SAMA5D27-SOM1-EK1-InstallBootloader

Section: Bootloader: U-Boot
Got both sets of patches and applied patches.

make ARCH=arm CROSS_COMPILE=${CC} sama5d27_som1_ek_mmc_defconfig

Fails:
make ARCH=arm CROSS_COMPILE=${CC} sama5d27_som1_ek_mmc_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
YACC scripts/kconfig/zconf.tab.c
/bin/sh: 1: bison: not found
scripts/Makefile.lib:226: recipe for target 'scripts/kconfig/zconf.tab.c' failed
make[1]: *** [scripts/kconfig/zconf.tab.c] Error 127
Makefile:516: recipe for target 'sama5d27_som1_ek_mmc_defconfig' failed
make: *** [sama5d27_som1_ek_mmc_defconfig] Error 2

Any idea how to fix this?

scripts/kconfig/zconf.tab.c doesn't exist.
Only zconf.l zconf.y in kconfig dir.

I'm following:
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black

I've patched successfuly (a git library command peculiarity meant git was checking out master instead of 2019.04 when I reported issue #11).

However, I now encounter the following error:

$ make ARCH=arm CROSS_COMPILE=${CC}

<snip>

scripts/Makefile.build:278: recipe for target 'board/ti/am335x/board.o' failed
Makefile:1531: recipe for target 'board/ti/am335x' failed
STDERR: In file included from include/post.h:15:0,
                 from include/serial.h:4,
                 from board/ti/am335x/board.c:14:
 board/ti/am335x/board.c: In function ‘board_init’:
board/ti/am335x/board.c:756:22: error: ‘RTC_OSC’ undeclared (first use in this function)
  sys_rtc_osc = readl(RTC_OSC);

There seems to be a bug in u-boot 2016.01. When I run printenv, I see the following (formatted for readability):

...
bootcmd=
    run findfdt; 
    setenv fdtfile am335x-boneblack.dtb;
    setenv fdtbase am335x-boneblack; 
    run distro_bootcmd
...
findfdt=
    if test $board_name = A335BONE; then 
        setenv fdtfile am335x-bone.dtb; 
        setenv fdtbase am335x-bone; 
    fi; 
    if test $board_name = A335BNLT; then 
        if test $board_rev = BBG1; then 
            setenv fdtfile am335x-bonegreen.dtb; 
            setenv fdtbase am335x-bonegreen; 
        elif test $board_rev = AIA0; then 
            setenv fdtfile am335x-abbbi.dtb; 
            setenv fdtbase am335x-abbbi; 
        else 
            setenv fdtfile am335x-boneblack.dtb; 
            setenv fdtbase am335x-boneblack; 
        fi; 
    fi; 
    if test $board_name = A33515BB; then 
        setenv fdtfile am335x-evm.dtb; 
    fi; 
    if test $board_name = A335X_SK; then 
        setenv fdtfile am335x-evmsk.dtb; 
    fi; 
    if test $fdtfile = undefined; then 
        echo WARNING: Could not determine device tree to use; 
    fi;

These are they only places that findfdt are used, so it looks like when run bootcmd is called the values found in findfdt are immediately written over with am335x-boneblack. I only have a BeagleBone Black, so I can't confirm this for sure.

Hi, Robert Nelson:

I'm just wondering how are you able to find those patches out?
Let's take this as an example:
"0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch"

You need to be very familiar with u-boot first, and then you must be very familiar with beaglebone-black board. After that, you have a chance to give out the above patch, and the patches modified two files:
patching file include/configs/am335x_evm.h
patching file include/configs/ti_armv7_common.h

So, Nelson, can you please suggest a way on how to provide a patch of u-boot, to a specific board??

Cheers
Pei

I can't seem to find a license for these patches. Was looking to use these in a commercial project, just wondering if there is a license for these.

Hi,

I was wondering if it is possible (as with AM335x) for AM5728 to compile a SPL that support network fetch of u-boot.img;

I did it with AM335x adding to file include/configs/ti_am335x_common.h:

define CONFIG_SPL_ETH_SUPPORT

define CONFIG_SPL_NET_SUPPORT

but I did not have success with AM5728 applying the same recipe on include/configs/am57xx_evm.h

I'm using ti-u-boot-2016.05 with this patch:

https://rcn-ee.com/repos/git/u-boot-patches/ti-2016.05/0001-beagle_x15-uEnv.txt-bootz-n-fixes.patch

I also launch these make to build U-Boot:

make ARCH=arm CROSS_COMPILE=${CC} distclean
make ARCH=arm CROSS_COMPILE=${CC} am57xx_evm_config
make ARCH=arm CROSS_COMPILE=${CC}

Thanks in advance,
Gennaro

is it possible password protected uboot login for security reason..??

This was for u-boot-2010.03!!!

https://dl.dropboxusercontent.com/u/22522783/0001-mx23_olinuxino-uEnv.txt-bootz-n-fixes-v2.patch

load command is not known..