Firefly Open Source Community

Title: PCIe M.2 SSD on FireFly RK339 Findings [Print This Page]

Author: rpk.firefly Time: 5/23/2018 05:31
Title: PCIe M.2 SSD on FireFly RK339 Findings
Last edited by rpk.firefly In 5/23/2018 05:33 Editor

Well I didn't hear back on the forum or from the sales dept. at FireFly.

I did however find the following post over on the Armbian forums by a rather opionated dude, last September. He seems soured due to the misleading PR FireFly put out (and still use):

If you refer to the Firefly Kickstarter page this is just an insane BS collection. I only know that they use an M.2 B key slot which is able to transport a couple of totally different protocols (see here). M.2 B key can either be used for PCIe 2.x x2 or SATA or USB3 (or maybe it's not 'or' but 'and' instead and the highspeed data lines are different ones allowing more than one such a protocol at the same time). Mentioning this theoretical SATA capability by Firefly marketing is of course misleading since RK3399 has no SATA capabilities and for SATA being usable on the M.2 slot there's missing something: a PCIe SATA controller needing another PCIe lane sitting somewhere on the Firefly around (as usual Kickstarter marketing was successful in fooling a lot of users trying out M.2 SATA which simply can not work on this board).

He goes on a little more, but ends with this:

RK3399 is a great SoC for many use cases (attach displays, attach cameras, attach USB peripherals and do with it for what it's designed for: consuming media) but unless someone provides real performance numbers when trying to combine the SoC with reasonable storage controllers I think it's better to ignore this potential use case here. And 'providing real performance numbers' is IMO not that easy since needing the necessary equipment and skills (experts in embedded area are usually missing)

However, someone replies:

According to the Firefly schematic, the M2-B connector on the top has the 4 PCIe lanes, USB 2.0 and I2C connected
The mPCIe connector on the bottom has only USB 2.0 connected.

The PCIe adapter sits on the upper part of the board, so in theory it has access to the 4 PCIe lanes, but who knows whether they all get used by it.

It sounds like some other board resellers are only utilizing a single lane for their adapters.

I'm glad I didn't bother with the FireFly SATA adapter - I doubt it gets any faster speeds than my Samsung T5 connected via USB 3.0, which seems to average 350 MB/sec read/write.

I still don't know if an M.2 SSD is even able to be used for linuxrootfs (Linux root). It looks like FireFly's Ubuntu .img file doesn't have the capabilities added and you need to build a custom kernel.

I would assume that root=/dev/nvmeXXX would be available to set via a CMDLINE flash, but I haven't heard of anyone actually doing this yet.

It sounds like a total crap-shoot, meaning gamble as to whether it works.

At this point my guess is that if they use 2 lanes, *perhaps* 1000 MB/sec is possible. I'll probably order an adapter anyway and an M.2 SSD and give it a shot.

This post will end up being scraped by google, so anyone researching before purchasing a Fly RK3399 will get a heads up.

Author: ballsystemlord Time: 9/27/2018 00:07
That "opinionated dude" saved me a headache and a lot of money by mentioning that M.2 SATA support was nonexistent.
It's sad, even "opensouce" stuff is becoming really junky. Was it this way to begin with?
Did you ever get your M.2 SSD up and running?
Thanks!

Author: leung先森 Time: 9/30/2018 11:05

ballsystemlord Posted at 9/27/2018 00:07
That "opinionated dude" saved me a headache and a lot of money by mentioning that M.2 SATA support w ...

M.2 NGFF ?
Firefly RK3399(B-key) i had tested the SAMSUNG EVO96 / Intel 600P SSD .
It worked fine, but need to use PCIe M.2 to SSD Adaptor.
If you want support SATA , it need PCIe M.2 to SATA3.0 Adapter

If your board is AIO-3399J((M-key)) , just use nvme SSD (SATA do not support), no need to use Conversion Module .

Author: jkampl Time: 12/3/2018 05:50
Hello,
I have the Firefly RK3399 4GB/32GB i Have the .m2 to Sata adaptor from firefly-shop, with a Samsung Evo 860.
Iam using the firefly Xubuntu Image. The ssd is not recognized.
Honestly Iam also quite disappointed. The support chain for this boards is reallyy unorganized. For Example some Downloads are only available via Baidu. Tried to download , you get a chinese language baidu drive client. So I cant download certain resources. Answers in the threads are inconsistant, some just BS.
Sad because if you look How good the Rockchip Kernel is for this sock, basics should work better..
We want to develop applications and not fixed buggy OS features.

If someone have a solution for my SSD issue, i really will apprecheate

Author: penguin Time: 12/4/2018 18:13
Which firmware do you use, jkampl?

We'll look into this.

Author: jkampl Time: 12/7/2018 01:05
Hello Peguin ,Thanx for your interest in my issue.
I have used the Ubuntu 16.04 image original offered here, and upgrated it and just to check I have now upgraded to 18.04, I will try the last download of Ubuntu 18.04 this weekend

Author: penguin Time: 12/7/2018 11:09
jkampl, FYI http://bbs.t-firefly.com/forum.p ... &fromuid=619799

Author: penguin Time: 12/7/2018 16:04
jkampl, we happen to buy the same model of the SSD disk: Samsung Evo 860.

We've tried it with the ".m2 to Sata adaptor from firefly-shop", which works like a charm
in Ubuntu 16.04.2 firmware.

Author: jkampl Time: 12/9/2018 22:52
Hello Penguin!

Thanx for your inputs.
I flashed the newest Ubuntu Image 18.04, and lucky me it works now as well. I guess that there are some firefly specific updates not automatically installed. Is there a firefly repro to add for updating e.g. the Kernel via a normal update procedure?
I now will have a look to Video HW accelaration.

Author: penguin Time: 12/13/2018 09:12
There're no kernel or rockchip deb repositories for the normal update procedure, I'm afraid.

Welcome Firefly Open Source Community (https://bbs.t-firefly.com/)