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\00T\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}
#####
** Attachment added: "IMG_1959.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1680605/+attachment/4858922/+files/IMG_1959.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680605
Title:
boot fails after upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1680605/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
