[U-Boot] Unable to saveenv to MMC

[Heinrich Schuchardt]

On 12/6/18 7:12 PM, Robin Polak wrote:
> Hello.
> 
>   I'm having trouble persisting my environment variables to the SD Card
> onto which I have FAT formatted and then written U-Boot to using the
> following command:
> 
> sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/disk2 bs=1024 seek=8
> 
> I get the following error when booting a Linksprite_pcDuino3_Nano with the
> SD Card I've built:
> 
> U-Boot SPL 2018.11 (Dec 06 2018 - 17:57:48 +0000)
> DRAM: 1024 MiB
> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> Trying to boot from MMC1
> 
> 
> U-Boot 2018.11 (Dec 06 2018 - 17:57:48 +0000) Allwinner Technology
> 
> CPU:   Allwinner A20 (SUN7I)
> Model: LinkSprite pcDuino3 Nano
> I2C:   ready
> DRAM:  1 GiB
> MMC:   SUNXI SD/MMC: 0
> Loading Environment from FAT... Unable to use mmc 0:0... In:    serial
> Out:   serial
> Err:   serial
> SCSI:  SATA link 0 timeout.
> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> flags: ncq stag pm led clo only pmp pio slum part ccc apst
> 
> Net:   eth0: ethernet at 1c50000
> starting USB...
> USB0:   USB EHCI 1.00
> USB1:   USB OHCI 1.0
> USB2:   USB EHCI 1.00
> USB3:   USB OHCI 1.0
> scanning bus 0 for devices... 1 USB Device(s) found
> scanning bus 2 for devices... 1 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> => saveenv
> Saving Environment to FAT... Unable to use mmc 0:0... Failed (1)

Partitions are numbered from 1. So partition 1 would be mmc 0:1.

mmc 0:0 would require that there is no partition table and the FAT file
system starts in block 0.

Please, check the value of CONFIG_ENV_FAT_DEVICE_AND_PART in your
configuration. The default is CONFIG_ENV_FAT_DEVICE_AND_PART="0:auto"

With "auto" function blk_get_device_part_str() looks for the first
partition that has the bootable flag set.

So to analyze your problem further please look at the output of

sudo fdisk -l /dev/<your_SD_card>

assuming that you use a DOS partition table.

Best regards

Heinrich

> 
> Thank you for any light that may be shed upon this error.
>