On 2018-06-05, Vagrant Cascadian wrote:

On 2018-05-21, Vagrant Cascadian wrote:

...

On 2018-05-12, Vagrant Cascadian wrote:

...

On 2018-05-12, Vagrant Cascadian wrote:

...

Booting firefly-rk3288 seems to hang looking for environment:

U-Boot 2018.05+dfsg-1 (May 10 2018 - 20:24:57 +0000)

Model: Firefly-RK3288 DRAM: 2 GiB MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0 Loading Environment from MMC...

And just hangs there.

Still happening with v2018.07-rc1, too.

Also just tried with v2018.09-rc2, same problem.

live well, vagrant

...

I tried to bisect this, and got:

commit 04a2ea248f58b3b6216d0cd0a6b8698df8b14355 Author: Jean-Jacques Hiblot jjhiblot@ti.com Date: Thu Sep 21 16:30:08 2017 +0200

mmc: disable UHS modes if Vcc cannot be switched on and off

But it fails in a slightly different way:

U-Boot 2018.01-00026-g04a2ea248f (May 21 2018 - 21:46:18 +0000)

Model: Firefly-RK3288 DRAM: 2 GiB MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0

And just hangs without the "Loading Environment from MMC..." part...

It is not a trivial revert on top of 2018.05, so I haven't been able to do that simple test.

On 2018-08-14, Vagrant Cascadian wrote:

...

Also just tried with v2018.09-rc2, same problem.

With some debugging in mmc enabled (#define DEBUG at the top of dw_mmc.c mmc-uclass.c mmc.c rockchip_dw_mmc.c) and CONFIG_MMC_TRACE=y, it gives a little more information:

U-Boot SPL 2018.09-rc2+dfsg-1~20180814~6 (Aug 14 2018 - 21:58:09 +0000) Returning to boot ROM... mmc_bind: alias ret=0, devnum=1

U-Boot 2018.09-rc2+dfsg-1~20180814~6 (Aug 14 2018 - 21:58:09 +0000)

Model: Firefly-RK3288 DRAM: 2 GiB mmc_bind: alias ret=0, devnum=1 mmc_bind: alias ret=0, devnum=0 MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0 Loading Environment from MMC... clock is disabled (0Hz)

Buswidth = 0, clock: 0

live well, vagrant

On 2018-12-18, Simon Glass wrote:

At little late to the party, but the current 2019.01.rc2 works OK for me:

crosfw -b firefly-rk3288 -i && /tmp/b/firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d /tmp/b/firefly-rk3288/spl/u-boot-spl.bin out && cat /tmp/b/firefly-rk3288/u-boot-dtb.bin >> out && sudo dd if=out of=/dev/sdb seek=64 && sync

U-Boot SPL 2019.01-rc2-00001-g90603d0093-dirty (Dec 18 2018 - 20:03:26 -0700) Returning to boot ROM...

U-Boot 2019.01-rc2-00001-g90603d0093-dirty (Dec 18 2018 - 20:03:26 -0700)

Model: Firefly-RK3288 DRAM: 2 GiB MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment

In: serial Out: serial Err: serial Model: Firefly-RK3288 Net: Warning: ethernet@ff290000 (eth0) using random MAC address - 56:3a:73:55:2e:82 eth0: ethernet@ff290000 Hit any key to stop autoboot: 0 =>

I'm not so lucky. 2019.01-rc2 hangs even earlier without detecting the ram (on a 4GB ram model)::

U-Boot SPL 2019.01-rc2+dfsg-1~20181219~2 (Dec 19 2018 - 23:12:56 +0000) Returning to boot ROM...

U-Boot 2019.01-rc2+dfsg-1~20181219~2 (Dec 19 2018 - 23:12:56 +0000)

Model: Firefly-RK3288 DRAM: 0 Bytes

Haven't tried on a 2GB model yet...

Could I get a copy of your working binaries to test?

What toolchain are you using to build?

I'm using gcc 8.2.0 and binutils 2.31.1 from debian, built natively.

live well, vagrant

On 27.12.2018, at 02:00, Kever Yang kever.yang@rock-chips.com wrote:

Hi Vagrant,

On 12/25/2018 12:14 AM, Vagrant Cascadian wrote:

...

I'm not so lucky. 2019.01-rc2 hangs even earlier without detecting the ram (on a 4GB ram model)::

U-Boot SPL 2019.01-rc2+dfsg-1~20181219~2 (Dec 19 2018 - 23:12:56 +0000) Returning to boot ROM...

U-Boot 2019.01-rc2+dfsg-1~20181219~2 (Dec 19 2018 - 23:12:56 +0000)

Model: Firefly-RK3288 DRAM: 0 Bytes

Seems like the 4GB ram size issue still not fixed on mainline :( 4GB is out of 32bit range, I though it has been fixed because I did see someone send the patch to list very long time ago.

That change is still waiting for an updated patch after it failed in Travis-CI. Unfortunately, that updated patch still hasn’t been sent...

Well, let me send one which works in my local branch.

Thanks for taking that on…

Philipp.