I’m looking for informations on how to set various jumpers (M.2 slot power, NAND-NOR, etc.), how to enable RTC (I have inserted a CR1220 battery, but RTC does not appear), which disk type can I insert on the M.2 slot or on the mPCIe slot. I’m using the latest OpenWRT SNAPSHOT. Except those problems, all is working as espected…
Thank you.
Official OpenWrt needs the DesignWare I2C package installed to support I2C (which is needed for RTC). You can manually install kmod-i2c-designware-platform. I2C0 works fine, I2C1 gives an error message (after enabling it in the DTS).
To switch from NAND to NOR, you need to flip the two jumpers next to the 26 pin header (i.e., || instead of =), but this will not help you unless you write something to the NOR flash beforehand – I got my unit with completely empty NOR (bootloader, factory and firmware are all FF’s).
Some PCIe cards are not detected (at least in the miniPCIe slot), some are. Cause is unknown. It could be a good idea to have a list of what was tried. My experience: MT7925 (via m.2 to miniPCIe adapter) isn’t detected, Intel 7260AC is.
NVME m.2 2242 worked for me in the m.2 slot after installing kmod-nvme.
In my unit, Ethernet port LEDS don’t work for any GbE ports (2.5GbE port LEDs work). Couldn’t find any datasheet of Ethernet PHYs SF23P1240 and SF23P1211, but probably that’s something that can be fixed in the DTS or in a driver.
Thank you very much: rtc works now! But (installed a new battery a month ago)…
[12781.750382] rtc-pcf8563 0-0051: low voltage detected, date/time is not reliable. [12781.757992] rtc-pcf8563 0-0051: registered as rtc0 [12781.763120] rtc-pcf8563 0-0051: low voltage detected, date/time is not reliable. [12781.770602] rtc-pcf8563 0-0051: hctosys: unable to read the hardware clock
Also my NOR is empty: I tried to flip jumpers with no results, obviously being NOR empty… Was just a question because I found NOR firmware on OpenWRT… I have a NVME M-Key and bought a M to B key adapter: it works well, luckily…
root@lapalma:~# lspci 0000:00:00.0 PCI bridge: Device 1a0a:abcd (rev 01) 0001:00:00.0 PCI bridge: Device 1a0a:abcd (rev 01) 0001:01:00.0 Non-Volatile memory controller: Phison Electronics Corporation PS5021-E21 PCIe4 NVMe Controller (DRAM-less) (rev 01)
Thank you again!
Piero.
At first I got the same low voltage warning; not sure how I got rid of it (it just started working at some point). Maybe try to reseat battery?
NOR firmware can be built, but we need a NOR bootloader too. Maybe OpenSBI can be compiled for NOR? no idea here.
BTW, installing nvme-cli failed for me, since some kernel option (URING_IO something) needs to be enabled. But even after enabling it I couldn’t compile liburing.
P.S. I found the LED initialization in Sinovoip’s Ethernet PHY driver, will try to port this to kernel 6.12.
Now I’m very far from the device and can only acces it remotely, so I cant do anything hardware, and I want no risk something that will block it. At following restart (automatically each night) the low voltage error disappeared. Now I’m very interested on a way to enable Ethernet leds… Thank you again.
Ciao, Piero.
Glad to hear RTC is working for you too now 
Meanwhile I got the 2nd I2C channel working too, so I2C pins on the GPIO header can be used (already committed to snapshot).
I added the LED initialization code from SinoVoip’s kernel (and fixed one typo there…) but this still doesn’t work as expected. I’ll open a draft PR with what I have, maybe someone could shed some light on it. Maybe I’ll also open an issue about the PCIe situation, where people could contribute their datapoints.