From: Alexander von Gluck IV <kallisti5@unixzen.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] rk3288 (Tinkerboard) not booting【请注意,邮件由u-boot-bounces@lists.denx.de代发】
Date: Wed, 25 Sep 2019 18:19:35 +0000 [thread overview]
Message-ID: <f063193e0517a508cb557cd7cbbe8438@unixzen.com> (raw)
In-Reply-To: <fa464b9d5bd57fe0160efefd97d312d6@unixzen.com>
Just rounding this one out.. I was definitely looking at the wrong uart. After
moving to uart2, things are working as expected (minus hdmi output from u-boot)
Thanks!
-- Alex
September 23, 2019 9:27 AM, "Alexander von Gluck IV" <kallisti5@unixzen.com> wrote:
> ACK! I'm on UART1. Mix that with video potentially not working
> in u-boot and I think I have my answer.
>
> I'll test this afternoon.
>
> (PS, since the Tinker is supposed to be "Raspberry Pi like", why would
> u-boot present on UART2 on it while the Raspberry Pi u-boot uses UART1?)
>
> Thanks for the help!
>
> -- Alex
>
> September 23, 2019 9:19 AM, "Jonathan Gray" <jsg@jsg.id.au> wrote:
>
>> On Mon, Sep 23, 2019 at 01:55:32PM +0000, Alexander von Gluck IV wrote:
>>
>>> Oh, a difference:
>>>
>>> $ tools/mkimage -n rk3288 -T rksd -d tpl/u-boot-tpl.bin idbloader.img && \
>>> cat spl/u-boot-spl-dtb.bin >> idbloader.img
>>>
>>> I'm using the idbloader.img that u-boot automatically spits out.
>>>
>>> $ tools/mkimage -n rk3288 -T rksd -d tpl/u-boot-tpl.bin idbloader-manual.img
>>> Image Type: Rockchip RK32 (SD/MMC) boot image
>>> Data Size: 20480 bytes
>>> $ cat spl/u-boot-spl-dtb.bin >> idbloader-manual.img
>>>
>>> However.. the generated idbloader-manual.img from the commands above is identical to idbloader.img
>>> that u-boot produces compared with md5sum.
>>>
>>> Are you writing the following?
>>>
>>> sudo dd if=idbloader.img of=/dev/sdd seek=64
>>> sudo dd if=u-boot-dtb.img of=/dev/sdd seek=16384
>>
>> those files/offsets yes
>>
>>> (where /dev/sdd is a MicroSD card)
>>>
>>> These should be enough to get into u-boot at startup... correct?
>>
>> yes
>>
>> I am using uart2
>> https://www.asus.com/us/Single-Board-Computer/Tinker-Board
>> 32 UART2TX_PWM3
>> 33 UART2RX_PWM2
>> and 30 for ground
>>
>>> I'm not missing some requirement of u-boot.bin on a FAT32 partition or something?
>>
>> the tpl/spl and u-boot proper are at raw offsets in this case
>>
>>> -- Alex
>>>
>>> September 23, 2019 8:31 AM, "Jonathan Gray" <jsg@jsg.id.au> wrote:
>>>
>>> On Mon, Sep 23, 2019 at 01:06:35PM +0000, Alexander von Gluck IV wrote:
>>>
>>> Ok, looking for differences now..
>>>
>>> * Older Tinker Board? (I'm not using the Tinker Board S)
>>>
>>> yes, the original one
>>>
>>> * Same steps?
>>>
>>> along the lines of
>>>
>>> gmake CROSS_COMPILE="arm-none-eabi-" tinker-rk3288_defconfig
>>> gmake CROSS_COMPILE="arm-none-eabi-" all
>>> tools/mkimage -n rk3288 -T rksd -d tpl/u-boot-tpl.bin idbloader.img && \
>>> cat spl/u-boot-spl-dtb.bin >> idbloader.img
>>>
>>> * Same config? tinker-rk3288_defconfig?
>>>
>>> yes
>>>
>>> * Uart 115200?
>>>
>>> yes
>>>
>>> * Any HDMI Video output?
>>>
>>> no hdmi connected only serial
>>>
>>> * GCC version?
>>>
>>> gcc-linaro-6.3.2017.02 binutils 2.27 arm-none-eabi target
>>>
>>> September 23, 2019 12:34 AM, "Jonathan Gray" <jsg@jsg.id.au> wrote:
>>>
>>> On Mon, Sep 23, 2019 at 01:17:40AM +0000, Alexander von Gluck IV wrote:
>>>
>>> Hello!
>>>
>>> There is no uart output and no video with u-boot master.
>>> The board works as expected booting the Asus Armbian image on an SD.
>>>
>>> At this point i'd be happy to get some u-boot uart output :-)
>>>
>>> -- Alex
>>>
>>> uart output works here with the latest master
>>> (780a17e814503f71d1b51d578b32bc9c89933183)
>>>
>>> U-Boot TPL 2019.10-rc3-00401-ge23a6e5c43 (Sep 23 2019 - 15:13:20)
>>> Trying to boot from BOOTROM
>>> Returning to boot ROM...
>>>
>>> U-Boot SPL 2019.10-rc3-00401-ge23a6e5c43 (Sep 23 2019 - 15:13:20 +1000)
>>> Trying to boot from MMC1
>>>
>>> U-Boot 2019.10-rc3-00401-ge23a6e5c43 (Sep 23 2019 - 15:13:20 +1000)
>>>
>>> Model: Tinker-RK3288
>>> DRAM: 2 GiB
>>> MMC: dwmmc at ff0c0000: 1
>>> Loading Environment from MMC... *** Warning - bad CRC, using default environment
>>>
>>> In: serial
>>> Out: serial
>>> Err: serial
>>> Model: Tinker-RK3288
>>> rockchip_dnl_key_pressed: adc_channel_single_shot fail!
>>> Net: eth0: ethernet at ff290000
>>> Hit any key to stop autoboot: 0
>>> switch to partitions #0, OK
>>> mmc1 is current device
>>> Scanning mmc 1:1...
>>> Found EFI removable media binary efi/boot/bootarm.efi
>>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>>> Scanning disk dwmmc at ff0c0000.blk...
>>> Found 3 disks
>>> BootOrder not defined
>>> EFI boot manager: Cannot load any image
>>> 88176 bytes read in 9 ms (9.3 MiB/s)
>>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>>> OpenBSD/armv7 BOOTARM 1.6
>>>
>>> boot>
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> https://lists.denx.de/listinfo/u-boot
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2019-09-25 18:19 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
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 [this message]
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=f063193e0517a508cb557cd7cbbe8438@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