QCM6490 Cellular Edge Platform 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 delivered a QCM6490 cellular edge-platform adaptation project using an SG560D smart-module architecture. The work covered customer requirements and contract confirmation, carrier hardware and software design, physical testing and delivery of the agreed implementation.
Defining the edge platform around the module
This project’s focus was the interface between a smart module and its product carrier: application processing, cellular connectivity and display/camera expansion needed one consistent configuration. Obeita completed the agreed hardware and software adaptation. The public architecture describes a six-layer carrier, while the selected module version determines the applicable memory, storage, radio features and software image.
The platform material includes Kryo 670 processing, Adreno 643 graphics and LPDDR4X/UFS variants. Those family options describe a selection envelope. They are not a record that every memory or cellular variant was included in the delivered product.
High-speed I/O and shared-pin constraints
The documented carrier exposes PCIe 3.0 ×2, MIPI DSI with touch, camera interfaces, microSD and sensor buses. USB-C DisplayPort Alternate Mode is allocated to USB1 only. QSPI flash shares signals with CAM0 and GPIO13/14/15/17. Under the listed pin allocation, QSPI flash and CAM0 are mutually exclusive, making peripheral allocation a central hardware/software design decision. Camera and flash requirements must be reconciled with that mapping before a new carrier configuration is fixed.
Software image, recovery and thermal integration
Android and Ubuntu remain the documented adaptation directions; Windows 11 is a pending firmware item, not ready support claimed by this case. Before destructive flashing or a full erase, preserve the module-specific QCN/radio configuration and confirm a matching recovery image and procedure. A full erase without these records can destroy information required for normal cellular operation. A generic operating-system image should not be treated as a complete device backup.
The carrier design also connects high-speed routing and assembly requirements with power and thermal decisions. Its six-layer stack-up, controlled-fan connection and 5–12 V input direction are documented design features. A new carrier scope should include impedance verification for the high-speed layout and power-transient checks, with sustained-load and thermal measurements defined for the intended enclosure.
Documented architecture and configuration
This table records the project’s documented architecture and selection boundaries. Options, variants and design inputs remain qualified as shown; their inclusion here is not an independent guarantee that every option formed part of the delivered configuration.
| Item | Configuration |
|---|---|
| Module / SoC | SG560D / Qualcomm QCM6490 direction |
| Memory variants | 4 / 6 / 8 GB LPDDR4X |
| Storage variants | 64 / 128 / 256 GB UFS |
| High-speed I/O | PCIe 3.0 ×2, MIPI DSI, 2 × CSI |
| USB display | DP Alt Mode on USB1 only |
| Other expansion | I2C/SPI, NFC, dual DMIC, UART, fan |
Delivered implementation and verification boundary
The customer received the agreed QCM6490 platform hardware and software implementation. Physical testing was completed, and the tested functions met the customer’s requirements before delivery. This outcome does not expand the documented software support or establish performance for all module SKUs, radio bands, camera combinations or thermal conditions.
For a similar product, exact module selection, peripheral pin allocation, target image and recovery requirements should be decided together. Market-specific radio configuration and enclosure constraints also need to be defined for that project.
Discuss a similar QCM6490 platform
Send Obeita the intended SG560D module SKU, operating system, camera/display list and deployment country. We can use those details to scope carrier adaptation, software integration and physical testing.