RK3399 M.2 SATA

friism

Nope, there's no such device as `/dev/block/nvme0n1p1`

friism

1. firefly@firefly:~/Desktop$ dmesg | grep pci
   
2. [    0.270194] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
   
3. [    0.270341] vcc3v3_pcie: no parameters
   
4. [    0.270373] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0uV
   
5. [    0.366993] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
   
6. [    0.367002] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
   
7. [    0.367027] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
   
8. [    0.367262] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
   
9. [    0.367273] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed
   
10. [    0.367286] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
    
11. [    0.367858] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
    
12. [    0.367868] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
    
13. [    0.367878] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
    
14. [    0.368435] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
    
15. [    0.368444] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
    
16. [    0.368453] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
    
17. [    0.910817] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
    
18. [    0.911459] rockchip-pcie: probe of f8000000.pcie failed with error -110
    
19. [    1.053521] ehci-pci: EHCI PCI platform driver
    
20. [    1.068234] ohci-pci: OHCI PCI platform driver
    

Copy the code

friism

1. ls /dev/block/
   
2. 179:0  179:1  179:2  179:3  179:32  179:4  179:5  179:6  179:64  179:96  1:0  1:1  1:10  1:11  1:12  1:13  1:14  1:15  1:2  1:3  1:4  1:5  1:6  1:7  1:8  1:9  254:0  7:0  7:1  7:2  7:3  7:4  7:5  7:6  7:7
   

Copy the code

friism

Will this work if I get your m.2 to SATA connector? http://shop.t-firefly.com/goods.php?id=52 The only reason I didn't get that one was that shipping was expensive.

饿客登门

rk3399 only support nvme ssd..

friism

rk3399 only support nvme ssd..

...ok - why then is Firefly selling a SATA adapter? http://shop.t-firefly.com/goods.php?id=52

mmind

Just to note, Firefly's M.2-Sata adapter works nicely with my 2.5" harddrive here. I'm of course working with a mainline kernel, but remember even the vendor kernel that was on the board before did recognize the harddrive with the adapter.

Also the actual sata support seems to be sitting on the adapter board, as there is that unlabeled 48-pin IC on it, which according to lspci is a
01:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 02)

friism

So you're using the adapter from the Firefly shop? Also, what instructions do you use to build a normal kernel?

mmind

Correct, the adapter from the shop. The firefly devicetree will make its way into kernel 4.13, so some time next week take linux-next, the arm64 "defconfig", enable rockchip pcie options (ip block and phy I thing) and just build a kernel using your favorite arm64 cross compiler.

You might also want to drop the vendor uboot and move the something resembling mainline. Rockchip arm64, atf and firefly patches are still in-flight, so I've collected the necessary things and am using https://github.com/mmind/u-boot- ... /tmp/rk3399-firefly right now. With that you can just use extlinux to boot things from usb-devices, emmc or whatever.

friism

Heiko!

Can I start building https://github.com/mmind/linux-rockchip/tree/tmp/rk3399-firefly in the interim before the changes are in linux-next?