Jump to content

rk3288 tinker: Ubuntu image not booting


Jagan

Recommended Posts

Hi,

 

I've downloaded Ubuntu-mainline image at https://www.armbian.com/tinkerboard/

and written to SD as below but Hang while booting.

 

# dd if=Armbian_5.35_Tinkerboard_Ubuntu_xenial_next_4.13.16_desktop.img of=/dev/mmcblk0
5742592+0 records in
5742592+0 records out
2940207104 bytes (2.9 GB, 2.7 GiB) copied, 481.509 s, 6.1 MB/s

 

Log:

U-Boot SPL 2017.09-armbian (Nov 22 2017 - 17:12:11)
Returning to boot ROM...


U-Boot 2017.09-armbian (Nov 22 2017 - 17:12:11 +0100)

Model: Tinker-RK3288
DRAM:  2 GiB
MMC:   dwmmc@ff0c0000: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Tinker-RK3288
Net:   eth0: ethernet@ff290000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1485 bytes read in 26 ms (55.7 KiB/s)
## Executing script at 00000000
U-boot loaded from eMMC
106 bytes read in 21 ms (4.9 KiB/s)
42451 bytes read in 48 ms (863.3 KiB/s)
4616543 bytes read in 241 ms (18.3 MiB/s)
8384056 bytes read in 410 ms (19.5 MiB/s)
## Loading init Ramdisk from Legacy Image at 21000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4616479 Bytes = 4.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to 0fb98000, end 0ffff11f ... OK
   Loading Device Tree to 0fb8a000, end 0fb975d2 ... OK

Starting kernel ...

Link to comment
Share on other sites

39 minutes ago, Jagan said:

# dd if=Armbian_5.35_Tinkerboard_Ubuntu_xenial_next_4.13.16_desktop.img of=/dev/mmcblk0

 

No need to format anything. Check is crucial that's why we suggest Etcher and if you can, try some other SD card.  I am not sure exactly for image which you are trying, but this one: https://dl.armbian.com/tinkerboard/nightly/Armbian_5.35.171130_Tinkerboard_Ubuntu_xenial_next_4.14.2_desktop.7z was tested personally and it works this way:
 

 

4.14.y is recommended since we are ditching 4.13.y ASAP.

Link to comment
Share on other sites

if you change the dtb it will be to "rk3288-miniarm.dtb" as that was the original name of the board.  I've stuck with it because of consistency to the 4.4 kernel.

 

But to be clear, I'm not sure how that would be the issue, I admit I haven't built an image in a couple days, but...

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines