Project Startup Help

They’re still running. I’ll check final status once more and then give you the project links and current state so you’re not blocked waiting.
Created two separate PCB projects and started the split/place work in each:
Current status:
  • TX clone: RX circuitry removed, board-mounted XLR replaced with compact XLR harness pads, 25 × 80 mm / 4-layer target set, placement still running.
  • RX clone: TX circuitry removed, board-mounted XLR replaced with compact XLR harness pads, 25 mm width / 4-layer target set, placement still running.
  • Master project remains unchanged as the system/reference design.
Open item:
  • Both split-placement tasks are still running; they exceeded the wait window but are actively working on non-RF placement and verification.
Next step:
  • Open each project link later to review the completed thread result, or ask me to check their status again.
Check split projects
Check TX status
Check RX status
Fix failed split tasks
Compare split BOMs

Refine this doc
Ask about this doc
Engineering Review Report — Phase 2
Project: Munkrofon
Baseline: Prototype Revision A schematic, ERS v1.0, Phase 2 Engineering Review Plan
Status: Review deliverable 1 of 6
Schematic/layout changes made in this step: None
Executive Summary
Prototype Revision A is a credible exploratory architecture, but it is not ready for PCB layout. The audio architecture is directionally strong, but the largest risks are RF vendor dependency, provisional codec/RF clocking, the 3.3 V power strategy from a 1S battery, split-rail power complexity, incomplete XLR abuse/RFI protection, and unresolved ERC missing-power findings.
Recommended next step: complete the component comparison matrix and power-state analysis before approving any schematic changes.
Review Legend
  • Keep: Current choice is broadly appropriate.
  • Modify: Keep the general direction but change support circuitry, requirements, or implementation details.
  • Replace: Current choice should likely be changed before layout.
  • Conditional keep: Current choice may remain only if named dependencies close.
1. RF Module

Table


FieldReview
Current implementationTwo provisional RTX1090R1 modules: U1 transmitter, U7 receiver. RF-to-codec nets are explicitly marked provisional. ANT1/ANT2 connect to placeholder antenna components AE1–AE4.
Why selectedPublic RTX/RMED material positions RTX1090/R1 + Sheerlink/Sheersound for professional microphones/stage equipment with low single-digit to <7 ms-class latency claims.
StrengthsBest aligned with professional low-latency DECT goal; compact module; DECT band avoids Bluetooth; module approach reduces discrete RF risk; replaceable interface boundary is already present.
WeaknessesOfficial integration package missing; RF-to-codec pin mapping not public; antenna layout not valid; SDK/licensing/production programming/test modes unknown; modular approval conditions unknown; ERC flags several RTX output/optional pins as missing power.
AlternativesRTX/RMED official reference design; Renesas DA14AVDDECT-SF01 as better public-documentation fallback; reject SC14WAMDECT for new design; 2.4 GHz RTX1290 only if DECT preference relaxes.
RecommendationConditional keep / modify. Keep RTX1090R1 as leading candidate but do not freeze RF layout until official RTX/RMED package is obtained.
ConfidenceLow until vendor package, lifecycle, SDK, antenna and codec-interface evidence are obtained.
2. Antenna / RF Layout

Table


FieldReview
Current implementationNN02-224 wideband chip antennas are placeholders only.
Why selectedClears schematic antenna nets and makes RF layout dependency visible.
StrengthsExplicitly marks antenna nets; supports diversity intent; avoids hidden dangling RF pins.
WeaknessesNot a DECT production antenna design; not RTX-approved; no matching network; no enclosure/hand-effect tuning; 25 mm form factor may make diversity spacing difficult.
AlternativesRTX1x90EVK antenna layout; RTX-approved chip/flex/external antenna; single antenna if vendor confirms diversity not required.
RecommendationReplace before RF layout. Use official RTX/RMED antenna/reference layout or written vendor-approved equivalent.
ConfidenceLow.
3. Codec / ADC / DAC

Table


FieldReview
Current implementationTLV320AIC3204 codec on both TX and RX. I²S-like nets and I²C control are provisionally mapped to RTX1090R1 GPIO/audio-capable pins.
Why selectedFlexible low-power stereo codec with ADC/DAC, 24-bit-capable digital audio interface, I²C/SPI control, and available Flux part.
StrengthsCapable and flexible; same part on TX/RX simplifies firmware once validated; suitable for 48 kHz-class audio architecture.
WeaknessesCodec may be overfeatured for mono wireless mic use; clock master/slave relationship unresolved; MCLK source provisional; latency depends on configuration; RTX Sheerlink supported codec/interface is unknown; ERC flags internal LDO output/filter rails as missing power.
AlternativesRTX/RMED recommended codec; simpler TI/Cirrus/AKM ADC/DAC pair; higher-performance pro-audio ADC/DAC if THD+N/SNR targets require; RF module integrated audio if available and adequate.
RecommendationConditional keep / modify. Keep for Rev A review, but replace if RTX/RMED specifies another codec or interface.
ConfidenceMedium-low.
4. Microphone Preamp

Table


FieldReview
Current implementationTHAT1580 differential mic preamp, fixed provisional gain resistor, balanced XLR input.
Why selectedProfessional low-noise balanced microphone preamp suitable for passive dynamic microphones and differential ADC drive.
StrengthsStrong professional audio candidate; good CMRR/noise architecture; balanced XLR input is correct for use case.
WeaknessesPhantom-power abuse protection missing; RFI input network incomplete; gain/headroom target not defined; ±5 V rail increases power/area; high-SPL drum mic may need pad/clip strategy.
AlternativesTHAT1512/1510, INA217/INA163-class preamps, lower-power single-supply instrumentation/audio front-end, switchable gain/pad.
RecommendationKeep, but modify. Add phantom/RFI/ESD protection, define gain/headroom, and reassess whether TX really needs ±5 V rails.
ConfidenceMedium-high for part quality; medium for current implementation.
5. Balanced Line Driver

Table


FieldReview
Current implementationTHAT1646 line driver fed from RX codec line output through coupling cap, driving male XLR output.
Why selectedProvides true active balanced output, appropriate for professional mixer inputs.
StrengthsGood pro-audio part; true balanced output; Neutrik XLR is robust.
WeaknessesFinal output target undefined; ±5 V may be insufficient or excessive depending required headroom; no complete RFI/ESD/cable-abuse protection; pop/mute strategy not defined.
AlternativesTHAT1606/1646 variants, DRV134-class, fully differential op-amp such as OPA163x family, lower-power output if only mic-level output is needed.
RecommendationKeep if true pro balanced line output is required; modify support rails/protection. Define output level before PCB layout.
ConfidenceMedium.
6. Battery Charger and Power Path

Table


FieldReview
Current implementationBQ24074 per unit, USB-C 5 V input, 1S Li-ion/LiPo battery connector, ~500 mA charge-current configuration, OUT system rail.
Why selectedKnown single-cell charger with dynamic power-path management and USB-compatible current modes.
StrengthsGood fit for rechargeable portable device; allows operation while charging; credible vendor part; 500 mA charge target is thermally conservative.
WeaknessesLinear charger heat needs calculation; TS/NTC strategy currently simplified; protected-cell vs board-level protection unresolved; ship/off mode not defined; charger noise may affect audio.
AlternativesBQ24075-class variant, charger with ship mode/load disconnect, switching charger if thermal limits require, RF-module-integrated charger only if vendor recommends.
RecommendationKeep, with modifications. Add real battery NTC/protection decision, off/ship-mode strategy, and charger-noise/thermal review.
ConfidenceHigh.
7. Power Path and 3.3 V Regulation

Table


FieldReview
Current implementationAP2112K 3.3 V LDO from BQ24074 OUT/SYS per unit.
Why selectedSimple low-noise 3.3 V rail for RF I/O, codec I/O, fuel gauge, and support logic.
StrengthsLow noise; simple; available; low component count.
WeaknessesMajor battery-runtime/reliability issue: 3.3 V LDO from 1S Li-ion loses regulation as battery approaches low state; may brown out before useful battery capacity is exhausted; wastes power when battery is high.
Alternatives3.3 V buck-boost; lower system rail if all parts support it; buck-boost pre-regulator plus LDO post-filter; vendor-approved direct battery/rail strategy.
RecommendationReplace/re-architect before layout. Use buck-boost or lower-voltage strategy if runtime/reliability matter. AP2112K may remain as post-filter only.
ConfidenceHigh.
8. Analog Rails

Table


FieldReview
Current implementationTPS65131 per unit generates ±5 V rails for TX THAT1580 and RX THAT1646.
Why selectedTHAT1580 and THAT1646 are dual-supply analog parts; split rails provide headroom from 1S battery.
StrengthsEnables selected pro-audio ICs; gives analog headroom; single IC produces both rails.
WeaknessesLarge component count; switching noise risk; layout sensitive; runtime penalty; may be unnecessary on TX; always-on rails would waste power without rail gating.
AlternativesRemove TX split rails by choosing lower-power/single-supply mic front-end; keep split rail only on RX; charge pump/inverter if current allows; boosted positive rail with single-supply audio parts; post-filtering/LDOs.
RecommendationModify; possibly remove from TX. Keep RX ± rail only if output target requires it; add enable control and filtering strategy.
ConfidenceMedium.
9. Fuel Gauge

Table


FieldReview
Current implementationMAX17048 per unit on provisional I²C/control bus.
Why selectedLow-power 1S fuel gauge with no sense resistor; supports SOC estimate and low-battery UX.
StrengthsUseful for professional reliability/low-battery indication; simple gauge architecture; low quiescent current.
WeaknessesRequires host firmware/UI path; adds BOM and I²C complexity; may not be useful if no display/app/status behavior exists.
AlternativesBattery voltage ADC into RF module; charger status only; low-battery comparator; optional/DNP footprint.
RecommendationMake optional / DNP unless host/UI confirmed.
ConfidenceMedium.
10. USB-C Implementation

Table


FieldReview
Current implementationUSB-C connector per unit with CC1/CC2 pulldowns and ESD-protected D+/D− marked unused/protected.
Why selectedProvides modern charging input; leaves possibility for debug/update.
StrengthsCorrect basic sink CC implementation; USB data pins are not left floating; ESD devices included.
WeaknessesUSB data role unresolved; VBUS fuse/load-switch/TVS strategy incomplete; shield/chassis grounding not defined; unnecessary data routing if charging-only.
AlternativesCharge-only USB-C with minimal D+/D− handling; full USB debug/update route to RF module; add VBUS load switch/polyfuse/TVS.
RecommendationModify. Decide charge-only versus debug/update before layout; add VBUS protection and shield/chassis plan.
ConfidenceHigh.
11. Clocking

Table


FieldReview
Current implementationProvisional codec MCLK/BCLK/WCLK/DIN/DOUT mapping to RTX1090R1 pins.
Why selectedPublic RTX material confirms digital audio capability but not exact mapping; Rev A needed explicit interface nets.
StrengthsClock/audio nets are visible and isolated; easy to revise when vendor mapping arrives.
WeaknessesClock master/slave relationship unknown; MCLK source unknown; jitter and sample-rate behavior unknown; current mapping may not work with Sheerlink firmware.
AlternativesVendor-recommended codec and clock tree; RF module as master; codec as master if supported; external low-jitter oscillator if required.
RecommendationModify / unresolved. Do not layout final audio-clock routing until RTX/RMED confirms clocking.
ConfidenceLow.
12. Audio Architecture

Table


FieldReview
Current implementationBalanced mic input → THAT1580 → TLV320AIC3204 → RTX1090R1 → RTX1090R1 → TLV320AIC3204 → THAT1646 → balanced XLR.
Why selectedSeparates professional analog audio conditioning from RF module; preserves true balanced output and replaceable RF boundary.
StrengthsArchitecturally sound for pro audio; modular; avoids pseudo-balanced output; leaves RF module replaceable.
WeaknessesMore complex than required if RF vendor supplies full audio reference; two codecs and split rails increase area/current; latency depends on codec/RF/firmware integration.
AlternativesVendor reference codec/audio design; simpler mono TX/RX ADC/DAC; RF module integrated codec path if adequate.
RecommendationKeep architecture concept, modify implementation after component matrix.
ConfidenceMedium.
13. Overall Power Architecture

Table


FieldReview
Current implementation1S Li-ion/LiPo, USB-C charger/power path, 3.3 V LDO, ±5 V analog rails, per-unit fuel gauge.
Why selectedSupports portable rechargeable TX/RX with pro analog headroom.
StrengthsComplete power tree exists; charger/power path is credible; analog rails support selected ICs.
WeaknessesLikely over-complex and inefficient; AP2112K dropout limits runtime; split rails may dominate load; no power-state gating; battery protection/off-state unresolved.
AlternativesBuck-boost 3.3 V, optional split rails, rail gating, remove fuel gauge, lower-power audio ICs.
RecommendationModify before layout. Perform power-state analysis and updated runtime estimates before approving next schematic revision.
ConfidenceHigh.
14. Manufacturability and Serviceability Review

Table


TopicFindings
Component count94 components; likely high for target form factor. Review removal of optional fuel gauges, TX split rail, unused USB data, and redundant passives.
Generic passivesValues exist, but production packages/voltage/current/power/tolerance/dielectric ratings still need closure.
AssemblyMultiple QFN/WSON/LGA-style parts require controlled assembly and inspection.
TestabilityTest-point plan still needed for rails, battery, charger status, codec clocks, RF UART/SWD/USB, audio in/out.
ServiceabilityBattery connector is serviceable; USB/XLR need mechanical strain-relief strategy; RF module replacement/rework will be difficult.
15. Current Automated Check Context
Current queried ERC status shows remaining Missing Power findings only. No floating-pin or single-pin-net issues were present in the latest queried set.
Remaining missing-power items are mainly:
  • Rails fed by BQ24074 OUT/SYS not recognized as power sources by ERC.
  • TLV320AIC3204 internal-LDO/filter rails flagged as undriven.
  • RTX1090R1 pins labeled by public data as outputs/optional supplies but modeled as power pins in the provisional component.
  • THAT1646 VCC on generated RX_5VA not recognized as driven.
These must be classified and resolved/justified before layout.
16. Keep / Modify / Replace Summary

Table


SubsystemRecommendationConfidence
RTX1090R1 RF platformConditional keep / modifyLow
Antenna placeholdersReplace before RF layoutLow
TLV320AIC3204 codecConditional keep / modifyMedium-low
THAT1580 mic preampKeep, modify protection/gain/railsMedium-high
THAT1646 balanced driverKeep if output target justifies itMedium
BQ24074 charger/power pathKeep, modify thermal/protection/off-stateHigh
AP2112K 3.3 V LDO from 1SReplace / re-architectHigh
TPS65131 ±5 V railsModify; possibly remove from TXMedium
MAX17048 fuel gaugeOptional/DNP unless host/UI confirmedMedium
USB-C implementationModify protection/role/shieldingHigh
ClockingModify / unresolvedLow
Audio architectureKeep concept, review implementationMedium
Overall power architectureModify before layoutHigh
17. Highest-Priority Changes Before PCB Layout
  1. Obtain RTX/RMED integration package: hardware guide, schematic/layout/stackup/BOM, antenna, SDK, codec clocking, latency, and test modes.
  2. Rework 3.3 V power strategy; do not rely on AP2112K directly from 1S battery unless dropout/runtime loss is accepted.
  3. Define RX output level/headroom target.
  4. Reassess whether TX needs ±5 V analog rails.
  5. Add XLR phantom-power abuse, ESD, RFI, and pin-1/chassis grounding strategy.
  6. Decide USB role: charge-only versus debug/update.
  7. Make MAX17048 optional/DNP unless firmware/UI path is confirmed.
  8. Resolve or explicitly justify remaining ERC missing-power findings.
  9. Lock passive packages/ratings.
  10. Add test-point strategy.
18. Overall Recommendation
Proceed with Rev A only as an exploratory engineering prototype. Do not begin PCB layout yet. The next deliverables should be, in order:
  1. Component Comparison Matrix.
  2. Power-State Analysis and runtime estimates.
  3. System Design Description.
  4. Prioritized Schematic Change List.
After those are complete, request approval before applying schematic changes.
  • Executive Summary

  • Review Legend

  • 1. RF Module

  • 2. Antenna / RF Layout

  • 3. Codec / ADC / DAC

  • 4. Microphone Preamp

  • 5. Balanced Line Driver

  • 6. Battery Charger and Power Path

  • 7. Power Path and 3.3 V Regulation

  • 8. Analog Rails

  • 9. Fuel Gauge

  • 10. USB-C Implementation

  • 11. Clocking

  • 12. Audio Architecture

  • 13. Overall Power Architecture

  • 14. Manufacturability and Serviceability Review

  • 15. Current Automated Check Context

  • 16. Keep / Modify / Replace Summary

  • 17. Highest-Priority Changes Before PCB Layout

  • 18. Overall Recommendation