|
|
Posted at 3/17/2019 06:00:14
Only Author
3#
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 |
|
