IoT Fire Alarm Device Design


You should ask Quectel / supplier for the EC25MXGA hardware design package, not just the marketing datasheet.
Ask for:
  1. EC25MXGA Hardware Design Guide
    • Full pin descriptions
    • Power supply requirements
    • PWRKEY / RESET timing
    • UART / USB / SIM / RF reference circuits
    • VDD_SDIO usage guidance
  2. Recommended PCB land pattern / footprint
    • Pad dimensions
    • Pad numbering
    • Paste mask / solder mask recommendations
    • Keepout zones under/around the module
    • Assembly notes
  3. Reference schematic
    • VBAT_RF / VBAT_BB decoupling
    • SIM socket wiring
    • Antenna matching / ESD
    • Status pins
    • Power-on/off sequence
  4. RF layout guidelines
    • 50 Ω antenna routing
    • Ground stitching via recommendations
    • Antenna connector/matching network placement
    • Diversity/GNSS pins if used or unused
  5. Certification documents
    • RCM / ACMA / AS/CA S042 relevance
    • Carrier approval info for Australia
    • LTE band support for AU carriers
    • Test reports if available
  6. Lifecycle / supply confirmation
    • Active production status
    • Recommended replacement if EC25MXGA is not preferred
    • Minimum order / lead time
Short message you can send:
We are designing a dual-modem Australian fire alarm signalling device using 2 × EC25MXGA. Please provide the EC25MXGA hardware design guide, recommended PCB land pattern/footprint, reference schematic, RF layout guide, SIM interface recommendations, VDD_SDIO connection guidance, Australian carrier/certification documentation, and lifecycle/supply status.
Ok I’ll contact them
Good plan. Ask them specifically for the hardware design guide + recommended PCB land pattern for EC25MXGA-128-SNNS.
Until we get that, the safest path is:
  • Keep EC25MXGA in the design.
  • Do not send the PCB to manufacture yet.
  • Continue with placement/routing cleanup only as a draft.
  • Finalize modem footprint, SIM wiring, RF layout, and VDD_SDIO treatment once Quectel confirms the official guidance.
Clean draft layout
Review EC25 wiring
Check power budget
Update factory checklist
Run current checks

Remaining Schematic Cleanup Tasks
Current Baseline
The schematic now contains the major required blocks for the ASE IoT device:
  • Protected 12–24 VDC input and regulated rails.
  • STM32H757 MCU core.
  • USB-C programming/service port and SWD debug.
  • 2 × EC25MXGA cellular modules.
  • 2 × SIM card slots, one SIM per modem.
  • 2 × external antenna/u.FL pigtail RF outputs.
  • 8 × supervised sealed-resistor-pack FAS inputs.
  • 1 × dedicated power-fail input.
  • 3 × programmable relay outputs.
  • Basic SPI LCD connector and four front-panel buttons.
  • Dallas/iButton isolate key interface.
  • RTC and SPI FRAM event memory.
Locked Practical Assumptions
  • LCD: basic SPI LCD module is acceptable for this revision; final connector pinout must match the selected LCD before manufacture.
  • Cellular: EC25MXGA-128-SNNS is the working module for both modem positions.
  • SIM: dual SIM card slots are required and remain part of the layout/routing constraints.
  • Inputs: sealed resistor-pack/EOL ladder is a product-specific design; first-pass values are documented separately and must be bench-validated against ADC tolerance and cable noise.
  • PCB: initial board target is 100 mm × 160 mm, 4-layer stackup.
  • MCU: STM32H757IIT6 LQFP-176 is now the selected processor package for manufacturability.
STM32 Package / DSI Fix Status
The original STM32H757ZIY6TR WLCSP part was removed because its footprint/library pad overrides caused impossible pad overlap and routing blockage around pins including PA9/PC9/PE2.
The processor is now STM32H757IIT6 in LQFP-176. This package is more practical for this board because it is easier to route, inspect, assemble, and rework than the WLCSP package.
U5 VDD12DSI has been fixed for unused DSI:
  • DSI is not used in this design.
  • VDD12DSI is tied to the local DSI regulator/capacitor node as required for the STM32 DSI supply domain handling.
  • Local 2.2 uF capacitance to GND has been added on the DSI 1.2 V node.
  • DSI signal pins remain unused/no-connect.
EC25 VDD_SDIO ERC Status
The EC25MXGA library symbol currently defines VDD_SDIO as a required power-input pin. In this project SDIO is unused, and VDD_SDIO should not be tied to 3.3 V just to silence ERC unless the Quectel hardware design guide explicitly requires that connection for the selected interface mode.
Actions attempted:
  • Marked U6:VDD_SDIO and U7:VDD_SDIO as no-connect using short pin names.
  • Re-applied no-connect using the exact symbol terminal identifiers U6:VDD_SDIO::34 and U7:VDD_SDIO::34.
  • Reran focused ERC for VDD_SDIO.
Result: the missing-power ERC still reports U6/U7 VDD_SDIO because the library pin is typed as a mandatory power input; the ERC engine does not suppress this specific power-pin rule with a project-level NC annotation.
Required final fix: edit/fork the EC25MXGA component library entry so pin 34 VDD_SDIO is typed as Power Out, Passive, or NC-compatible for this project. Do not electrically drive VDD_SDIO from a board rail unless verified against the EC25 hardware design guide.
Latest Routing / Check Status
Previous routing/check status before the STM32 package replacement and DSI fix:
  • 69 airwire errors remained.
  • 7 overlapping-copper errors remained.
  • 2 dangling-trace warnings remained.
  • 2 EC25 VDD_SDIO missing-power ERC errors remained.
The WLCSP footprint blocker has been corrected by switching to the LQFP-176 MCU, but PCB placement and routing still need to be cleaned up around the larger processor package.
Cleanup Tasks Before Factory Release
  1. Finish MCU placement/routing cleanup — highest priority
    • Re-place MCU decoupling/support parts tightly around the new STM32H757IIT6 LQFP-176.
    • Remove stale routing from the previous WLCSP placement if it causes overlaps or dangling traces.
    • Re-route MCU escape, USB, SPI, ADC inputs, buttons, LCD, FRAM, RTC, and modem UART/control nets.
    • Re-run DRC before manufacturing export.
  2. Resolve EC25 VDD_SDIO ERC at library/component level
    • Preferred: edit/fork the EC25MXGA component so VDD_SDIO pin 34 is typed as Power Out, Passive, or NC-compatible.
    • Do not tie VDD_SDIO to 3.3 V just to silence ERC unless the EC25 hardware design guide explicitly requires it for the selected interface mode.
  3. Power front end
    • Calculate final LTC4368 UV/OV threshold resistor values.
    • Verify back-to-back MOSFET orientation against the LTC4368 reference design.
    • Confirm fuse/eFuse rating and TVS surge energy rating for the intended fire-panel supply environment.
  4. Regulators and modem rails
    • Finalize 4.0 V modem buck feedback values and compensation/bootstrap/soft-start values.
    • Confirm each modem rail can support simultaneous cellular TX current peaks.
    • Add current/fault telemetry if required by compliance testing.
  5. EC25MXGA modem interface
    • Confirm VBAT, VDD_EXT, PWRKEY, RESET_N, STATUS, RI, UART, SIM, and RF pin usage against the EC25 hardware design guide.
    • Verify SIM ESD capacitance is suitable for SIM clock/data lines.
    • Confirm RF ESD part and footprint are acceptable for cellular antenna routing.
  6. SIM card slots
    • Verify pinout of both SIM sockets against the selected physical socket datasheet.
    • Place SIM sockets near accessible enclosure/service area.
    • Route SIM lines short, protected, and away from noisy buck/RF switching areas.
  7. LCD and front panel
    • Select final SPI LCD module or connector pinout.
    • Verify backlight current and driver method.
    • Confirm button placement matches front-panel mechanical design.
  8. Inputs and power-fail input
    • Bench-calculate and simulate ADC thresholds using STM32 ADC reference tolerance and resistor tolerances.
    • Choose final resistor-pack values and tolerance grade.
    • Add input surge/ESD/EMI filtering appropriate for field wiring.
  9. Relays
    • Confirm relay contact rating and terminal block rating for intended programmable outputs.
    • Add contact terminal labels and isolation/clearance notes.
  10. MCU support
  • Audit STM32H757 power pins, VCAP, decoupling, boot mode, reset, clocks, and unused pins.
  • Decide whether an external HSE crystal/oscillator is required for modem/USB timing robustness.
  1. PCB layout and routing
  • Keep RF paths 50 Ω and short from modem RF pins to u.FL connectors.
  • Keep SIM slots with their matching modems.
  • Spread MCU, modem, SIM, RF, and regulator sections to remove current routing congestion.
  • Finish all remaining airwires after placement cleanup.
  • Clear overlapping copper and dangling traces.
  • Run full DRC/ERC/airwire checks after final routing.
  1. Manufacturing package
  • Generate and review Gerbers, drill files, BOM, pick-and-place, assembly notes, and test checklist only after ERC/DRC are clean.
  • Current Baseline

  • Locked Practical Assumptions

  • STM32 Package / DSI Fix Status

  • EC25 VDD_SDIO ERC Status

  • Latest Routing / Check Status

  • Cleanup Tasks Before Factory Release