Comment 4 for bug 1680605

No, it's not a exactly a duplicate.

As you can see in the picture, it gets an error after reading boot.scr

If I look into the content of the boot.scr the fdt_addr_r is set.

So my guess is it should be fairly simple to fix once it's properly setting/reading the environment variable.

#####boot.scr
'V\86\9C\00PX\EA)\D2\00\00
\\00\00\00\00\00\00\00\00oH+\FD\00boot script\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00
T\00\00\00\00setenv fdt_addr_r 0x02008000
fdt addr ${fdt_addr_r}
fdt get value bootargs /chosen bootargs
setenv kernel_addr_r 0x01000000
setenv ramdisk_addr_r 0x02100000
fatload mmc 0:1 ${kernel_addr_r} vmlinuz
fatload mmc 0:1 ${ramdisk_addr_r} initrd.img
setenv initrdsize $filesize
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${initrdsize} ${fdt_addr_r}
#####