Embedded AI Processor Recommendation
Thought for 2 mins 52 sec
The schematic PDF is readable and shows several important differences from the current Flux design, including added DW01A/FS8205A battery protection and an AT2659 RF stage. The STEP file did not load in the first inspection, so I’m retrying the mechanical review separately while verifying the current Flux layout and stack-up.
Thought for 5 sec
Review started but is blocked because no ACUs are currently available.
Completed:
- Inspected the schematic PDF and extracted its major circuits, components, and nets.
- Flagged preliminary concerns: limited USB protection, charging-only USB implementation, power-tree/current-capacity validation, RF-layout dependence, and incorrect
U10inductor designator. - Confirmed the PDF includes DW01A/FS8205A battery protection and AT2659 RF circuitry not reflected in the current Flux BOM.
Remaining:
- Inspect the STEP model and physical placement.
- Verify the current Flux schematic, footprints, stack-up, keepouts, and DRC state.
- Complete power, signal, RF, thermal, and manufacturability analysis.
- Generate the production-readiness review report and rating.
No project changes were made.
Retry full review
List mismatches
Inspect STEP placement
Check missing circuits
Refine this doc
Ask about this doc
Power Tree and Current Budget
Status: planning estimate. Values must be refined after final LCD, LED ring, Radxa workload, battery pack, and charger settings are selected. The 6–8 hour runtime target is aspirational unless measured power supports it; prioritize reliable operation and accurate power-budget reporting over forcing runtime assumptions.
Proposed Power Architecture
Diagram
Rail Budget
Table
| Rail | Load | Typical Estimate | Peak / Design Estimate | Notes |
|---|---|---|---|---|
| 5 V | Radxa Zero 3W | 500-900 mA | 2.0 A transient target | AI, Wi-Fi, USB, CPU/NPU load can create bursts. Validate with real workload. |
| 5 V or LED rail | High-CRI LED ring | 200-500 mA assumed | 800 mA planning limit | Must be finalized from LED count/current and optical target. |
| 3.3 V | TFT logic/touch | 20-60 mA | 100 mA | Backlight not included unless module uses 3.3 V backlight. |
| 3.3 V | GPS ATGM336H | 25-50 mA | 100 mA | Add margin for active antenna if powered. |
| 3.3 V | AS7341 breakout | <10 mA | 25 mA | Excludes illumination LEDs. |
| 3.3 V | MAX17048 + buttons/status | <5 mA | 20 mA | Fuel gauge may be always-on. |
| 3.3 V | Expansion/debug | 0 mA base | 100-300 mA reserved | Limit via header label/fuse if needed. |
System-Level Estimate
Table
| Scenario | 5 V Load Equivalent | Battery Input Current at 3.7 V, 85% Boost Efficiency | Notes |
|---|---|---|---|
| Idle / display dim / GPS on | 3-4 W | 0.95-1.27 A | Radxa idle dominates. |
| Active measurement, LED moderate | 5-7 W | 1.6-2.2 A | Typical field measurement target. |
| AI + Wi-Fi + bright LCD + LED high | 9-12 W | 2.9-3.8 A | Design thermal and connector paths for this. |
| Worst-case 5 V at 2.5 A | 12.5 W | 4.0 A at 3.7 V; ~4.9 A at 3.0 V | This is the critical TPS61088/battery path sizing case. |
Battery Runtime Assumptions
Battery energy:
- 4000 mAh 1S LiPo: ~14.8 Wh nominal
- 6000 mAh 1S LiPo: ~22.2 Wh nominal
- Usable energy after converter losses and cutoff: assume 75-85% of nominal until validated
Approximate runtime:
Table
| Average System Power | 4000 mAh Pack | 6000 mAh Pack | Use Case |
|---|---|---|---|
| 3 W | 3.7-4.2 h | 5.5-6.3 h | standby/low-brightness logging |
| 5 W | 2.2-2.5 h | 3.3-3.8 h | moderate active use |
| 7 W | 1.6-1.8 h | 2.4-2.7 h | frequent measurements |
| 10 W | 1.1-1.25 h | 1.7-1.9 h | high brightness + AI/Wi-Fi |
Runtime Policy
- A 6–8 hour runtime is an aspirational target, not a fixed electrical requirement for Rev A.
- Do not undersize regulators, battery-current paths, connectors, or thermal copper to make runtime estimates look better.
- Report runtime honestly from measured current and realistic duty cycles.
- Prioritize reliable boot, AI inference, measurement accuracy, charging safety, and thermal stability over an unverified long-runtime claim.
- Use load switches, backlight dimming, LED duty-cycle control, Wi-Fi power management, and firmware sleep modes to improve runtime after base reliability is proven.
Regulator Sizing Notes
TPS61088 5 V Boost
- Keep as a strong candidate only if implemented with the datasheet-recommended inductor, MOSFET/current settings, thermal copper, and low-ESR input/output capacitors.
- Design target: at least 5 V / 2.5 A peak, preferably 3 A short peak margin if thermals allow.
- Worst case near low battery is severe: 5 V at 2.5 A can pull nearly 5 A from a 3.0 V cell after efficiency losses.
- Battery connector, protection IC, charger/power-path, boost inductor saturation, input capacitors, and copper width must all support this pulse current.
MP2667 Charger / Power Path
- Must be verified for the selected charge current, system load sharing, battery supplement behavior, thermal limits, input current limit, and USB-C 5 V-only sink behavior.
- If the MP2667 cannot support simultaneous high system load and charging without thermal throttling or battery droop, consider a higher-current power-path charger or reduce charge current during operation.
- Charger STAT/PG pins should be routed to LEDs/GPIO if available.
LMR33630 3.3 V Regulator
- A 3 A-capable buck is more than enough for listed 3.3 V peripherals, but it provides expansion margin.
- If it is fed from 5 V boost, total system efficiency is boost-then-buck. If fed directly from battery/system node, check input range/dropout behavior.
- Keep switching node compact and away from AS7341/GPS antenna.
Recommended Power Improvements
- Add load switches for GPS, LCD backlight, AS7341/optical head, and LED ring enable so firmware can reduce standby power.
- Add current measurement option on LED rail or 5 V rail for calibration/debug, either a shunt footprint or test pads.
- Add test points for USB_5V, BAT, SYSBAT, 5V, 3V3, CHG_STAT, PGOOD, LED rail, and shutdown signals.
- Consider using the Radxa eMMC variant so the SPI bus is not required for OS storage.
- Keep USB-C charging as 5 V sink for rev A unless a clear need for USB PD appears.
Proposed Power Architecture
Rail Budget
System-Level Estimate
Battery Runtime Assumptions
Runtime Policy
Regulator Sizing Notes
TPS61088 5 V Boost
MP2667 Charger / Power Path
LMR33630 3.3 V Regulator
Recommended Power Improvements
