4004 R5S R5C R6S R6C 4G WiFi EN

Keywords

FriendlyElec NanoPi R5S, R5C, R6S, R6C, RK3568B2, RK3588S, USB3.2, M.2 NVME, WiFi6, 4G LTE, FriendlyWrt, OpenWrt, Debian, Ubuntu

I. Introduction

By leveraging the NanoPi R5S/R6C's PCIe M.2 M-KEY NVMe SSD interface, we can expand it into various interfaces, combining multi-network ports, lightweight NAS, and video playback in one compact system. Perfect for IoT development, tinkering, and creative exploration, it unlocks endless possibilities for unique projects.

NanoPi R5S (abbreviated as "R5S") is a development board designed by the FriendlyElec team, featuring three network ports (dual 2.5G Ethernet + Gigabit Ethernet). It uses the Rockchip RK3568B2 as its main processor, equipped with 4GB LPDDR4x RAM and 32GB eMMC flash storage. It also supports booting from a TF card and running OSs like FriendlyWrt. The R5S features a rich set of interfaces with a compact layout, and its motherboard measures only 90x62mm. It can be paired with an integrated CNC-machined aluminum oxide shell. It features one HDMI output port and can run OSs such as Android, Buildroot, and Ubuntu Desktop, as well as serve as a command-line mode favored by geeks. It also supports decoding and playback of 4K60p H.265/H.264 videos.

The NanoPi R5C is a streamlined version of the R5S, with a built-in Wi-Fi interface and support for external 4G module expansion.

NanoPi R6C (abbreviated as "R6C") is an open-source, high-performance all-in-one edge computing platform designed and produced by the FriendlyElec team. It features dual network ports, including a 2.5G and a Gigabit Ethernet port. Powered by the Rockchip RK3588S as its main processor, it comes with 4GB/8GB LPDDR4x RAM and optional 32GB eMMC flash storage. The device supports multiple OSs, including FriendlyWrt, Android, Debian, and Ubuntu, and offers GPU and VPU acceleration.

The R6C features a rich set of interfaces and a compact layout, with a motherboard size of only 90x62 mm. It comes with a 30-pin GPIO, including general-purpose I/O ports, I2C, I2S, PWM, and SPI interfaces. Additionally, it is equipped with an HDMI output port capable of decoding and playing videos in formats up to 8K@60fps H.265/VP9, as well as 8K@30fps H.264. For developers' convenience, the R6C also comes with a built-in USB-to-serial converter and is equipped with a USB Type-C port.

The R6C also comes with one M.2 NVMe SSD slot, one USB 3.0 port, and one USB 2.0 port, and supports the currently popular PD fast charging (USB-C port), eliminating concerns about insufficient power when connecting external hard drives. Additionally, an optional integrated CNC-machined aluminum oxide shell is available for installation.

II. Extended peripherals

2.1. NVMe to WiFi6 adapter board

This adapter board converts the PCIe M.2 M-Key interface for hard drives on the R5S/R6C into an M.2 A-Key WiFi interface. In terms of hardware, it can be used to connect WiFi6 modules such as the MT7922, MT7921K, AX210, and AX200. It also supports WiFi5 modules like the Intel 8265C, and it can even connect to Google's Coral TPU module, the R5S can recognize the TPU device.

The hardware requires corresponding drivers in the OS to function. The latest OS for Nano Pi supports the MT7922 and MT7921.

The adapter board is 2.9mm thick and can be fully embedded inside the R5S device without the need to replace the base.

The adapter board reserves the USB Bluetooth interface for the WiFi module, with a 1.25mm-4P connector. To use Bluetooth, this interface needs to be connected to the USB port of the R5S, and Bluetooth drivers and applications are required. If Bluetooth is used, its thickness of 4.2mm makes it incompatible with the original R5S dock. You can choose to equip a 3D mounting bracket to raise the dock or replace the dock altogether.

This adapter board is compatible with three models: NanoPi R5S, R6C, and M6.

2.2. NVMe to dual WiFi6 adapter board

This adapter board utilizes a switch chip to split the PCIe interface of the R5S's M.2 M-KEY SSD slot into two channels, expanding the original SSD slot into two M.2 A-KEY interfaces. In terms of hardware, these interfaces can be used to connect WiFi6 modules such as the MT7922, MT7921K, AX210, or AX200, as well as WiFi5 modules like the Intel 8265C.

The hardware requires corresponding drivers in the OS to function. The latest FriendlyElec's OSs for Nano Pi supports MT7922 and MT7921K, which can function as a wireless repeater—one WiFi connects to the upstream router, and another WiFi acts as an AP to share the hotspot.

The adapter board reserves a USB Bluetooth interface for the WiFi module itself, with a 1.25mm-4P connector. If Bluetooth functionality is required, this interface needs to be connected to the USB port of the R5S, along with the necessary Bluetooth drivers and applications.

The thickness of the adapter plate is 4.2mm, it needs to be used with a 3D fixing frame, and the original CNC shell base of the R5S machine can still be utilized.

This adapter board is compatible with two models: NanoPi R5S, R6C.

2.3. NVMe to SSD+WiFi7 adapter board

This adapter board utilizes a switch chip to split the PCIe interface of the R5S's M.2 M-KEY SSD slot into two channels, expanding the original SSD slot into one SSD interface and one M.2 E-KEY WiFi7 interface.

The SSD interface supports NVMe SSDs in 2242/2280 sizes, with the 2280 mounting post pre-soldered by default.

The M.2 E-Key interface can be used to connect WiFi7, such as the BE200 and MT7925, as well as WiFi6 devices like the MT7922, MT7921K, AX210, and AX200. It also supports WiFi 5 modules, such as the Intel 8265C. The hardware requires corresponding drivers in the OS to function properly. The latest FriendlyElec's OSs for Nano Pi supports MT7922 and MT7921K.

The adapter board reserves the USB Bluetooth interface for the WiFi module, featuring a 1.25mm-4P connector. To use Bluetooth, this interface must be connected to the USB port of the R5S, and Bluetooth drivers and applications are required.

The thickness of the adapter plate is 4.2mm; when used with the 3D mounting frame, it remains compatible with the machine's original CNC enclosure base.

This adapter board is compatible with two models: NanoPi R5S, R6C.

2.4. NVMe to WiFi6+4G adapter board (with fixing holes)

This adapter board converts the R5S's hard drive interface from PCIe M.2 M-KEY to M.2 A-KEY WiFi6, while also adding mounting holes for a 4G module.

The M.2 A-KEY interface can be used to connect WiFi6 modules such as the MT7922, MT7921K, AX210, and AX200. It can also support WiFi5 modules like the Intel 8265C, and even Google's Coral TPU module, which can be detected by the R5S. For the hardware to function, the corresponding drivers must be available in the system. The latest system from Nano Pi supports the MT7922 and MT7921K.

The adapter board reserves the USB Bluetooth interface for the WiFi module, with a 1.25mm-4P connector. If Bluetooth functionality is required, this interface must be connected to the USB port of the R5S/R6C, along with the necessary Bluetooth drivers and applications.

The 4G fixing hole is designed for our company's CM4 4G mini module. The 4G module is a USB device, which connects to the USB port of the R5S machine via a 1.25 4p USB cable. The latest FriendlyElec's OSs for Nano Pi supports 4G, offering plug-and-play functionality with auto-identification, eliminating the need for additional drivers.

This adapter board is compatible with two models: NanoPi R5S, R6C.

This adapter board converts the R5S's PCIe M.2 M-KEY hard drive interface into a USB port, connects the USB to 4G, and features an onboard Nano SIM card slot. The latest FriendlyElec's OSs for Nano Pi supports 4G, supports 4G with plug-and-play functionality, auto-identification without the need for additional drivers.

This adapter board is compatible with two models: NanoPi R5S, R6C.

2.6. 4G carrier board

2.6.1 The 4G carrier board for R5S/R6C/R6S

This is a carrier board designed for the R5S based on our company's CM4 4G mini module. It can be assembled at the bottom of the R5S. The 4G module is a USB device connected to the USB port of the R5S via a 1.25mm 4-pin USB cable. Both the latest FriendlyElec's OSs and the newest iStore OS support 4G connectivity.

This adapter board is compatible with three models: NanoPi R5S, R6C, and R6S.

2.6.2 The 4G carrier board for R5C

Based on our company's CM4 4G mini module, we have designed a 4G carrier board compatible with the R5C, and redesigned a 3D-printed base to replace the original R5C shell base, integrating the 4G antenna internally.

The 4G module is driver-free and auto-identification in both the latest FriendlyElec's OSs and the newest iStore OS, requiring no additional driver installation.

2.7. Note for 4G

Our company offers multiple 4G models. Under FriendWrt, the Qualcomm 4G/Qualcomm 4G-GPS module and NL668-EU/EAU/AM 4G module and the R5S can be auto-identification upon startup when assembled together. However, other modules such as the CAT4 4G/ZTE CAT4/ZTE CAT4-EU module need to be inserted after FriendWrt has booted up. Otherwise, the network interface order may become disordered due to the 4G module being recognized earlier than the network card, which could prevent access to the backend.

III. Work with FriendlyWrt

No matter which adapter board is used, the operation methods for 4G and WiFi are the same.

▶ The 4G modules used are Qualcomm 4G/Qualcomm 4G-GPS, NL668-EU/EAU/AM 4G, CAT4 4G/ZTE CAT4/ZTE CAT4-EU. The 4G modules are driver-free, meaning the firmware comes with built-in drivers and is auto-identification, requiring no additional driver installation.

▶ The WiFi module used is the MT7922, whose driver is the same as that of the MT7921K. The WiFi module requires firmware with a driver to enable WiFi functionality.

The WiFi module can operate in AP mode (as a wireless hotspot). In this mode, the 4G module serves as the WAN, while the WiFi acts as the LAN (wireless hotspot), providing wireless internet access for other devices.

▶ R5S/R5C: The tested FriendlyWrt's version is: rk3568-eflasher-friendlywrt-23.05-20241112.img.gz, and boot from the eMMC.

You can download it in:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S/zh#.E4.B8.8B.E8.BD.BD.E5.9B.BA.E4.BB.B6

▶ R6S/R6C: The tested FriendlyWrt's version is: rk3588-eflasher-friendlywrt-23.05-20241112.img.gz, and boot from the eMMC.

You can download it in:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6C/zh#.E4.B8.8B.E8.BD.BD.E5.9B.BA.E4.BB.B6

3.1 The operation of the 4G module

3.1.1 Identify the 4G module

The 4G module is used as the WAN port in the FriendlyWrt. Connect the LAN port of the R5S/R5C/R6S/R6C to the PC's Ethernet port using a network cable. Power on the OS, then open the browser on the PC and navigate to 192.168.2.1 to access the FriendlyWrt's backend page (default username: root, password: password).

Click on "Services - Terminal," then log in to the terminal:

The default username is root, and the password is the "password":

Execute ip addr, and the result is as follows, usb0 is the Qualcomm 4G (or Qualcomm 4G-GPS, or NL668-EU/EAU/AM 4G):

If it is a CAT4 4G/ZTE CAT4/ZTE CAT4-EU module, it will be recognized as eth3 or eth2 (depending on the number of wired network ports on the device), as shown in the figure below:

Note 1: The numbering of eth interfaces is based on the number of the device's own network ports, starting from 0. For example, the R5S has 3 network ports, so its own ports are numbered eth0, eth1, and eth2, and the 4G interface will be eth3. For the R5C/R6C, which have 2 network ports, the device's own ports are eth0 and eth1, and the 4G interface will be recognized as eth2.

Note 2: Modules such as the CAT4 4G must be inserted into the USB port only after the FriendlyWrt system has fully booted. Otherwise, the computer will not be able to obtain the correct IP address, making it impossible to access the FriendlyWrt backend configuration page.

Note 3: If you are using third-party firmware and the eth or usb0 device does not appear in the terminal, it means the firmware was not compiled with the 4G driver, and thus 4G cannot be used. In this case, you will need to replace the firmware.

3.1.2 Set the 4G module as WAN

Click "Network - Interfaces" - "Add new interface...":

Configure as shown in the figure (the "Name" can be customized), Device selection: "usb0" (Qualcomm 4G/Qualcomm 4G-GPS, or NL668-EU/EAU/AM 4G) or "eth3" (or "eth2", varying based on the number of wired network ports on the device, CAT4 4G/ZTE CAT4/ZTE CAT4-EU), then click "Create Interface".

In the "Firewall Settings", set "Create/Assign firewall-zone" to "wan", then click "Save":

Return to the previous page, click "Save & Apply":

After a short wait, we can see that the 4G module has obtained an IP address:

Then we return to the terminal and execute ifconfig -a(or ifconfig -a eth3), with the following result:

Pinging the domain name is successful, and the 4G module is working normally:

Now that the PC is online, we can run a speed test on the speed test website：

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

3.1.3 AT command operations

If you want to perform AT command operations on the 4G module, you first need to download a serial port tool. The steps are as follows:

Click on "System - Software:

Click on "Update lists..." button on the Software page:

After the update is complete, enter "minicom" in the "Download and install package" field and click the OK button.

Then click the "Install" button, wait a moment for the installation to complete, and click the "Dismiss" button to finish:

Now we can view minicom's software details on the "Installed" page:

Click on "Services - Terminal," then log in to the terminal.

Taking the Qualcomm 4G module as an example, execute the command lsusb in the terminal, as shown in the figure below:

Record the ID value of the 4G module: 05c6 90b6.

Use the following command to open the ttyUSB serial port, where the value after echo is the ID recorded above:

modprobe option

sh -c 'echo 05c6 90b6 > /sys/bus/usb-serial/drivers/option1/new_id'

After execution is complete, execute:

ls /dev/ttyUSB*

Now you should be able to see three devices under the dev directory: ttyUSB0 through ttyUSB2:

Open the AT command serial port through minicom:

minicom -D /dev/ttyUSB0

(Note: The selection of which serial port to use should be based on entering the port and being able to input AT commands without garbled characters or erratic results.)

The first time you enter an AT command, there may be no echo. If you then type at and press Enter, and it returns "OK," it means the system is working properly. If you need to check the echo, type the command: ATE1, then press Enter. Continue typing other commands and press Enter to see the echo.

Common AT commands:

1. View echo:

ate1

The first time you enter an AT command, there may be no echo. If you then input the command at and press Enter, and it returns "OK," it indicates that everything is working properly. If you need to check the echo, please type the command: ate1, then press Enter. After that, you can continue to type other commands and see the inputs.

2. Check if the SIM card is detected:

at+cpin?

Return ready to indicate the card has been recognized, if return error, you need to check the hardware.

3. Check antenna signal quality:

at+csq

Return values between 26 and 31 indicate a good signal, with 31 representing a full signal strength; return values between 20 and 25 indicate a barely acceptable signal; return values below 20 indicate a poor signal or that the antenna might not be connected.

4. Check network registration status:

at+cops?

Normally, it should return the network supporter's code: 7, where 7 represents 4G.

Note: The above command at+csq should not include a question mark, while the other two commands require a question mark.

5. View the SIM card's IMEI code:

at+cgsn

6. Reset 4G module (Sometimes, if you reinsert the SIM card, hot swapping may not work; in such cases, you can use this reset command to reset the module.):

at+reset

7. Disable radio frequency:

at+cfun=0

Enable radio frequency:

at+cfun=1

The two commands mentioned above can be used in pairs to allow the module to re-register with the network without restarting the 4G module.

3.1.4 Modify the 4G IP address

If the default 4G IP address assigned at the factory conflicts with the IP address being used by the user, or if there is a need to modify the IP address, you can change the 4G module's IP.

Qualcomm 4G/Qualcomm 4G-GPS/NL668-EU/NL668-EAU/NL668-AM, ZTE CAT4 4G:

Set the 4G module's IP to directly obtain a public IP. Please execute the AT command:

Set the IP to public: AT+GTIPPASS=1

Set the IP to private: AT+GTIPPASS=0

Check whether the current IP is a public or private IP: AT+GTIPPASS?

After modifying the IP, a power cycle reboot is required for the changes to take effect.

CAT4 4G：

Execute the AT command:

AT+ROUTEIP=<newip>

Note: only addresses in the format of 192.168.x.1 are supported. If you set AT+ROUTEIP=192.168.3.1, the final IP address obtained will be 192.168.3.100. After making the changes, you need to power off and restart the OS.

Query current IP: AT+ROUTEIP?, it returns two values, the first one is the old IP, and the second one is the new IP.

Test command: AT+ROUTEIP=?

3.2 The operation of the WiFi

3.2.1 View WiFi information

Click on "Services - Terminal," then log in to the terminal.

Execute lspci to check the information of the wireless module:

Execute ifconfig wlan0 to check the network information of the wireless module:

3.2.2 Set up a wireless network

Click "Network - Wireless" to enter the wireless settings:

click the "Add" button next to "radio0", and the "Edit Wireless Network" page will pop up:

Please set the wireless channel in the "Device Configuration - General Setup - Operating frequency" section as shown below:

In the "Device Configuration - Advanced Settings" section, set the "Country Code" to US.

Under "Interface Configuration - General Setup", enter the hotspot name (which can be customized) in the "ESSID" field, and check the "lan" option in the "Network" section.

Click on "Interface Configuration - Wireless Security", then set the encryption type (e.g., "WPA2-PSK (strong security)") and the password:

Note: Setting a key may result in the inability to connect to the wireless network. Therefore, if there is no specific need, it is recommended not to set a key, i.e., select "No Encryption (open network)".

Click on "Interface Configuration - Advanced Settings", enter "wlan1" (the name can be customized) in the "Interface name" field:

Then click "Save", return to the previous page, click "Save & Apply":

Since a reboot is required for the changes to take effect, click "System - Reboot":

If it keeps showing "Loading view", please manually power off and reboot.

3.2.3 Set up operating frequency

After reboot, return to "Network - Wireless", click the "Disable" button in the red box to deactivate the default hotspot, as only one hotspot can be active at a time.

Then click "Edit" for the newly created third wireless hotspot:

In the "Device Configuration - General Setup - Operating frequency" section, set the wireless channel as shown below:

Then click "Save", return to the previous page, click "Save & Apply":

After the page refreshes, we can see that this hotspot has been activated:

3.2.4 Connect to the hotspot and test the speed

You can connect to this hotspot using your mobile phone or other mobile devices:

In the previous section, the 4G module serves as the WAN, while the wireless hotspot acts as the LAN. Once a phone connects to it, it can access the internet via the 4G network through the wireless hotspot.

After testing the speed on a speed test website, the results are as follows:

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

IV. Work with Debian OS

R5S/R5C: The tested Debian OS's version is: rk3568-eflasher-debian-bullseye-desktop-6.1-arm64-20250123.img.gz, and boot from the eMMC.

You can download it in:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S/zh#.E4.B8.8B.E8.BD.BD.E5.9B.BA.E4.BB.B6

R6S/R6C: The tested Debian OS's version is: rk3588-eflasher-debian-bullseye-desktop-6.1-arm64-20250123.img.gz, and boot from the eMMC.

You can download it in:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6C/zh#.E4.B8.8B.E8.BD.BD.E5.9B.BA.E4.BB.B6

The 4G modules included in this test are: Qualcomm 4G, CAT4 4G, and ZTE 4G.

4.1 Qualcomm 4G module test

After the OS starts up, execute ip addr in the terminal:

From the above image, we can see that the 4G module (usb0) has successfully obtained an IP address, and we can ping external network addresses, such as:

sudo ping www.mcuzone.com

It can also connect to the external network via the 4G module and access the speed test website for testing, with the results as follows:

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

4.2 CAT4 4G module test

After the OS starts up, execute ip addr in the terminal:

From the above image, we can see that the 4G module (eth1, eth2, or eth3, depending on the number of wired network ports available on the device.) has successfully obtained an IP address, and we can ping external network addresses, such as:

sudo ping www.mcuzone.com

It can also connect to the external network via the 4G module and access the speed test website for testing, with the results as follows:

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

4.3 ZTE 4G module test

After the OS starts up, execute ip addr in the terminal:

From the above image, we can see that the 4G module (eth3 or eth2, depending on the number of wired network ports available on the device.) has successfully obtained an IP address, and we can ping external network addresses, such as:

sudo ping www.mcuzone.com

It can also connect to the external network via the 4G module and access the speed test website for testing, with the results as follows:

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

V. Work with Ubuntu OS

R5S/R5C: The tested Ubuntu OS's version is: rk3568-eflasher-ubuntu-focal-desktop-6.1-arm64-20250123.img.gz。烧写在eMMC内。

You can download it in:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S/zh#.E4.B8.8B.E8.BD.BD.E5.9B.BA.E4.BB.B6

R6S/R6C: The tested Ubuntu OS's version is: rk3588-eflasher-ubuntu-noble-desktop-6.1-arm64-20250122.img.gz。烧写在eMMC内。

You can download it in:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6C/zh#.E4.B8.8B.E8.BD.BD.E5.9B.BA.E4.BB.B6

The 4G modules included in this test are: Qualcomm 4G, CAT4 4G, and ZTE 4G.

5.1 Qualcomm 4G module test

After the OS starts up, execute ifconfig -a in the terminal:

From the above image, we can see that the 4G module (usb0) has successfully obtained an IP address, and we can ping external network addresses, such as:

sudo ping www.mcuzone.com

It can also connect to the external network via the 4G module and access the speed test website for testing, with the results as follows:

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

5.2 CAT4 4G module test

After the OS starts up, execute ifconfig -a in the terminal:

From the above image, we can see that the 4G module (eth1, eth2, or eth3, depending on the number of wired network ports available on the device.) has successfully obtained an IP address, and we can ping external network addresses, such as:

sudo ping www.mcuzone.com

It can also connect to the external network via the 4G module and access the speed test website for testing, with the results as follows:

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

5.3 ZTE 4G module test

After the OS starts up, execute ifconfig -a in the terminal:

From the above image, we can see that the 4G module (eth3 or eth2, depending on the number of wired network ports available on the device.) has successfully obtained an IP address, and we can ping external network addresses, such as:

sudo ping www.mcuzone.com

When executing the ping command, you may encounter a name server error:

Connect the LAN port to the upstream router and install the DHCP software udhcpc:

sudo apt install udhcpc

After the installation is complete, unplug the network cable and execute:

sudo udhcpc -i eth3

Once the execution is finished, ping the external address, with the following result:

It can also connect to the external network via the 4G module and access the speed test website for testing, with the results as follows:

Note: Network speed tests are affected by the network environment and testing methods. Please refer to the actual speed, as this test is for reference only.

VI. NanoPi 4G and WiFi selection guide

No.	NanoPi Model	CPU	Ethernet	Built-in 4G	Built-in WiFi	USB	Notes
1	R2S PLUS	RK3328	2	CM4 CAT4/ CM4 Qualcomm 4G/NL668-EAU/EU/AM--USB	RTL8822(SDIO)	2	1 USB left, after using 4G
2	R3S	RK3566	2	CM4 Qualcomm 4G/NL668-EAU/EU/AM-USB	None	1	No USB after using 4G
3	R5C	RK3568B2	2	CM4 Qualcomm 4G/NL668-EAU/EU/AM-USB	MT7922/8822CE	2	1 USB left, after using 4G
4	R5S LTS		3	CM4 Qualcomm 4G/NL668-EAU/EU/AM-USB	External MT7922/8822CE	2	1 USB left ,after using 4G
4	R5S LTS		3	Qualcomm 4G/NL668-EAU/EU/AM/ZTE CAT4-M.2	None	2
5	R6C	RK3588S	2	CM4 Qualcomm 4G/NL668-EAU/EU/AM-USB	External MT7922/8822CE	2	1 USB left, after using 4G
5	R6C		2	Qualcomm 4G/NL668-EAU/EU/AM/ZTE CAT4-M.2	None	2
6	M6		1	Qualcomm 4G/NL668-EAU/EU/AM/ZTE CAT4-M.2	MT7922/8822CE	3
7	R6S		3	CM4 CAT4/Qualcomm 4G/NL668-EU/EAU / AM/ZTE CAT4-USB	None	2	1 USB left ,after using 4G
8	T6 (Ver. 2301)	RK3588	2	CAT4/Qualcomm 4G/NL668-EU/EAU/AM/ZTE CAT4(miniPCIe)	MT7922/8822CE	1
9	T6 LTS	RK3588	2	CM4 CAT4/Qualcomm 4G/NL668-EU/EAU/AM/ZTE CAT4-USB	MT7922/8822CE	3+2	3+1 USB left, after using 4G
10	R4S	RK3399	2	CM4 CAT4/Qualcomm 4G/NL668-EAU/EU/AM-USB	None	2+1
11	R4SE	RK3399	2	CM4 CAT4/Qualcomm 4G/NL668-EAU/EU/AM-USB	None	2	1 USB left ,after using 4G
12	Zero2	RK3528A	1	External CM4 CAT4/ Qualcomm 4G/NL668-EAU/EU/AM-USB	MT7922/8822CE	1	No USB after using 4G

VII. Nano Pi selection guide

NanoPi Rockchip Platform Series Selection Guide. Click on the thumbnail to view the full-size image:

VIII. Summary

We only introduce the usage and operations for 4G module based on NanoPi R5S/R5C/R6C, without covering the operations and software system specific to the NanoPi R5S/R5C/R6C development board itself.

For information about the NanoPi R5S boards, please visit the FriendlyElec's website:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S/

For information about the NanoPi R5C boards, please visit the FriendlyElec's website:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5C/

For information about the NanoPi R6S boards, please visit the FriendlyElec's website:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6S/

For information about the NanoPi R6C boards, please visit the FriendlyElec's website:

https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6C/

Contact Us

QQ：8204136

Email: mcuzone@vip.qq.com

Tel: +86(0)13957118045

If there are any omissions, errors, or infringements on this page, please contact us through the above methods. Thank you!