[U-Boot] rk3288 (Tinkerboard) not booting【请注意,邮件由u-boot-bounces at lists.denx.de代发】
Jonathan Gray
jsg at jsg.id.au
Mon Sep 23 14:19:25 UTC 2019
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 at 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 at 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
More information about the U-Boot
mailing list