M.2 PCIE is it powered on?

enrogued

I'm having issues with the RK3399 even recognising that there is a PCIE bus let alone getting it to work

It appears from the following that the voltage regulator is not configured to feed the pcie:

1. [    0.261544] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
   
2. [    0.261597] vcc3v3_pcie: no parameters
   
3. [    0.261735] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0uV
   
4. [    0.261850] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-3g-regulator[0]' - status (0)
   
5. [    0.261889] vcc3v3_3g: no parameters
   
6. [    0.262014] reg-fixed-voltage vcc3v3-3g-regulator: vcc3v3_3g supplying 0uV
   
7. [    0.262067] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc3v3-sys[0]'
   
8. [    0.262102] vcc3v3_sys: 3300 mV
   
9. [    0.262217] reg-fixed-voltage vcc3v3-sys: vcc3v3_sys supplying 3300000uV
   
10. [    0.262357] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc5v0-host-regulator[0]' - status (0)
    
11. [    0.262394] vcc5v0_host: no parameters
    
12. [    0.262511] reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 0uV
    
13. [    0.262559] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc5v0-sys[0]'
    
14. [    0.262579] vcc5v0_sys: 5000 mV
    
15. [    0.262693] reg-fixed-voltage vcc5v0-sys: vcc5v0_sys supplying 5000000uV
    
16. [    0.262738] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc-phy-regulator[0]'
    
17. [    0.262752] vcc_phy: no parameters
    
18. [    0.262875] reg-fixed-voltage vcc-phy-regulator: vcc_phy supplying 0uV
    
19. [    0.262925] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vccadc-ref[0]'
    
20. [    0.262940] vcc1v8_sys: 1800 mV
    
21. [    0.263055] reg-fixed-voltage vccadc-ref: vcc1v8_sys supplying 1800000uV
    
22. [    0.263188] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc-lcd-regulator[0]' - status (0)
    
23. [    0.263224] vcc_lcd: no parameters
    
24. [    0.263337] reg-fixed-voltage vcc-lcd-regulator: vcc_lcd supplying 0uV
    

Copy the code

but some of the other bits are configured to provide power. I've been looking at the device tree files, but I'm a bit stuck as to what is missing - I don't really know what the gpio parameters are, and the only thing I can think of doing is setting it to be always on by setting it's voltage parameter to 3300000 in the dts like it is for vcc3v3_sys


any ideas?

shermanp

Same issue here. Two Firefly RK3399's, brand new, ordered and received about a month apart. Wondering about some physical board mis-configuration/installation or removal of 0-Ohm options/etc. Here is a dmesg | grep pci output:
[    0.235599] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3
-pcie-regulator[0]' - status (0)
[    0.235647] vcc3v3_pcie: no parameters
[    0.235804] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0u
V
[    0.342952] phy phy-pcie-phy.5: Looking up phy-supply from device tree
[    0.342962] phy phy-pcie-phy.5: Looking up phy-supply property in node /pcie-
phy failed
[    0.344882] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    0.344892] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    0.344919] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pc
ie@f8000000[0]' - status (0)
[    0.345159] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from devi
ce tree
[    0.345170] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property
in node /pcie@f8000000 failed
[    0.345184] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[    0.345746] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from devi
ce tree
[    0.345755] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property
in node /pcie@f8000000 failed
[    0.345766] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    0.346338] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from devi
ce tree
[    0.346347] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property
in node /pcie@f8000000 failed
[    0.346358] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    0.888882] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    0.889603] rockchip-pcie: probe of f8000000.pcie failed with error -110
[    1.038857] ehci-pci: EHCI PCI platform driver
root@firefly:~# parameters
-bash: parameters: command not found
root@firefly:~# dmesg | grep pci | more
[    0.235599] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3
-pcie-regulator[0]' - status (0)
[    0.235647] vcc3v3_pcie: no parameters
[    0.235804] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0u
V
[    0.342952] phy phy-pcie-phy.5: Looking up phy-supply from device tree
[    0.342962] phy phy-pcie-phy.5: Looking up phy-supply property in node /pcie-
phy failed
[    0.344882] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    0.344892] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    0.344919] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pc
ie@f8000000[0]' - status (0)
[    0.345159] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from devi
ce tree
[    0.345170] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property
in node /pcie@f8000000 failed
[    0.345184] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[    0.345746] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from devi
ce tree
[    0.345755] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property
in node /pcie@f8000000 failed
[    0.345766] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    0.346338] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from devi
ce tree
[    0.346347] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property
in node /pcie@f8000000 failed
[    0.346358] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    0.888882] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    0.889603] rockchip-pcie: probe of f8000000.pcie failed with error -110
[    1.038857] ehci-pci: EHCI PCI platform driver

mazze

Hi everybody,

did you manage to get the PCIe on the NGFF working?
I myself also have an RF3399 with the intent to use it as a storage server by using this PCIe 2.0 to 4x SATA adapter
https://www.delock.com/produkte/G_62850/merkmale.html
Unfortunately it didn't work right from the start (same messages as you see). So there is obviously stuff to do with the device tree but after measuring the PCIE_3V3 signal I found that the supply voltage from U15 is there.
The main issue seems so be differrent:   
M.2 has 4 config pins
config_0 : Pin 21
config_1 : Pin 69
config_2 : Pin 75
config_3 : Pin 1
as described here  http://pinoutguide.com/HD/M.2_NGFF_connector_pinout.shtml
If you look at the schematic you can get the impression that config_0 is not connected and the others are connected to GND (with the caveat that the Pin numbers in the schematic does not match the official pin numbers, e.g. config_0 is numbered 13 instead of 21).  
This would mean the board will only be able to accept WWAN-SIC (if config_0 is left open) or SATA (if config_0 is tied to GND on the m.2 card).
http://download-c.huawei.com/dow ... er?downloadId=18428
http://www.computex.biz/PhotoPool2/201406/201406251407499629.pdf

Unfortunately for me my PCIe > SATA adapter pulls config_1 to PCIE_3V3 (which leads to high current consumption and is also not correct).

So I have some questions to the Firefly Team:
- Can you provide a schematic with correct config pin numbers
- Why did you connect all this config pins to GND instead of pull them up to PCIE_3V3 and route them to GPIO as proposed here https://mindchasers.com/dev/m2-connectors ?
- Is config_1 (pin69) actually connected to GND (without a 0 Ohm bridge)
  - If so, can you provide a board layout with this line highlighted so I can (hopefully) scratch it off?

Best regards,
Mathias

radfish

FWIW, had the same -110 error with M.2 SATA card (ASM106x chipset) on NanoPC-T4 (RK3399) with 4.4.x from FriendlyARM and from Rockchip, but problem went away on mainline 5.8.5. Details here: https://discuss.96boards.org/t/p ... rd/9643/7?u=redfish

philipp.ludwig

@radfish how did you manage to run 5.8.5 on the device?