Dietpi: Image | Firefly RK3399

[carlosedp]

ADMIN EDIT

New SDcard Buster-based image available: https://dietpi.com/downloads/images/DietPi_FireflyRK3399-ARMv8-Buster.7z

• Flash to eMMC should work as well via adapter or directly when initially booting from SDcard.

---

I have build an image for Firefly RK3399 SBC based on the existing FriendlyARM NanoPC-T4 from here.

The image still has some NanoPC-T4 markings on it's config so it might require updates. The Kernel is the 4.4.138 built from Rockchip tree and contains most useful modules for Docker, Kubernetes, networking as IPVS and IPTables. The modules are in a .tar.gz file that need to be copied to the rootfs
/lib/modules after install. Newer DietPi rootfs already contains this in right place.

Device information:

• Device name: Firefly RK3399
• Official product URL: http://en.t-firefly.com/product/rk3399.html
• Image download URL: https://dietpi.com/downloads/images/DietPi_FireflyRK3399-ARMv8-Buster.7z

Benchmarks:

Writing DietPi to the onboard EMMC:

Requires:

• Firefly RK3399
• USB-C Cable (eg: https://www.amazon.co.uk/Syncwire-USB-3-0-Type-Cable/dp/B01C8BFHW4)
• Ethernet connected (or WiFi can be setup with serial console during 1st run setup)
• A Windows system (to use the provided easy write tool with USB-C, Linux options require command line).
  -- Linux users, please follow this guide: http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T4#Flash_Image_to_eMMC_with_Linux_Upgrade_Tool

Writing the images to the EMMC

• Download image file and unpack
• Power off the board
• Plug in the USB-C cable and power cable (do not power on). Plug in the other end of the USB-C cable into your Windows system.
• Launch the program AndroidTool.exe

Now we need to enter into MASKROM mode:

• Follow the steps from http://en.t-firefly.com/doc/product/info/id/479.html.
• When you see a MASKROM message appear in the AndroidTool.exe window, release the buttons.
• Select Run. This will write the images to the EMMC.
  When the transfer is completed, the system will automatically reboot and begin the 1st run setup.

The image works with Firefly M.2 to SATA adapter card. The drivers were included into the Kernel. Check benchmark image for the "Custom" line.

@Fourdee , can you check this out and update the config files/rootfs to contain the kernel modules and Firefly naming all around? Also, testers needed.

[Fourdee]

@carlosedp

Great work, thanks for creating and sharing this 👍

@Fourdee , can you check this out and update the config files/rootfs to contain the kernel modules and Firefly naming all around?

Yep, leave it with me. I lack the Firefly device, but, may try it on NanoPC-T4, you never know :)

[Fourdee]

@carlosedp

Image uploaded https://dietpi.com/downloads/images/DietPi_FireflyRK3399-ARMv8-Buster.7z

• Contains the G_HW_MODEL ID for Firefly
• Contains the additional modules you linked in original post.

I've not tested it yet. Will try NanoPC-T4 when I can.

[carlosedp]

Gonna update my initial comment with this link since it contains the modules and correct naming.

[carlosedp]

@Fourdee I reflashed my board and found a problem with the provided package. Android Flash Tool gave me an error where the rootfs could not be flashed. I unpacked the rootfs.img with the imgRePackerRK utility and flashed the generated rootfs.img.iso successfully.

λ img_pack\imgRePackerRK.exe rootfs.img

        imgRepackerRK (version 1.06 windows)
        Rockchip firmware batch/update images unpacker/packer

        (c) RedScorpio, Moscow, 2013-2017
            [email protected]

        Detected OS:    Windows 7 Enterprise SP 1.0 [build 7601] x64
        ==========================[ START ]==========================

        --- Firmware unpacking ---

        2-nd layer file unpacking
        sparse image format detected
        "rootfs.img" (sparse image) unpacking
                Processed 100 chunks
                Processed 200 chunks
                Processed 300 chunks
                Processed 400 chunks
        Processed blocks        = 217600
        Stored CRC32            = 0x00000000
        Calculated CRC32        = 0xd756b914
        Stored and calculated CRC32 are not equal
        Probably CRC32 don't used
        Configuration file"rootfs.img.cfg"      created
        Unpacked image format: ext4 image (16)

                FS file properties:

                Size:                   838860800
                Label:                  ""
                Block size:             4096
                Blocks per group:       32768
                Inodes count:           51296
                Inode size:             256
                Inodes per group:       7328
                Reserved GDT blocks:    99
        "rootfs.img"    unpacked

[Fourdee]

@carlosedp

Ah yes, I repacked the .img for the image we uploaded: https://dietpi.com/downloads/images/DietPi_FireflyRK3399-ARMv8-Buster.7z

A quick way to test if its been packed, try opening the .img in 7zip. .iso will open, packed wont 😃

[MichaIng]

We have anther open image request for ROC-RK3328-CC: https://dietpi.com/phpbb/viewtopic.php?f=12&t=2694

They at least share the same CPU with Rock64 at least, not sure if images can be used cross devices?

[carlosedp]

Usually not because of the DTBs for each board. This seems very similar in specs to Rock64 from Pine64. The Rockchip tree doesn't contain it but I believe Firefly probably do. Need to check this once I get some time.

[MichaIng]

@carlosedp
I created a new Buster image, based on Armbian with Linux mainline kernel 5.4: https://dietpi.com/downloads/images/DietPi_FireflyRK3399-ARMv8-Buster.7z
It is an SDcard image, no GPT => eMMC installer image like the one you created from NanoPC T4, since I am not familiar with the Android Tools method. Also it should be possible to flash it directly to eMMC via adapter or from running system on SDcard, remounting rootfs as rw and using dd.

However if some is experienced with the Android Tools (or equivalent) method to create an installer image (boot from e.g. USB flash, install directly to internal eMMC), then I am open for it and would love to integrate it into our image creation script: https://github.com/MichaIng/DietPi/blob/dev/.meta/dietpi-imager

---

Added it to official download page as well (marked as beta): https://dietpi.com/#download

[MichaIng]

I mark this as closed. Interest in this board is VERY small, however Buster-based image is up, marked as beta, any observed issues can be handled via dedicated issue.