Feature Request: Port for NanoPi R5S #40
Comments
|
You can use this repo for now |
|
@S199pWa1k9r Thank you for your reply! Your code works very well for me (except PCIe 3.0). I'm not familiar with EDK2, so may I ask how we can make PCIe work or where's the problem now? |
|
Hi @NN708 I'm very glad I could help. What operating system are you using on the R5S? I don't have much experience with PCIe, You can find my contacts on my website. |
I tried Debian 11, and I disabled DeviceTree while compiling to force it using ACPI. |
|
This commit adds pcie3 support to rk3588: https://gitlab.com/rk3588_linux/rk/uefi-monorepo/-/commit/7609a76bd7d8f24fcd2e7642194a2155874443c0 |
|
Well, havn't written PCIe support code for EDK2, but I have added proper FDT support for the Pine64 Quarts64, FriendlyElec Nanopi R5S and the Firefly StationPC M2 and P2. |
|
@S199pWa1k9r Hi, thanks for your fork, I flashed on a sdcard and inserted it into my R5S, with NetBSD 10 rootfs on a USB drive. Everything works quite well, except that there's no graphic output through HDMI to display. HDMI used to be working when I booted vendor provided Linux directly from sdcard. |
|
Vendor provide image is completely different than what we're using here. I think there should be HDMI support but maybe just not ready for R5S board. |
|
Out of curiosity, which image are you flashing from the I tried adding a Thanks in advance! |
|
@precurse I use a pre-built image from the fork owner. You could find the link from this thread . |
|
Note to self: use a baud rate of |
|
It's in the README 😄 |
|
@S199pWa1k9r are you building your https://personalbsd.org/download/UEFI-RK356x/NANOPI-R5S_EFI.img image directly from your Github fork? I can't find any reference to NanoPi-R5S in the Thanks! |
|
I'm working with a NanoPi R5C, and I see TianoCore output on HDMI port running img file from: I need to run RedHat 9.x, so if any changes are required I will submit PR. |
|
R5C and R5S have a lot in common. I'm trying to get R5S to work and I have R5C too. Perhaps this can be fixed, but significant changes need to be made to the implementation of PCIe in UEFI. If you build a UEFI with the correct DTB file and boot the OS in FDT mode, There are reports of successful testing of running NetBSD, OpenBSD and FeeBSD on R5S in FDT mode. Both of these devices have a maximum RAM size of 4Gb, and the VMware installer will not work on them. I'll be happy to send a PR if @jaredmcneill agrees. In my opinion, @jaredmcneill has neither R5S nor R5C in its hands. |
|
@S199pWa1k9r Can you point me to your changes? I'm interested in a project mu implementation. Was going to look at that next. I worked at Surface on the ProX (aarh64). |
|
@jwinarske Schematic: DTS: |
|
@S199pWa1k9r Sounds good. The R5C has two 2.5GB Ethernet controllers. Also only the download USB port is active. Also the USB keyboard doesn't enable UEFI, only serial terminal, then USB keyboard works. Once I can boot RHEL I'll create a mu UEFI version with additional features. |
|
Latest test UEFI for NanoPi-R5C Full UEFI image |
|
I see the updated graphic, cool. USB works on both ports. I was seeing a single 2.5GB Ethernet device prior, and am still only seeing a single controller: In the case of R5C, the M.2 card slot pin muxing needs to be setup for PCIe2.0. This is unlike the R5S. I think there are some more Board Init changes required. This is what I currently see with your update: These look odd: I do see quite a few more blkdevices now (16), which is good. Three of which are the SD Card. That would indicate the eMMC has 13 partitions. Seems the RT clock might have been affected, as I now see an error every time with timezone, date, or time cmds: Exposing the eMMC via mass storage mode might be handy. I may have some code for that. |
|
@S199pWa1k9r I'm making progress. I have all PCIe Root devices enabled and responding on the R5C. Only issue I'm seeing is eMMC is generating errors and not always working. I'll share my fork soon. |
|
R5C WIP - #51 |
|
@jwinarske |
|
@S199pWa1k9r thanks! I just need a R5S now... |
|
I just figured out the RTC issue. If the low voltage bit is set, the first clock read always ends in error. I added clearing it in board init, if set. I think the only way to avoid the bit being set is to use a coin battery. Not sure why they didn't just use the PMIC RTC, but then again I haven't yet looked at any of the errata. It's pushed to my PR. |
|
Wow, this is awesome work guys! Thanks for all the effort :) |
I found that HDMI works great after flashing the latest UEFI img here. |
Anyone tried boot from PCIe M2 on NanoPi R5S? I can boot from USB drive with the help of this UEFI image, and now I'm considering to purchase a M2 ssd drive, but not sure if it works on R5S😄. |
Not all operating systems operate the same in ACPI mode. If you can supply the correct DTB file for your version of Linux, and use FDT mode, then NVMe will most likely work. But there may be surprises. |
|
@S199pWa1k9r do you plan on submitting your changes to this branch? |
|
@jaredmcneill But PCie2.0 and PCie3.0 will not work at the same time. Will this cause any inconvenience? |
|
Maybe we should merge the changes to PCI in #51 first? |
|
I looked at this code. Yes, it will probably work. But I would also like to analyze the code for RK3588. Maybe there are a lot of similarities there. I planned to spend the next week at home and have more free time. I suggest discussing and finding the best solution. I think we can make a drastic improvement |
Hi, I flashed this uefi firmware to my R5C, and it seems work good, both hdmi and usb work. |
My device is R5S, I flash the img to sdcard, but the internal NVME SDD did not show up in boot manage, how can i fix it, I want to install OS to internal NVME SDD. |
Friendly NanoPi R5S also uses a Rockchip RK3568B2 CPU. Is it possible to have prebuilt image for this board?
The text was updated successfully, but these errors were encountered: