From: "Heiko Stübner" <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [BUG] booting on the Tinker Board (tinker-rk3288_defconfig) is broken
Date: Thu, 28 Feb 2019 11:50:11 +0100 [thread overview]
Message-ID: <14117955.6ItOSGQUdQ@diego> (raw)
In-Reply-To: <c851f36b-8848-ab1a-7673-bdf33a3ca64c@rock-chips.com>
Hi David,
Am Montag, 18. Februar 2019, 02:05:12 CET schrieb David Wu:
> Hi Heinrich and Michael,
>
> Another thing i see is that I missed a patch, for the 3288 gpio0, its
> iomux is special, there is no high 16-bit write-enabled bit. For Tinker
> board, it uses I2C0, the current driver will overwrite the I2C0 iomux,
> while request the GPIO0A4. It requires a patch:
>
> http://patchwork.ozlabs.org/patch/1040541/
I've also just stumbled onto the issue of recent uboots not booting
on rk3288. While your patch seems to have reached patchwork, somehow
the u-boot list seems to have lost it - as it's neither in public
archives nor in my inbox it seems.
Applying the patch does not make my board (phycore-rk3288 in this case)
get farther though - I'll investigate more.
But it looks like we should be having the same issue in the kernel, just
never triggered it, as the gpio0 are of more esotheric uses normally.
Anyway, I'm wondering if defining IOMUX_WRITABLE_32BIT alone
wouldn't be enough and use that for iomux, pull and drv, similar to
what we do for the pull/drv register source already.
That way we could refrain from introducing DRV_TYPE_WRITABLE_32BIT
and PULL_TYPE_WRITABLE_32BIT .
Heiko
>
> 在 2019/2/17 下午8:41, Heinrich Schuchardt 写道:
> > On 2/17/19 1:18 PM, Michael Nazzareno Trimarchi wrote:
> >> Hi
> >>
> >> [U-Boot] [PATCH 3/5] rockchip: rk3288-vyasa: increase heap space after
> >> relocation
> >>
> >> Can you check it if you have the same problem?
> >
> > Applying all the changes causes SPL not to start.
> >
> > CONFIG_SYS_MALLOC_F_LEN=0x4000
> > does not solve the problem.
> >
> > Best regards
> >
> > Heinrich
> >
> >> Michael
> >>
> >>
> >> On Sun., 17 Feb. 2019, 1:11 pm Heinrich Schuchardt <xypron.glpk@gmx.de
> >>
> >> <mailto:xypron.glpk@gmx.de> wrote:
> >> On 2/17/19 9:19 AM, David Wu wrote:
> >> > Hi Henrich,
> >> >
> >> > 在 2019/2/16 下午5:53, Heinrich Schuchardt 写道:
> >> >> On 2/13/19 11:56 AM, Philipp Tomsich wrote:
> >> <snip>
> >>
> >> >> Hello David, hello Philipp,
> >> >>
> >> >> what are your ideas to reduce the SPL size to under 0x7800 again?
> >> >> Or will you move all rk3288 boards to TPL like
> >> >> TARGET_VYASA_RK3288?
> >> >
> >> > CONFIG_SPL_I2C_SUPPORT is necessary for Tink spl? Remove this can
> >> > make
> >> > spl boot. As the Tinker does not use the i2c to read the MAC
> >> > address
> >> > from eeprom at the SPL stage, which is at uboot.
> >>
> >> Hello David,
> >>
> >> the SPL image size now just fits:
> >> Image Type: Rockchip RK32 (SD/MMC) boot image
> >> Data Size: 30720 bytes
> >>
> >> SPL is successful. But MMC is failing in main U-Boot:
> >>
> >> ```
> >> U-Boot SPL 2019.04-rc1-00239-gb89074f650 (Feb 17 2019 - 12:41:39
> >> +0100)
> >> Returning to boot ROM...
> >>
> >>
> >> U-Boot 2019.04-rc1-00239-gb89074f650 (Feb 17 2019 - 12:41:39 +0100)
> >>
> >> Model: Tinker-RK3288
> >> DRAM: 2 GiB
> >> MMC: dwmmc at ff0c0000: 1
> >> Loading Environment from MMC...
> >> ```
> >>
> >> No further output here.
> >>
> >> With some debug output enabled:
> >>
> >> ```
> >> U-Boot SPL 2019.04-rc1-00239-gb89074f650-dirty (Feb 17 2019 -
> >> 13:05:10
> >> +0100)
> >> Returning to boot ROM...
> >> mmc_bind: alias ret=0, devnum=1
> >> env_init: Environment MMC init done (ret=-2)
> >>
> >>
> >> U-Boot 2019.04-rc1-00239-gb89074f650-dirty (Feb 17 2019 - 13:05:10
> >> +0100)
> >>
> >> Model: Tinker-RK3288
> >> DRAM: 2 GiB
> >> mmc_bind: alias ret=0, devnum=1
> >> MMC: dwmmc at ff0c0000: 1
> >> Loading Environment from MMC...
> >> ```
> >>
> >> Any suggestion how to proceed?
> >>
> >> CC: Jaehoon.
> >>
> >> Best regards
> >>
> >> Heinrich
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2019-02-28 10:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 12:12 [U-Boot] [BUG] booting on the Tinker Board (tinker-rk3288_defconfig) is broken Heinrich Schuchardt
2019-02-09 15:08 ` Philipp Tomsich
2019-02-09 15:24 ` Philipp Tomsich
2019-02-09 16:39 ` Heinrich Schuchardt
2019-02-09 18:24 ` Philipp Tomsich
2019-02-12 12:38 ` David Wu
2019-02-12 13:53 ` Philipp Tomsich
2019-02-13 10:28 ` David Wu
2019-02-13 10:30 ` Philipp Tomsich
2019-02-13 10:42 ` David Wu
2019-02-13 10:47 ` Philipp Tomsich
2019-02-12 13:54 ` Philipp Tomsich
2019-02-13 10:10 ` David Wu
2019-02-13 10:13 ` Philipp Tomsich
2019-02-13 10:33 ` David Wu
2019-02-13 10:47 ` Philipp Tomsich
2019-02-13 10:52 ` David Wu
2019-02-13 10:56 ` Philipp Tomsich
2019-02-16 9:53 ` Heinrich Schuchardt
2019-02-17 8:19 ` David Wu
2019-02-17 12:10 ` Heinrich Schuchardt
2019-02-17 12:18 ` Michael Nazzareno Trimarchi
2019-02-17 12:41 ` Heinrich Schuchardt
2019-02-18 1:05 ` David Wu
2019-02-28 10:50 ` Heiko Stübner [this message]
2019-02-28 12:36 ` Philipp Tomsich
2019-02-28 12:46 ` Heiko Stübner
2019-02-28 13:29 ` Heiko Stübner
2019-03-01 12:35 ` David Wu
2019-03-01 12:29 ` David Wu
2019-03-01 12:48 ` Philipp Tomsich
2019-02-13 12:25 ` Tom Rini
2019-02-13 13:16 ` Heinrich Schuchardt
2019-02-13 13:24 ` Tom Rini
2019-02-13 20:13 ` Heinrich Schuchardt
2019-02-13 20:19 ` Tom Rini
2019-02-12 11:53 ` David Wu
2019-02-11 10:30 ` Jack Mitchell
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=14117955.6ItOSGQUdQ@diego \
--to=heiko@sntech.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