RK3566 Embedded Terminal and BSP Adaptation | 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 completed and delivered an RK3566 embedded terminal and BSP adaptation project, from customer requirements and contract scope through hardware and software design, physical testing and delivery. The case focused on a compact display-oriented board, where the selected panel and FPC peripheral connections shaped the integration work.
Making the terminal’s interface choices explicit
The project’s documented architecture prioritises a compact terminal rather than exposing every RK3566 interface. It pairs LPDDR4 memory and eMMC storage with a 40-pin FPC carrying USB, I2C, SPI, microphone and speaker signals. AP6212 provides the wireless path, while the RK809 codec serves the headphone audio path.
Requirements and contract scoping linked the terminal task to the available hardware connections. Ethernet, eDP and HDMI are not routed in this layout. A product needing those interfaces requires a hardware review; software configuration cannot create an absent signal path.
Developing the board and panel-specific software scope
Obeita completed hardware and software design for the agreed terminal and BSP work. The technical focus was matching the compact board to the selected MIPI display and touch interface, with the panel connection, timing and driver requirements treated as related integration inputs.
The documented design uses a fine-pitch, six-layer board approach. In similar projects, assembly quality and DDR behaviour need to be considered alongside BSP bring-up. Panel-specific porting should include boot and suspend/resume checks in the new project’s requirements; those behaviours cannot be inferred from the processor model.
Separating terminal delivery from later expansion
The source architecture considered an OV2640-class camera connection, cellular/GNSS expansion and portable power options. These directions do not establish validated camera support or battery-transition behaviour. Before agreeing a portable-terminal specification, power-path continuity and charge/discharge transitions, including the IP5209 power-switching arrangement, require measurements on the assembled board.
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 | RK3566 |
| Memory | 4 GB LPDDR4 |
| Storage | 32 GB eMMC |
| Radio / audio | AP6212; RK809 codec |
| Peripheral connector | 40-pin FPC; USB/I2C/SPI/audio signals |
| Not routed | Ethernet, eDP and HDMI in this layout |
Delivery outcome and test scope
The agreed RK3566 terminal hardware and software were completed and delivered. Physical functional testing confirmed that the project met the customer’s requirements.
This functional completion applies to the contracted terminal scope. It does not extend to interfaces absent from the board, every possible MIPI panel, the considered camera path, or unconfirmed battery and power-transition extensions.
Discuss a similar project
Send Obeita the intended panel datasheet, touch-controller details, FPC definition and any portable-power requirements. A similar terminal project can then separate the display/BSP integration from hardware changes and optional expansion.