will Ubuntu 18.04 image be made for RK3399

penguin

Actually, there's a new  ubuntu 18.04 for Firefly-RK3399 in

  http://www.t-firefly.com/doc/download/page/id/3.html

But it is in Baidu Pan up till now.  We're working on moving it to Google Drive.

penguin

Here comes the Ubuntu 18.04 firmware for Firefly-RK3399, with Google Drive link:

    https://drive.google.com/drive/f ... 089aMAW_4cDGF11F2ou

Uncompress the downloaded file using:

    unxz -k Firefly-RK3399-ubuntu18.04_20181017.img.xz

This firmware uses the gpt partition scheme. Therefore you need the latest
v3.4 upgrade_tool to upgrade the firmware. Download it from:

    http://download.t-firefly.com/pr ... grade_Tool_1.34.zip

To install upgrade_tool to /usr/local/bin, run:

    unzip Linux_Upgrade_Tool_1.34.zip
    cd Linux_Upgrade_Tool/Linux_Upgrade_Tool/
    chmod 755 upgrade_tool
    mv gpt_upgrade_tool
    sudo cp gpt_upgrade_tool config.ini /usr/local/bin/

Now that flashing tool `gpt_upgrade_tool` and firmware file are ready.
To upgrade from the old ubuntu 16.04, the board needs to enter MaskRom mode.
There're two methods:

1. Using the cutting edge metal tweezers following:

    http://en.t-firefly.com/index.php/doc/product/info/id/479.html

2. Or from the running Ubuntu 16.04, unplug the SD Card, and zero head zone of the eMMC by:
  
    sudo dd if=/dev/zero of=/dev/mmcblk? count=$((0x2000))
    # Connect the TypeC cable with PC
    sudo reboot
   
Flash the firmware:

    cd /path/to/the/Firefly-RK3399-ubuntu18.04_20181017.img
    gpt_upgrade_tool uf Firefly-RK3399-ubuntu18.04_20181017.img

Good luck. If any question, write here. I'll try my best to help.

penguin

@Jack_P

You can download it at:
https://drive.google.com/drive/f ... qTpgCQiZFCmj-DUbbwb

penguin

Jack_P Posted at 1/9/2019 23:06
Hey Penguin,
I tried installing using your steps for ROC-RK3399-PC. But the upgrade tool wasn't det ...

https://drive.google.com/drive/f ... qTpgCQiZFCmj-DUbbwb

ROC-RK3399-PC-Ubuntu18.04-SDBOOT-xxxx.img

penguin

Hi, @KD0OHR , do you have the serial adapter to access the log of u-boot?
That helps to identify the problem. Thanks!

penguin

Hi @tek ,
From the log,  eMMC is fixed to mmcblk1 and SD card is fixed to mmcblk0. Both are correct.

The rootfs is chosen from either mmcblk0p5 or mmcblk1p5.
What's the `root=` parameter in the kernel cmdline?

plz paste result of： cat /proc/cmdline

penguin

@tek

You are right. Using the same PARTUUID is the culprit.

SD seems to intermittently not come up consistently (sometimes as 50MHz, sometimes as 150MHZ, sometimes as "high speed" and sometimes as "ultra speed")

This needs further investigation. What sd card do you use?

penguin

The difference is the phase tuning, but I do not have any clue about what causes this.