Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image | Firefly RK3399 #1986

Closed
carlosedp opened this issue Aug 2, 2018 · 17 comments
Closed

Image | Firefly RK3399 #1986

carlosedp opened this issue Aug 2, 2018 · 17 comments
Assignees
Labels
Image request 💾 Solution available 🥂 Definite solution has been done
Milestone

Comments

@carlosedp
Copy link

carlosedp commented Aug 2, 2018

ADMIN EDIT

New SDcard Buster-based image available: REMOVED AS NO SINGLE INSTALL FOR MONTHS

  • 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.

image

Device information:

Benchmarks:

image

Writing DietPi to the onboard EMMC:

Requires:

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
Copy link
Collaborator

Fourdee commented Aug 3, 2018

@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 Fourdee added this to the v6.13 milestone Aug 3, 2018
@Fourdee
Copy link
Collaborator

Fourdee commented Aug 3, 2018

@carlosedp

Image uploaded REMOVED AS NO SINGLE INSTALL FOR MONTHS

  • 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
Copy link
Author

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

@Fourdee Fourdee modified the milestones: v6.13, Prototyping Aug 13, 2018
@carlosedp
Copy link
Author

@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
            RedScorpio@land.ru

        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
Copy link
Collaborator

Fourdee commented Aug 16, 2018

@carlosedp

Ah yes, I repacked the .img for the image we uploaded: REMOVED AS NO SINGLE INSTALL FOR MONTHS

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

@MichaIng
Copy link
Owner

MichaIng commented Oct 19, 2018

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

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

@carlosedp
Copy link
Author

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
Copy link
Owner

MichaIng commented Jan 27, 2020

@carlosedp
I created a new Buster image, based on Armbian with Linux mainline kernel 5.4: REMOVED AS NO SINGLE INSTALL FOR MONTHS
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 MichaIng modified the milestones: Prototyping, v6.29 Jan 27, 2020
@MichaIng MichaIng added the Solution available 🥂 Definite solution has been done label Mar 9, 2020
@MichaIng MichaIng modified the milestones: v6.29, v6.30, v6.31 May 3, 2020
@MichaIng
Copy link
Owner

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.

@belveder79
Copy link

@Fourdee I would be very interested in testing your image and hear if you are still actively using the firefly board...

@MichaIng
Copy link
Owner

MichaIng commented Apr 6, 2022

We had a Firefly RK3399 image for about two years, but there were nearly zero users, according to our survey, hence we removed this image from our list.

But if you have such SBC, you can turn a Debian or Armbian image into DietPi, by making use of our PREP script: https://dietpi.com/docs/hardware/#make-your-own-distribution
There is a "Generic Rockchip RK3399" hardware ID which can be selected.

@belveder79
Copy link

Ok I will give this a try. As I'm struggling right now to get basically ANY image to work with this SBC, I can understand why people are reluctant to use it with anything else than the android 7 image it ships with...

@MichaIng
Copy link
Owner

MichaIng commented Apr 6, 2022

At least for common server usage, Android is indeed a questionable OS 😉. Let me know if you run into any issues. One AFAIK was that network connections can be dropped in the middle, when they are managed by connman or NetworkManager, so best is to run the script with screen and keyboard attached (instead of SSH), so you are able to re-establish the network connection from the related error prompt, if necessary.

@belveder79
Copy link

@carlosedp do you still have those flashable images and some instruction how to flash it to emmc without an adaptor?

I am close to use a nail and a hammer and use this board as a decorative element on the wall for my office...

@carlosedp
Copy link
Author

@belveder79 It's been a looong time since I don't play with it... I think I gave this board away in a "purge" I did a while back.
Sorry, I'd try the Armbian image from https://www.armbian.com/firefly-rk3399/.

@MichaIng
Copy link
Owner

Jep, using the Armbian Bookworm image, then running our installer and choosing "Generic RK3399" should work: https://dietpi.com/docs/hardware/#make-your-own-distribution

@belveder79
Copy link

@MichaIng @carlosedp yes, this indeed worked flawlessly, thx a lot...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Image request 💾 Solution available 🥂 Definite solution has been done
Projects
None yet
Development

No branches or pull requests

4 participants