U-Boot ignores uEnv.txt

Hemant · August 15, 2021, 9:12am

Hello All,

I took latest U-Boot and created my own uEnv.txt so that it mounts RFS from NFS.
But is seems that it ignores uEnv.txt.

When I load the uEnv.txt manually as below:

load mmc 0:1 0x80800000 uEnv.txt
env import -t 0x80800000 459

then it works.

If I let u-boot run then below is the output

U-Boot 2021.10-rc1-00275-g3823315cbe (Aug 15 2021 - 09:42:20 +0100)

CPU : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
WDT: Started with servicing (60s timeout)
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT… OK
Net: eth2: ethernet@4a100000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@48060000.blk…
Scanning disk mmc@481d8000.blk…
** Unrecognized filesystem type **
Found 6 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1…
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
BootOrder not defined
EFI boot manager: Cannot load any image

Error: “bootcmd_nand0” not defined

starting USB…
No working controllers found
USB is stopped. Please issue ‘usb start’ first.
starting USB…
No working controllers found
link up on port 0, speed 100, full duplex

Please let me know what I am missing.

RobertCNelson · August 15, 2021, 3:23pm

A post was split to a new topic: BBBW regulator

RobertCNelson · August 15, 2021, 3:21pm

That’s expected after…

Docs,

github.com

u-boot/u-boot/blob/master/doc/README.distro

SPDX-License-Identifier: GPL-2.0+
/*
 * (C) Copyright 2014 Red Hat Inc.
 * Copyright (c) 2014-2015, NVIDIA CORPORATION.  All rights reserved.
 * Copyright (C) 2015 K. Merker <merker@debian.org>
 */

Generic Distro Configuration Concept
====================================

Linux distributions are faced with supporting a variety of boot mechanisms,
environments or bootloaders (PC BIOS, EFI, U-Boot, Barebox, ...). This makes
life complicated. Worse, bootloaders such as U-Boot have a configurable set
of features, and each board chooses to enable a different set of features.
Hence, distros typically need to have board-specific knowledge in order to
set up a bootable system.

This document defines a common set of U-Boot features that are required for
a distro to support the board in a generic fashion. Any board wishing to
allow distros to install and boot in an out-of-the-box fashion should enable

This file has been truncated. show original

use

/extlinux/extlinux.conf
/boot/extlinux/extlinux.conf

Regards,