public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] rockchip: firefly-rk3288 broken - DRAM wrong?
Date: Sun, 3 Apr 2016 18:05:06 +0200	[thread overview]
Message-ID: <57013F32.9040801@suse.de> (raw)

Hello,

v2016.01 is the last release to boot Linux on the Firefly-RK3288 for me.
On v2016.03 or master there is no output from the kernel.

This coincides with the DRAM getting misdetected as 512 MiB:


U-Boot SPL 2016.03-00634-g563d8d9 (Apr 03 2016 - 16:29:17)
Trying to boot from MMC1


U-Boot 2016.03-00634-g563d8d9 (Apr 03 2016 - 16:29:17 +0200)

Model: Firefly-RK3288
DRAM:  512 MiB
MMC:   dwmmc at ff0f0000: 0, dwmmc at ff0c0000: 1
*** Warning - bad CRC, using default environment

stdio_add_devices: Video device failed (ret=-19)
In:    serial
Out:   serial
Err:   serial
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
** No partition table - mmc 0 **
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
473 bytes read in 45 ms (9.8 KiB/s)
## Executing script at 00000000
6082320 bytes read in 559 ms (10.4 MiB/s)
38354 bytes read in 135 ms (277.3 KiB/s)
7409264 bytes read in 647 ms (10.9 MiB/s)
Kernel image @ 0x2000000 [ 0x000000 - 0x5ccf10 ]
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to 1d369000, end 1da79e70 ... OK
   Loading Device Tree to 1d35c000, end 1d3685d1 ... OK

Starting kernel ...


vs.


U-Boot SPL 2016.01 (Apr 03 2016 - 16:47:26)
Trying to boot from MMC


U-Boot 2016.01 (Apr 03 2016 - 16:47:26 +0200)

Model: Firefly-RK3288
DRAM:  2 GiB
MMC:   dwmmc at ff0c0000: 0, dwmmc at ff0f0000: 1
*** Warning - bad CRC, using default environment

In:    serial at ff690000
Out:   serial at ff690000
Err:   serial at ff690000
Net:   Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
473 bytes read in 51 ms (8.8 KiB/s)
## Executing script at 00000000
6082320 bytes read in 1222 ms (4.7 MiB/s)
38354 bytes read in 155 ms (241.2 KiB/s)
7409264 bytes read in 1450 ms (4.9 MiB/s)
Kernel image @ 0x2000000 [ 0x000000 - 0x5ccf10 ]
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to 1f8ef000, end 1ffffe70 ... OK
   Loading Device Tree to 1f8e2000, end 1f8ee5d1 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x500
[...]


Any hints for speeding up bisection appreciated.

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)

             reply	other threads:[~2016-04-03 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-03 16:05 Andreas Färber [this message]
2016-04-03 19:32 ` [U-Boot] rockchip: firefly-rk3288 broken - DRAM wrong? Andreas Färber
2016-04-03 19:59   ` Alexander Graf
2016-04-03 21:18     ` Andreas Färber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57013F32.9040801@suse.de \
    --to=afaerber@suse.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox