1. Noavatar

    Thomas 2018-04-24 13:05

    Instead of setting the bootcmd to whatever you are booting to like this for mmc:

    Marvell>> setenv bootcmd 'mmc dev 1; ext4load mmc 1:1 $kernel_addr $image_name;ext4load mmc 1:1 $fdt_addr $fdt_name;setenv bootargs $console root=/dev/mmcblk1p1 rw rootwait; booti $kernel_addr - $fdt_addr'
    Marvell>> save

    it is better to set the bootcmd to just run your already created bootmmc / bootusb etc.

    Marvell>> setenv bootcmd 'run bootmmc'

    I also had to use a different save commend for it to save, dont know if that is for my board or all boards:

    Marvell>> saveenv
    1. akrog 2018-04-25 11:48

      Thanks Thomas for the feedback, your suggestions have been added.