RK3528 Linux Network Gateway Development | Obeita
Delivered project. The completed hardware and software met the customer’s agreed requirements in testing. Specifications for a new project must be agreed separately.
Obeita delivered an RK3528 Linux network gateway project covering customer requirements, contract scope, hardware and software design, physical testing and delivery. Its engineering focus was the relationship between physical Ethernet paths and Linux network roles, with wireless and peripheral expansion bounded by the agreed application.
Turning the network topology into a board and software scope
The project centred on an IP-network appliance rather than a serial conversion task. The documented architecture uses the integrated 100 Mbps Ethernet path, a Gigabit port with RTL8211F on GMAC, and another Gigabit port with RTL8111F over PCIe. Physical port labels must match the Linux interface map; the different controller paths need explicit interface assignment and management.
Customer requirements and contract scoping established the network job to be delivered. The OpenWrt configuration direction distinguishes LAN and WAN, while VLANs, traffic controls, filtering and Samba file services are software selections that need an agreed resource and configuration scope.
Coordinating Linux integration and peripheral hardware
Obeita carried out hardware and software design for the agreed gateway configuration. The public architecture includes AP6275S wireless hardware and USB, OTG, display, audio and storage interfaces. Wi-Fi station/access-point operation and Bluetooth A2DP sink use different software paths; the available radio hardware does not make all roles a single delivered feature.
A display expansion board and a temperature-controlled fan remain separate development items in the documented architecture. For a similar appliance, peripheral loads and the selected software packages should be defined together so that expansion requirements do not become implicit acceptance criteria.
Designing for service access
Separate USB-C power and OTG connections, along with Maskrom, Recovery and Reset controls, give the architecture specific service-access considerations. Enclosure design should preserve the required entry points and clearance for the selected antenna and heatsink. Disable the OTG 5 V peripheral-power output whenever the connection arrangement could back-feed a host computer. Deployment credentials should be handled separately from development defaults.
Documented architecture and configuration
The table records the documented architecture, configuration directions and selection boundaries for this case. Optional items, firmware-dependent choices and expansion directions are not independent guarantees that every listed option was delivered. The agreed project hardware, software and functional scope define the actual delivery.
| Item | Configuration |
|---|---|
| SoC | Rockchip RK3528 |
| Ethernet | 1 × 100 Mbps + 2 × Gigabit |
| Radio | AP6275S; Wi-Fi 6 / Bluetooth 5.0 |
| USB | 4 × USB 2.0 plus OTG |
| Media / expansion | HDMI 2.0, audio, microSD, I2C/UART/SPI |
| Supply | USB-C 5 V; separate OTG power control |
Delivery outcome and test scope
The contracted RK3528 gateway hardware and software were completed and delivered. Physical functional testing confirmed that the delivered project met the customer’s requirements.
That result covers the agreed configuration and functions. It does not provide a published forwarding benchmark, claim switch-like equivalence between all Ethernet ports, or confirm delivery of every optional wireless role, software package and peripheral extension.
Discuss a similar project
Send Obeita a port-role diagram, the intended Linux or OpenWrt package requirements, wireless roles and USB peripheral loads. These inputs define a similar network gateway’s hardware paths, software configuration and service access.