Re: [U-Boot] Odroid U3 - Upgrade to latest u-boot kernel load fails.
Hi Krzysztof,
On Tue, 19 Mar 2019 at 01:54, Anand Moon wrote:
>
> Hi Krzysztof,
>
> On Mon, 18 Mar 2019 at 23:33, Krzysztof Kozlowski wrote:
> >
> > On Mon, 18 Mar 2019 at 18:49, Anand Moon wrote:
> > >
> > > Hi Krzysztof,
> > >
> > > On Mon, 18 Mar 2019 at 18:20, Krzysztof Kozlowski wrote:
> > > >
> > > > On Mon, 18 Mar 2019 at 13:32, Anand Moon wrote:
> > > > >
> > > > > Hi Krzysztof / Marek,
> > > > >
> > > > > After I update the latest u-boot on my Odroud U3+ it fails to load the
> > > > > kernel it hangs.
> > > > > I am using Archlinux on Odroid U3.
> > > > >
> > > > > U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 12:12:23
> > > > > +)
> > > > >
> > > > > CPU: Exynos4412 @ 1 GHz
> > > > > Model: Odroid based on Exynos4412
> > > > > Type: u3
> > > > > DRAM: 2 GiB
> > > > > LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
> > > > > LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
> > > > > LDO21@TFLASH_2.8V: set 280 uV; enabling
> > > > > MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
> > > > > Loading Environment from MMC... Card did not respond to voltage
> > > > > select!
> > > > > *** Warning - No block device, using default environment
> > > > >
> > > > > Net: No ethernet found.
> > > > > Hit any key to stop autoboot: 0
> > > > > switch to partitions #0, OK
> > > > > mmc1 is current device
> > > > > Scanning mmc 1:1...
> > > > > Found U-Boot script /boot/boot.scr
> > > > > 769 bytes read in 6 ms (125 KiB/s)
> > > > > ## Executing script at 4200
> > > > > 6901856 bytes read in 253 ms (26 MiB/s)
> > > > > 53078 bytes read in 19 ms (2.7 MiB/s)
> > > > > 6590950 bytes read in 240 ms (26.2 MiB/s)
> > > > > Kernel image @ 0x4100 [ 0x00 - 0x695060 ]
> > > > > ## Flattened Device Tree blob at 4080
> > > > >Booting using the fdt blob at 0x4080
> > > > >Loading Ramdisk to 4f9b6000, end 41e6 ... OK
> > > > >Loading Device Tree to 4f9a6000, end 4f9b5f55 ... OK
> > > > >
> > > > > Starting kernel ...
> > > >
> > > > Can you attach your boot.init file (the source of boot.scr)?
> > > >
> > > > By the size of DTB you can see that different DTB is loaded. I assume
> > > > you tried to boot the same kernel, then it could mean that boardname
> > > > was used instead of board_name to choose DTB. Suspicious is that
> > > > kernel size also differs... so maybe you booted something else? As
> > > > usual debugging practice, reduce number of unknown factors. Do not
> > > > change kernel and U-Boot at the same time.
> > > >
> > > > Also, you can try reverting commit e6b1467081d3 ("arm: exynos: Remove
> > > > duplicated "boardname" env setting") and see if it helps. Or just try
> > > > to bisect around changes coming from u-boot samsung tree. Try booting
> > > > v2019.01 and paste the results as well.
> > > >
> > > > Best regards,
> > > > Krzysztof
> > > >
> > >
> > > I have tested with pre-compiled image and the cross compiled kernel image
> > > both failed to load the kernel.
> > >
> > > No revert of the commit e6b1467081d3 did not help.
> > >
> > > Yes it seem strange that that load address is changes some how in the
> > > u-boot env
> > >
> > > printenv setting of the latest u-boot U-Boot
> > > 2019.04-rc3-00131-g8303467e80d-dirty
> > > [0] https://pastebin.com/1Hgc5xxC (newu-boot.txt)
> > >
> > > printenv setting for the old u-boot. U-Boot 2018.01-1
> > > [1] https://pastebin.com/wD6zK6eG(oldu-boot.txt)
> > >
> > > Attach is the boot.txt (boot.scr), also the u-boot env old and u-boot-env
> > > new
> >
> > And does 2019.01 work?
> >
> > Krzysztof
>
> It looks like Archlinux uboot for Odroid U3 set some extra environment
> variable to make this work.
>
> [0]
> https://github.com/archlinuxarm/PKGBUILDs/blob/master/alarm/uboot-odroid/0001-Convert-odroid-to-use-distro_bootcmd.patch
> [1]
> https://github.com/archlinuxarm/PKGBUILDs/blob/master/alarm/uboot-odroid/0002-odroid-x-support.patch
>
> I gave these patches a try but no success
>
> Best Regards
> -Anand
If found out the commit that break the boot on Odroid U3
Revert of below commit breaks the booting of the kernel.
From: Seung-Woo Kim
Date: Tue, 20 Nov 2018 14:54:39 +0900
Subject: [PATCH] Revert "arm: config: fix default console only to specify the
device"
This reverts commit 232ed3ca534708527a9515c7c41bc3542949525c.
In exynos boards, ${console} is used to set bootargs but it sets
without "console=", so CONFIG_DEFAULT_CONSOLE for these boards is
designated with "console=" but it is removed. So revert the commit.
References for using ${console} in
board/samsung/common/bootscripts/autoboot.cmd
board/samsung/common/bootscripts/bootzimg.cmd
Please let me know it how to resolve this issue.
Best Regards
-Anand
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Odroid U3 - Upgrade to latest u-boot kernel load fails.
Hi Krzysztof,
On Mon, 18 Mar 2019 at 23:33, Krzysztof Kozlowski wrote:
>
> On Mon, 18 Mar 2019 at 18:49, Anand Moon wrote:
> >
> > Hi Krzysztof,
> >
> > On Mon, 18 Mar 2019 at 18:20, Krzysztof Kozlowski
wrote:
> > >
> > > On Mon, 18 Mar 2019 at 13:32, Anand Moon
wrote:
> > > >
> > > > Hi Krzysztof / Marek,
> > > >
> > > > After I update the latest u-boot on my Odroud U3+ it fails to load
the
> > > > kernel it hangs.
> > > > I am using Archlinux on Odroid U3.
> > > >
> > > > U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 12:12:23
+)
> > > >
> > > > CPU: Exynos4412 @ 1 GHz
> > > > Model: Odroid based on Exynos4412
> > > > Type: u3
> > > > DRAM: 2 GiB
> > > > LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
> > > > LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
> > > > LDO21@TFLASH_2.8V: set 280 uV; enabling
> > > > MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
> > > > Loading Environment from MMC... Card did not respond to voltage
select!
> > > > *** Warning - No block device, using default environment
> > > >
> > > > Net: No ethernet found.
> > > > Hit any key to stop autoboot: 0
> > > > switch to partitions #0, OK
> > > > mmc1 is current device
> > > > Scanning mmc 1:1...
> > > > Found U-Boot script /boot/boot.scr
> > > > 769 bytes read in 6 ms (125 KiB/s)
> > > > ## Executing script at 4200
> > > > 6901856 bytes read in 253 ms (26 MiB/s)
> > > > 53078 bytes read in 19 ms (2.7 MiB/s)
> > > > 6590950 bytes read in 240 ms (26.2 MiB/s)
> > > > Kernel image @ 0x4100 [ 0x00 - 0x695060 ]
> > > > ## Flattened Device Tree blob at 4080
> > > >Booting using the fdt blob at 0x4080
> > > >Loading Ramdisk to 4f9b6000, end 41e6 ... OK
> > > >Loading Device Tree to 4f9a6000, end 4f9b5f55 ... OK
> > > >
> > > > Starting kernel ...
> > >
> > > Can you attach your boot.init file (the source of boot.scr)?
> > >
> > > By the size of DTB you can see that different DTB is loaded. I assume
> > > you tried to boot the same kernel, then it could mean that boardname
> > > was used instead of board_name to choose DTB. Suspicious is that
> > > kernel size also differs... so maybe you booted something else? As
> > > usual debugging practice, reduce number of unknown factors. Do not
> > > change kernel and U-Boot at the same time.
> > >
> > > Also, you can try reverting commit e6b1467081d3 ("arm: exynos: Remove
> > > duplicated "boardname" env setting") and see if it helps. Or just try
> > > to bisect around changes coming from u-boot samsung tree. Try booting
> > > v2019.01 and paste the results as well.
> > >
> > > Best regards,
> > > Krzysztof
> > >
> >
> > I have tested with pre-compiled image and the cross compiled kernel
image
> > both failed to load the kernel.
> >
> > No revert of the commit e6b1467081d3 did not help.
> >
> > Yes it seem strange that that load address is changes some how in the
u-boot env
> >
> > printenv setting of the latest u-boot U-Boot
> > 2019.04-rc3-00131-g8303467e80d-dirty
> > [0] https://pastebin.com/1Hgc5xxC (newu-boot.txt)
> >
> > printenv setting for the old u-boot. U-Boot 2018.01-1
> > [1] https://pastebin.com/wD6zK6eG(oldu-boot.txt)
> >
> > Attach is the boot.txt (boot.scr), also the u-boot env old and
u-boot-env new
>
> And does 2019.01 work?
>
> Krzysztof
It looks like Archlinux uboot for Odroid U3 set some extra environment
variable to make this work.
[0]
https://github.com/archlinuxarm/PKGBUILDs/blob/master/alarm/uboot-odroid/0001-Convert-odroid-to-use-distro_bootcmd.patch
[1]
https://github.com/archlinuxarm/PKGBUILDs/blob/master/alarm/uboot-odroid/0002-odroid-x-support.patch
I gave these patches a try but no success 樂
Best Regards
-Anand
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Odroid U3 - Upgrade to latest u-boot kernel load fails.
Hi Krzysztof,
On Mon, 18 Mar 2019 at 23:33, Krzysztof Kozlowski wrote:
>
> On Mon, 18 Mar 2019 at 18:49, Anand Moon wrote:
> >
> > Hi Krzysztof,
> >
> > On Mon, 18 Mar 2019 at 18:20, Krzysztof Kozlowski wrote:
> > >
> > > On Mon, 18 Mar 2019 at 13:32, Anand Moon wrote:
> > > >
> > > > Hi Krzysztof / Marek,
> > > >
> > > > After I update the latest u-boot on my Odroud U3+ it fails to load the
> > > > kernel it hangs.
> > > > I am using Archlinux on Odroid U3.
> > > >
> > > > U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 12:12:23
> > > > +)
> > > >
> > > > CPU: Exynos4412 @ 1 GHz
> > > > Model: Odroid based on Exynos4412
> > > > Type: u3
> > > > DRAM: 2 GiB
> > > > LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
> > > > LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
> > > > LDO21@TFLASH_2.8V: set 280 uV; enabling
> > > > MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
> > > > Loading Environment from MMC... Card did not respond to voltage select!
> > > > *** Warning - No block device, using default environment
> > > >
> > > > Net: No ethernet found.
> > > > Hit any key to stop autoboot: 0
> > > > switch to partitions #0, OK
> > > > mmc1 is current device
> > > > Scanning mmc 1:1...
> > > > Found U-Boot script /boot/boot.scr
> > > > 769 bytes read in 6 ms (125 KiB/s)
> > > > ## Executing script at 4200
> > > > 6901856 bytes read in 253 ms (26 MiB/s)
> > > > 53078 bytes read in 19 ms (2.7 MiB/s)
> > > > 6590950 bytes read in 240 ms (26.2 MiB/s)
> > > > Kernel image @ 0x4100 [ 0x00 - 0x695060 ]
> > > > ## Flattened Device Tree blob at 4080
> > > >Booting using the fdt blob at 0x4080
> > > >Loading Ramdisk to 4f9b6000, end 41e6 ... OK
> > > >Loading Device Tree to 4f9a6000, end 4f9b5f55 ... OK
> > > >
> > > > Starting kernel ...
> > >
> > > Can you attach your boot.init file (the source of boot.scr)?
> > >
> > > By the size of DTB you can see that different DTB is loaded. I assume
> > > you tried to boot the same kernel, then it could mean that boardname
> > > was used instead of board_name to choose DTB. Suspicious is that
> > > kernel size also differs... so maybe you booted something else? As
> > > usual debugging practice, reduce number of unknown factors. Do not
> > > change kernel and U-Boot at the same time.
> > >
> > > Also, you can try reverting commit e6b1467081d3 ("arm: exynos: Remove
> > > duplicated "boardname" env setting") and see if it helps. Or just try
> > > to bisect around changes coming from u-boot samsung tree. Try booting
> > > v2019.01 and paste the results as well.
> > >
> > > Best regards,
> > > Krzysztof
> > >
> >
> > I have tested with pre-compiled image and the cross compiled kernel image
> > both failed to load the kernel.
> >
> > No revert of the commit e6b1467081d3 did not help.
> >
> > Yes it seem strange that that load address is changes some how in the
> > u-boot env
> >
> > printenv setting of the latest u-boot U-Boot
> > 2019.04-rc3-00131-g8303467e80d-dirty
> > [0] https://pastebin.com/1Hgc5xxC (newu-boot.txt)
> >
> > printenv setting for the old u-boot. U-Boot 2018.01-1
> > [1] https://pastebin.com/wD6zK6eG(oldu-boot.txt)
> >
> > Attach is the boot.txt (boot.scr), also the u-boot env old and u-boot-env
> > new
>
> And does 2019.01 work?
I have not tied this version.
>
> Krzysztof
I have flashed the latest Archlinux Image for Odroid U3 on the sdcard.
did full update on the kernel image and then tried to update the latest u-boot
it failed to boot. It looks like the some u-boot environment settings
are incorrect.
Best Regards
-Anand
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Odroid U3 - Upgrade to latest u-boot kernel load fails.
On Mon, 18 Mar 2019 at 18:49, Anand Moon wrote:
>
> Hi Krzysztof,
>
> On Mon, 18 Mar 2019 at 18:20, Krzysztof Kozlowski wrote:
> >
> > On Mon, 18 Mar 2019 at 13:32, Anand Moon wrote:
> > >
> > > Hi Krzysztof / Marek,
> > >
> > > After I update the latest u-boot on my Odroud U3+ it fails to load the
> > > kernel it hangs.
> > > I am using Archlinux on Odroid U3.
> > >
> > > U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 12:12:23 +)
> > >
> > > CPU: Exynos4412 @ 1 GHz
> > > Model: Odroid based on Exynos4412
> > > Type: u3
> > > DRAM: 2 GiB
> > > LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
> > > LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
> > > LDO21@TFLASH_2.8V: set 280 uV; enabling
> > > MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
> > > Loading Environment from MMC... Card did not respond to voltage select!
> > > *** Warning - No block device, using default environment
> > >
> > > Net: No ethernet found.
> > > Hit any key to stop autoboot: 0
> > > switch to partitions #0, OK
> > > mmc1 is current device
> > > Scanning mmc 1:1...
> > > Found U-Boot script /boot/boot.scr
> > > 769 bytes read in 6 ms (125 KiB/s)
> > > ## Executing script at 4200
> > > 6901856 bytes read in 253 ms (26 MiB/s)
> > > 53078 bytes read in 19 ms (2.7 MiB/s)
> > > 6590950 bytes read in 240 ms (26.2 MiB/s)
> > > Kernel image @ 0x4100 [ 0x00 - 0x695060 ]
> > > ## Flattened Device Tree blob at 4080
> > >Booting using the fdt blob at 0x4080
> > >Loading Ramdisk to 4f9b6000, end 41e6 ... OK
> > >Loading Device Tree to 4f9a6000, end 4f9b5f55 ... OK
> > >
> > > Starting kernel ...
> >
> > Can you attach your boot.init file (the source of boot.scr)?
> >
> > By the size of DTB you can see that different DTB is loaded. I assume
> > you tried to boot the same kernel, then it could mean that boardname
> > was used instead of board_name to choose DTB. Suspicious is that
> > kernel size also differs... so maybe you booted something else? As
> > usual debugging practice, reduce number of unknown factors. Do not
> > change kernel and U-Boot at the same time.
> >
> > Also, you can try reverting commit e6b1467081d3 ("arm: exynos: Remove
> > duplicated "boardname" env setting") and see if it helps. Or just try
> > to bisect around changes coming from u-boot samsung tree. Try booting
> > v2019.01 and paste the results as well.
> >
> > Best regards,
> > Krzysztof
> >
>
> I have tested with pre-compiled image and the cross compiled kernel image
> both failed to load the kernel.
>
> No revert of the commit e6b1467081d3 did not help.
>
> Yes it seem strange that that load address is changes some how in the u-boot
> env
>
> printenv setting of the latest u-boot U-Boot
> 2019.04-rc3-00131-g8303467e80d-dirty
> [0] https://pastebin.com/1Hgc5xxC (newu-boot.txt)
>
> printenv setting for the old u-boot. U-Boot 2018.01-1
> [1] https://pastebin.com/wD6zK6eG(oldu-boot.txt)
>
> Attach is the boot.txt (boot.scr), also the u-boot env old and u-boot-env new
And does 2019.01 work?
Krzysztof
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Odroid U3 - Upgrade to latest u-boot kernel load fails.
Hi Krzysztof,
On Mon, 18 Mar 2019 at 18:20, Krzysztof Kozlowski wrote:
>
> On Mon, 18 Mar 2019 at 13:32, Anand Moon wrote:
> >
> > Hi Krzysztof / Marek,
> >
> > After I update the latest u-boot on my Odroud U3+ it fails to load the
> > kernel it hangs.
> > I am using Archlinux on Odroid U3.
> >
> > U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 12:12:23 +)
> >
> > CPU: Exynos4412 @ 1 GHz
> > Model: Odroid based on Exynos4412
> > Type: u3
> > DRAM: 2 GiB
> > LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
> > LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
> > LDO21@TFLASH_2.8V: set 280 uV; enabling
> > MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
> > Loading Environment from MMC... Card did not respond to voltage select!
> > *** Warning - No block device, using default environment
> >
> > Net: No ethernet found.
> > Hit any key to stop autoboot: 0
> > switch to partitions #0, OK
> > mmc1 is current device
> > Scanning mmc 1:1...
> > Found U-Boot script /boot/boot.scr
> > 769 bytes read in 6 ms (125 KiB/s)
> > ## Executing script at 4200
> > 6901856 bytes read in 253 ms (26 MiB/s)
> > 53078 bytes read in 19 ms (2.7 MiB/s)
> > 6590950 bytes read in 240 ms (26.2 MiB/s)
> > Kernel image @ 0x4100 [ 0x00 - 0x695060 ]
> > ## Flattened Device Tree blob at 4080
> >Booting using the fdt blob at 0x4080
> >Loading Ramdisk to 4f9b6000, end 41e6 ... OK
> >Loading Device Tree to 4f9a6000, end 4f9b5f55 ... OK
> >
> > Starting kernel ...
>
> Can you attach your boot.init file (the source of boot.scr)?
>
> By the size of DTB you can see that different DTB is loaded. I assume
> you tried to boot the same kernel, then it could mean that boardname
> was used instead of board_name to choose DTB. Suspicious is that
> kernel size also differs... so maybe you booted something else? As
> usual debugging practice, reduce number of unknown factors. Do not
> change kernel and U-Boot at the same time.
>
> Also, you can try reverting commit e6b1467081d3 ("arm: exynos: Remove
> duplicated "boardname" env setting") and see if it helps. Or just try
> to bisect around changes coming from u-boot samsung tree. Try booting
> v2019.01 and paste the results as well.
>
> Best regards,
> Krzysztof
>
I have tested with pre-compiled image and the cross compiled kernel image
both failed to load the kernel.
No revert of the commit e6b1467081d3 did not help.
Yes it seem strange that that load address is changes some how in the u-boot env
printenv setting of the latest u-boot U-Boot
2019.04-rc3-00131-g8303467e80d-dirty
[0] https://pastebin.com/1Hgc5xxC (newu-boot.txt)
printenv setting for the old u-boot. U-Boot 2018.01-1
[1] https://pastebin.com/wD6zK6eG(oldu-boot.txt)
Attach is the boot.txt (boot.scr), also the u-boot env old and u-boot-env new
Best Regards
-Anand
# After modifying, run ./mkscr
# MAC address configuration
# setenv macaddr "00:1e:ee:61:7a:39"
setenv macaddr "3A:02:DD:67:B6:01"
part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs "console=tty1 console=${console} root=PARTUUID=${uuid} rw
rootwait smsc95xx.macaddr=${macaddr}"
if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile};
then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r}
/boot/initramfs-linux.img; then
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
bootz ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi
U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 16:27:40 +)
CPU: Exynos4412 @ 1 GHz
Model: Odroid based on Exynos4412
Type: u3
DRAM: 2 GiB
LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
LDO21@TFLASH_2.8V: set 280 uV; enabling
MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment
Net: No ethernet found.
Hit any key to stop autoboot: 0
Odroid #
Odroid #
Odroid #
Odroid #
Odroid # print env
## Error: "env" not defined
Odroid # printenv
arch=arm
autoboot=if test -e mmc 0 boot.scr; then; run boot_script; elif test -e mmc 0
Image.itb; then; run boot_fit;elif test -e mmc 0 zImage; then; run
boot_zimg;elif test -e mmc 0 uImage; then; run boot_uimg;fi;
baudrate=115200
board=odroid
board_name=odroid
boardname=odroidu3
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr}
${prefix}${script}; source ${scriptaddr}
boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr
${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype}
${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr
${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi
${kernel_addr_r} ${fdtcontroladdr};fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr}
Re: [U-Boot] Odroid U3 - Upgrade to latest u-boot kernel load fails.
On Mon, 18 Mar 2019 at 13:32, Anand Moon wrote:
>
> Hi Krzysztof / Marek,
>
> After I update the latest u-boot on my Odroud U3+ it fails to load the
> kernel it hangs.
> I am using Archlinux on Odroid U3.
>
> U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 12:12:23 +)
>
> CPU: Exynos4412 @ 1 GHz
> Model: Odroid based on Exynos4412
> Type: u3
> DRAM: 2 GiB
> LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
> LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
> LDO21@TFLASH_2.8V: set 280 uV; enabling
> MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
> Loading Environment from MMC... Card did not respond to voltage select!
> *** Warning - No block device, using default environment
>
> Net: No ethernet found.
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
> Found U-Boot script /boot/boot.scr
> 769 bytes read in 6 ms (125 KiB/s)
> ## Executing script at 4200
> 6901856 bytes read in 253 ms (26 MiB/s)
> 53078 bytes read in 19 ms (2.7 MiB/s)
> 6590950 bytes read in 240 ms (26.2 MiB/s)
> Kernel image @ 0x4100 [ 0x00 - 0x695060 ]
> ## Flattened Device Tree blob at 4080
>Booting using the fdt blob at 0x4080
>Loading Ramdisk to 4f9b6000, end 41e6 ... OK
>Loading Device Tree to 4f9a6000, end 4f9b5f55 ... OK
>
> Starting kernel ...
Can you attach your boot.init file (the source of boot.scr)?
By the size of DTB you can see that different DTB is loaded. I assume
you tried to boot the same kernel, then it could mean that boardname
was used instead of board_name to choose DTB. Suspicious is that
kernel size also differs... so maybe you booted something else? As
usual debugging practice, reduce number of unknown factors. Do not
change kernel and U-Boot at the same time.
Also, you can try reverting commit e6b1467081d3 ("arm: exynos: Remove
duplicated "boardname" env setting") and see if it helps. Or just try
to bisect around changes coming from u-boot samsung tree. Try booting
v2019.01 and paste the results as well.
Best regards,
Krzysztof
>
> Old u-boot boots fine see the logs below.
> --
> U-Boot 2018.01-1 (Feb 13 2018 - 02:19:55 +) Arch Linux ARM
>
> CPU: Exynos4412 @ 1 GHz
> Model: Odroid based on Exynos4412
> Board: Odroid based on Exynos4412
> Type: u3
> DRAM: 2 GiB
> LDO20@VDDQ_EMMC_1.8V: set 180 uV; enabling
> LDO22@VDDQ_EMMC_2.8V: set 280 uV; enabling
> LDO21@TFLASH_2.8V: set 280 uV; enabling
> MMC: sdhci@1253 - probe failed: -19
>
> *** Warning - bad CRC, using default environment
>
> Net: No ethernet found.
> Hit any key to stop autoboot: 0
> no mmc device at slot 1
> switch to partitions #0, OK
> mmc0(part 0) is current device
> Scanning mmc 0:1...
> Found U-Boot script /boot/boot.scr
> 770 bytes read in 31 ms (23.4 KiB/s)
> ## Executing script at 5000
> 6625416 bytes read in 267 ms (23.7 MiB/s)
> 72531 bytes read in 483 ms (146.5 KiB/s)
> 6590888 bytes read in 256 ms (24.6 MiB/s)
> Kernel image @ 0x4200 [ 0x00 - 0x651888 ]
> ## Flattened Device Tree blob at 4300
>Booting using the fdt blob at 0x4300
>Loading Ramdisk to 4f9b6000, end 41a8 ... OK
>Loading Device Tree to 4f9a1000, end 4f9b5b52 ... OK
>
> Starting kernel ...
>
> [0.00] Booting Linux on physical CPU 0xa00
> [0.00] Linux version 5.0.1-1-ARCH (builduser@leming) (gcc
> version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Tue Mar 12 04:09:35 UTC
> 2019
> [0.00] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
> instruction cache
> [0.00] OF: fdt: Machine model: Hardkernel ODROID-U3 board
> based on Exynos4412
> [0.00] Memory policy: Data cache writealloc
> [0.00] Reserved memory: created DMA memory pool at 0xbf70,
> size 8 MiB
> [0.00] OF: reserved mem: initialized node region_mfc_right,
> compatible id shared-dma-pool
> [0.00] Reserved memory: created DMA memory pool at 0xbd30,
> size 36 MiB
>
> Please could you share the details on how to debug this issue or how to
> resolve.
>
> Best Regards
> -Anand
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
