When increasing #define CONFIG_ENV_SIZE 0x2000
to #define CONFIG_ENV_SIZE 0x20000
and updating u-boot in the eMMC using run setupdate
+ run update_uboot
and poweroff/on it hangs up right after boot:
U-Boot 2016.11-00006-gfc72714-dirty (Jan 31 2017 - 13:01:55 +0100)
TEGRA124
DRAM: 2 GiB
MMC: Tegra SD/MMC: 0, Tegra SD/MMC: 1, Tegra SD/MMC: 2
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
When u-boot is run in the recovery mode from RAM it runs properly and boots into Ubuntu.
When the same u-boot configuration is build with #define CONFIG_ENV_SIZE 0x2000
it does also boot properly into Ubuntu from eMMC (not RAM):
U-Boot 2016.11-00006-gfc72714-dirty (Jan 31 2017 - 15:31:15 +0100)
TEGRA124
DRAM: 2 GiB
MMC: Tegra SD/MMC: 0, Tegra SD/MMC: 1, Tegra SD/MMC: 2
In: serial
Out: serial
Err: serial
Model: Toradex Apalis TK1 2GB V1.1A, Serial# 02864547
Net: No ethernet found.
Hit any key to stop autoboot: 0
Booting from internal eMMC chip...
Unknown command 'dtbparam' - try 'help'
49735 bytes read in 155 ms (312.5 KiB/s)
5471848 bytes read in 387 ms (13.5 MiB/s)
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-3.10.40-v2.7b1+g19722d4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5471784 Bytes = 5.2 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 82000000
Booting using the fdt blob at 0x82000000
Loading Kernel Image ... OK
Using Device Tree in place at 82000000, end 8200f246
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.10.40-v2.7b1+g19722d4 (linuxdev@linuxdev.toradex7
[ 0.000000] ...
Where did I missed to consider the increased environment size? (I did not change the partitioning until and inclusive the vfat partition. I appended 2 other partitions after the rootfs partition of the original apalis image.)
BTW: How do I get rid of this ugly -00006-gfc72714-dirty
appended to the u-boot identification?