From: Alexander von Gluck IV <kallisti5@unixzen.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] rk3288 (Tinkerboard) not booting
Date: Sun, 22 Sep 2019 21:22:38 +0000 [thread overview]
Message-ID: <718d9a0495c3d940e4f00038cbdd495e@unixzen.com> (raw)
In-Reply-To: <CAOf5uwmKXwjXczLs0y+m9oyUXSSZnnenuNvzDk4j57Apg5svjA@mail.gmail.com>
Using master from git://git.denx.de/u-boot.git
commit 390183b58179ddaf986422f4d9446c596660f7e0 (HEAD -> master, origin/master, origin/HEAD)
Merge: d6c7309f56 79907a4f84
Author: Tom Rini <trini@konsulko.com>
Date: Sat Sep 21 07:31:23 2019 -0400
Merge tag 'efi-2019-10-rc4-5' of https://gitlab.denx.de/u-boot/custodians/u-boot-efi
Pull request for UEFI sub-system for v2019.10-rc4 (5)
This patch set fixes errors in the UEFI sub-system and adds a function to
compare u16 strings which is prerequisite for further patches.
Same error:
$ ./tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl-dtb.bin out
Warning: SPL image is too large (size 0xb000) and will not boot
Error: image verification failed
$ ls -lah spl/u-boot-spl-dtb.bin
-rw-rw-r-- 1 kallisti5 kallisti5 43K Sep 22 16:17 spl/u-boot-spl-dtb.bin
September 22, 2019 4:03 PM, "Michael Nazzareno Trimarchi" <michael@amarulasolutions.com> wrote:
> Hi
>
> Please use the latest uboot. The fixes should be already merged
>
> Mcihael
>
> On Sun, Sep 22, 2019 at 10:53 PM Alexander von Gluck IV
> <kallisti5@unixzen.com> wrote:
>
>> Anyone know a way to get a functional u-boot on the rk3288? (Tinkerboard, SD)
>>
>> The docs seem to recommend:
>> $ /tmp/arm-build/tools/mkimage -n rk3288 -T rksd -d arm/tinkerboard/u-boot-spl-dtb.bin out
>>
>> However, that produces:
>> Warning: SPL image is too large (size 0xb000) and will not boot
>>
>> I saw this patch to disable I2C in the SPL to reduce its size:
>> https://github.com/xypron/u-boot-patches/blob/df2ceb65fb4cc433aa17304ed9d3d591c14ef5ac/0001-configs-
>> inker-rk3288-disable-CONFIG_SPL_I2C_SUPPORT.patch
>>
>> However, that breaks the build :-|
>>
>> LD spl/u-boot-spl
>> arm-unknown-haiku-ld.bfd: drivers/built-in.o: in function `rk8xx_write':
>> /tmp/arm-build/drivers/power/pmic/rk8xx.c:30: undefined reference to `dm_i2c_write'
>> arm-unknown-haiku-ld.bfd: drivers/built-in.o: in function `rk8xx_read':
>> /tmp/arm-build/drivers/power/pmic/rk8xx.c:43: undefined reference to `dm_i2c_read'
>> make[1]: *** [scripts/Makefile.spl:404: spl/u-boot-spl] Error 1
>> make: *** [Makefile:1762: spl/u-boot-spl] Error 2
>> make: Leaving directory '/tmp/arm-build'
>> Disabling SPL Power then results in an error compiling MMC support
>> Any alternative methods to getting u-boot running from SD?
>> Rockchip devices seem to be kind of complex to get going :-|
>> -- Alex
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> https://lists.denx.de/listinfo/u-boot
>
> --
> | Michael Nazzareno Trimarchi Amarula Solutions BV |
> | COO - Founder Cruquiuskade 47 |
> | +31(0)851119172 Amsterdam 1018 AM NL |
> | [`as] http://www.amarulasolutions.com |
next prev parent reply other threads:[~2019-09-22 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 20:53 [U-Boot] rk3288 (Tinkerboard) not booting Alexander von Gluck IV
2019-09-22 21:03 ` Michael Nazzareno Trimarchi
2019-09-22 21:22 ` Alexander von Gluck IV [this message]
2019-09-22 21:46 ` Michael Nazzareno Trimarchi
2019-09-22 22:00 ` Alexander von Gluck IV
2019-09-22 22:09 ` Alexander von Gluck IV
2019-09-23 1:04 ` [U-Boot] rk3288 (Tinkerboard) not booting【请注意,邮件由u-boot-bounces@lists.denx.de代发】 Kever Yang
2019-09-23 1:17 ` Alexander von Gluck IV
2019-09-23 5:34 ` Jonathan Gray
2019-09-23 13:06 ` Alexander von Gluck IV
2019-09-23 13:31 ` Jonathan Gray
2019-09-23 13:55 ` Alexander von Gluck IV
2019-09-23 14:19 ` Jonathan Gray
2019-09-23 14:26 ` Alexander von Gluck IV
2019-09-25 18:19 ` Alexander von Gluck IV
2019-09-26 5:01 ` Michael Nazzareno Trimarchi
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=718d9a0495c3d940e4f00038cbdd495e@unixzen.com \
--to=kallisti5@unixzen.com \
--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