Choose a RobustOS device and SDK platform that can run your application. This guide lists each product’s CPU platform and the Flash and RAM available to SDK applications, so you can match the device to your processing, storage and memory requirements.
Applies to: RobustOS SDK application development for the models listed below. Select the SDK and firmware for your exact device model and hardware variant. The tables do not cover RobustOS Pro, eSIM, Global or 5G RedCap variants.
An application package is built for a specific SDK hardware target. Packages built for different CPU platforms are not interchangeable. When moving an application to a different platform, use its matching SDK and build target to compile and package the application again. Adapt hardware interfaces or libraries as needed, then test the new package on the target device.
For example, R3000 uses the r3000 target and R5010 uses the r5010a target. Build a separate application package for each target. Two models using the same CPU architecture do not automatically share an SDK target.
| Field | How to use it |
|---|---|
| CPU platform and architecture | Identify the processor family and instruction-set architecture. Use the exact SDK target and toolchain for the device. ARM or MIPS alone is not a build-target name or a promise of binary compatibility. |
| Clock and core count | Help shortlist a processing platform. Compare actual application latency and throughput: clock rates across different architectures are not directly comparable, and multiple cores help only when the software can use them. |
| Device Flash and RAM | Describe the device profile's overall storage and memory. They are not all available to your application. |
| SDK Flash and RAM | Resources reserved for SDK applications, expressed as limits. Include the executable, required libraries, persistent data and working memory in your sizing. These values are not a measurement of current free space or memory. |
Follow the model links for product information. SDK resource allocations depend on the device model and firmware.
Compare total device capacity with the limits reserved for SDK applications. Include installed applications, dependencies, configuration and retained data in the Flash budget, and peak working memory and concurrent activity in the RAM budget.
| Model | CPU platform / clock | Device capacity | SDK resource limits |
|---|---|---|---|
| M1200 | Nuvoton NUC976DK63YC; ARM926EJ-S / ARM Single-core, 300 MHz | Flash: 16 MB RAM: 64 MB | Flash: 3 MB RAM: 16 MB |
| R1510 | Qualcomm QCA9531; MIPS 24KEc / MIPS Single-core, 650 MHz | Flash: 16 MB RAM: 128 MB | Flash: 4 MB RAM: 64 MB |
| R1510-Lite | Qualcomm QCA9531; MIPS 24KEc / MIPS Single-core, 650 MHz | Flash: 16 MB RAM: 128 MB | Flash: 4 MB RAM: 64 MB |
| R1511 | Qualcomm QCA9531; MIPS 24KEc / MIPS Single-core, 650 MHz | Flash: 16 MB RAM: 128 MB | Flash: 4 MB RAM: 64 MB |
| R1511P | Qualcomm QCA9531; MIPS 24KEc / MIPS Single-core, 650 MHz | Flash: 16 MB RAM: 128 MB | Flash: 4 MB RAM: 64 MB |
| R1520 | Qualcomm QCA9531; MIPS 24KEc / MIPS Single-core, 650 MHz | Flash: 16 MB RAM: 128 MB | Flash: 4 MB RAM: 64 MB |
| R2010 | Qualcomm QCA9531; MIPS 24KEc / MIPS Single-core, 650 MHz | Flash: 32 MB RAM: 128 MB | Flash: 16 MB RAM: 64 MB |
| R2011 | Qualcomm QCA9531; MIPS 24KEc / MIPS Single-core, 650 MHz | Flash: 32 MB RAM: 128 MB | Flash: 16 MB RAM: 64 MB |
| R2110-4L | MediaTek MT7621AT; MIPS 1004Kc / MIPS Dual-core, 880 MHz | Flash: 32 MB RAM: 512 MB | Flash: 16 MB RAM: 64 MB |
| R2120 | MediaTek MT7621AT; MIPS 1004Kc / MIPS Dual-core, 880 MHz | Flash: 32 MB RAM: 512 MB | Flash: 5 MB RAM: 256 MB |
| R3000 | Microchip AT91SAM9X25; ARM926EJ-S / ARM Single-core, 400 MHz | Flash: 256 MB RAM: 128 MB | Flash: 64 MB RAM: 64 MB |
| R3000 Lite | Microchip AT91SAM9X25; ARM926EJ-S / ARM Single-core, 400 MHz | Flash: 256 MB RAM: 128 MB | Flash: 64 MB RAM: 64 MB |
| R3000-Quad | Microchip AT91SAM9X25; ARM926EJ-S / ARM Single-core, 400 MHz | Flash: 256 MB RAM: 128 MB | Flash: 64 MB RAM: 64 MB |
| R5010 | CPU built into RG520NEBDC module Not listed | Flash: 110 MB (module internal Flash) RAM: 192 MB (module internal SRAM) | Flash: 10 MB RAM: 45 MB |
| R5020 | MediaTek MT7621AT; MIPS 1004Kc / MIPS Dual-core, 880 MHz | Flash: 32 MB RAM: 512 MB | Flash: 5 MB RAM: 256 MB |
| R5020-Lite | MediaTek MT7621AT; MIPS 1004Kc / MIPS Dual-core, 880 MHz | Flash: 32 MB RAM: 256 MB | Flash: 5 MB RAM: 128 MB |
| R5030 | Qualcomm IPQ5018 / ARM Cortex-A53 Dual-core, 1.0 GHz | Flash: 8 GB eMMC RAM: 512 MB | Flash: 6.5 GB RAM: 128 MB |
Not listed means the information is not specified here. Device totals include resources used by the operating system and services. SDK resources are shared by applications and services; check available storage and memory on the configured device. For an SDK resource allocation not listed, contact Robustel Support.
SoC means system-on-chip. Test compute-intensive applications with the network services and other applications required by your deployment.
For example, an application needing 20 MB of installed Flash exceeds a 4–5 MB SDK Flash allocation. The R3000 models listed here provide 64 MB, and R5030 provides 6.5 GB. Compare CPU, RAM and interfaces as well as storage before selecting a model.
An application needing 100 MB of peak RAM exceeds the 64 MB SDK profiles. R5020-Lite and R5030 have 128 MB of SDK RAM; R5020 and R2120 have 256 MB. Consider the remaining headroom and other applications before selecting one. More Flash does not imply more SDK RAM: R5030 has much more application storage than R5020, while R5020 has the larger listed SDK RAM budget.
Use the SDK archive, build target and firmware for your exact device model and hardware variant. CPU architecture alone does not identify the SDK build target.