Skip to main content

Omega4 Hardware Design Guide

This guide provides electrical and layout recommendations for integrating the Omega4 (OM-O4) module into a custom carrier board.

Download design libraries​

Download the package library files for your CAD tool:

2. System Block Diagram​

System block diagram

3. Pin Definition​

3.1 Pin Assignment​

The table below lists the Omega4 module pins and their common alternate functions. In the I/O column, I indicates input, O indicates output, and I/O indicates bidirectional.

Signal levels

All MIPI-related pins on Omega4 use 1.8 V logic. Add level shifting if you need to interface to 3.3 V peripherals.

Omega4 Pin Order

Left (Pins 1-21)​

NoPin NameI/ODescription
1CAM_CLK0_OUT/I2C0_SCL_M2/UART2_TX_M2/GPIO1_B5_dI/OMIPI_MCLK (1.8 V)
2GNDIGND
3GNDIGND
4NCNC
5VCC_1V8OVCC_1V8, 1.8 V output (max 100 mA)
6GNDIGND
7SDMMC0_DET/GPIO1_A6_uI/OSDMMC_DET
8SDMMC0_D1/UART1_RX_M1/PWM2_CH1_M0/GPIO1_A7_dI/OSDMMC_D1
9SDMMC0_D0/UART1_TX_M1/PWM2_CH0_M0/GPIO1_B0_dI/OSDMMC_D0
10SDMMC0_CMD/UART1_CTSN_M1/GPIO1_B2_dI/OSDMMC_CMD
11SDMMC0_CLK/UART1_RTSN_M1/GPIO1_B1_dI/OSDMMC_CLK
12SDMMC0_D3/UART0_RX_M2/JTAG_TMS_M2/PWM2_CH3_M0/I2C0_SDA_M1/GPIO1_B3_dI/OSDMMC_D3
13SDMMC0_D2/UART0_TX_M2/JTAG_TCK_M2/PWM2_CH2_M0/I2C0_SCL_M1/GPIO1_B4_dI/OSDMMC_D2
14GNDIGND
15USB_DMI/OUSB_DM
16USB_DPI/OUSB_DP
17GNDIGND
18ACODEC_AVSSIACODEC_AVSS
19ACODEC_LINEOUTOLINE_OUT
20GNDIGND
21GNDIGND

Bottom (Pins 22-56)​

NoPin NameI/ODescription
22GNDIGND
235 V inputI5 V main power input
245 V inputI5 V main power input
25GNDIGND
26VCC_3V3OVCC_3V3, 3.3 V output (max 100 mA)
27NC/NC
28VCC_RTCIVCC_RTC, input power < 3.63 V
29FSPI_D0IFSPI_D0, boot key
30GNDIGND
31ACODEC_MIC_NIAUD_MICIN
32ACODEC_MIC_PIAUD_MICIP
33ACODEC_MICBIASACODEC_MICBIAS
34GNDIGND
35PWM0_CH0_M0/CPU_AVS/GPIO0_A1_dI/OGPIO0_A1_d
36RTC_32K_CLKO/CLK_32K/CLK_24M_OUT/GPIO0_A0_zI/OGPIO0_A0_z
37PWM0_CH3_M0/GPIO0_A2_dI/OPWM0_CH3_M0/GPIO0_A2_d
38PWR_CTRL_M1/GPIO0_A4_dI/OPWR_CTRL_M1/GPIO0_A4_d
39UART0_TX_M0/PWM0_CH1_M0/I2C0_SCL_M0/JTAG_TCK_M0/GPIO0_A5_dI/OSOC UART0_TX_M0 Debug
40UART0_RX_M0/PWM0_CH2_M0/I2C0_SDA_M0/JTAG_TMS_M0/GPIO0_A6_uI/OSOC UART0_RX_M0 Debug
41UART2_RTSN_M1/SPI0_CS0n_M0/PWM2_CH2_M1/I2C3_SDA_M1/SAI_SDO/GPIO2_B2_dI/OUART2_RTSN_M1
42UART2_CTSN_M1/SPI0_MISO_M0/PWM2_CH3_M1/I2C3_SCL_M1/GPIO2_B3_dI/OUART2_CTSN_M1
43UART2_RX_M1/SPI0_MOSI_M0/PWM1_CH3_M1/I2C4_SDA_M0/SAI_LRCK/PRELIGHT_TRIG/GPIO2_B1_dI/OUART2_RX_M1
44UART2_TX_M1/SPI0_CLK_M0/PWM0_CH3_M1/I2C4_SCL_M0/SAI_MCLK/FLASH_TRIG/GPIO2_B0_dI/OUART2_TX_M1
45BT_UART_RX GPIOA4I/OWiFi pin, BT_UART_RX GPIOA4
46BT_UART_TX GPIOA5I/OWiFi pin, BT_UART_TX GPIOA5
47BT_UART_CTS GPIOA6I/OWiFi pin, BT_UART_CTS GPIOA6
48BT_UART_RTS GPIOA7I/OWiFi pin, BT_UART_RTS GPIOA7
49WIFI GPIOA8_UART_RXI/OWiFi pin, Debug_UART_RX
50WIFI GPIOA9_UART_TXI/OWiFi pin, Debug_UART_TX
51HST_WAK_WF GPIOB0I/OWiFi pin, HST_WAK_WF GPIOB0
52WF_WAK_HST GPIOB1I/OWiFi pin, WF_WAK_HST GPIOB1
53WIFI GPIOA3 PCM_DOUTOWiFi pin, GPIOA3 PCM_DOUT
54WIFI GPIOA1 PCM_CLKOWiFi pin, GPIOA1 PCM_CLK
55WIFI GPIOA0 PCM_FSYNCOWiFi pin, GPIOA0 PCM_FSYNC
56WIFI GPIOA2 PCM_DINIWiFi pin, GPIOA2 PCM_DIN

Top (Pins 57-91)​

NoPin NameI/ODescription
57GNDIGND
58WIFI&BT 2.4G&5G ANT/WiFi/BT 2.4/5 GHz antenna
59GNDIGND
60NC/NC
61UART1_RX_M2/SPI0_CS1n_M0/PWM2_CH1_M1/I2C2_SDA_M1/SAI_SCLK/ETH_LED_SPD/GPIO2_A7_dI/OGPIO2_A7_d
62UART1_TX_M2/PWM2_CH0_M1/I2C2_SCL_M1/SAI_SDI/ETH_LED_LINK/GPIO2_A6_dI/OGPIO2_A6_d
63SARADC_IN0/GPIO2_B4_zI/OSARADC_IN0/GPIO2_B4_z
64GNDIGND
65FEPHY_TXPOFEPHY_TXP
66FEPHY_TXNOFEPHY_TXN
67GNDIGND
68FEPHY_RXPIFEPHY_RXP
69FEPHY_RXNIFEPHY_RXN
70GNDIGND
71MIPI_CSI_D3N/GPI1_C1_uI/OMIPI_D3N (1.8 V)
72MIPI_CSI_D3P/GPI1_C2_uI/OMIPI_D3P (1.8 V)
73GNDIGND
74MIPI_CSI_CK1N/GPI1_C3_uI/OMIPI_CLK1N (1.8 V)
75MIPI_CSI_CK1P/GPI1_C4_uI/OMIPI_CLK1P (1.8 V)
76GNDIGND
77MIPI_CSI_D2N/GPI1_C5_uI/OMIPI_D2N (1.8 V)
78MIPI_CSI_D2P/GPI1_C6_uI/OMIPI_D2P (1.8 V)
79GNDIGND
80MIPI_CSI_D1N/GPI1_D0_uI/OMIPI_D1N (1.8 V)
81MIPI_CSI_D1P/GPI1_D1_uI/OMIPI_D1P (1.8 V)
82GNDIGND
83MIPI_CSI_CK0N/GPI1_D2_uI/OMIPI_CKN (1.8 V)
84MIPI_CSI_CK0P/GPI1_D3_uI/OMIPI_CKP (1.8 V)
85GNDIGND
86MIPI_CSI_D0N/GPI1_D4_uI/OMIPI_D0N (1.8 V)
87MIPI_CSI_D0P/GPI1_D5_uI/OMIPI_D0P (1.8 V)
88GNDIGND
89PWM0_CH2_M2/I2C4_SDA_M1/UART2_CTSN_M2/GPIO1_C0_dI/OMIPI_I2C_SDA (1.8 V)
90PWM0_CH1_M2/I2C4_SCL_M1/UART2_RTSN_M2/GPIO1_B7_dI/OMIPI_I2C_SCL (1.8 V)
91CAM_CLK1_OUT/I2C0_SDA_M2/UART2_RX_M2/GPIO1_B6_dI/OMIPI_RST (1.8 V)

4. Hardware Integration Guide​

Power and Boot​

4.1 5 V Power Supply​

Provide a regulated 5 V supply to Omega4. PIN23 and PIN24 are the 5 V main power inputs; connect both pins to the 5 V rail.

Place one 10 uF bulk capacitor and one 0.1 uF high-frequency decoupling capacitor close to the power pins, with a short, low-impedance return to ground.

5 V input decoupling capacitors

4.2 3.3 V and 1.8 V Power Output​

Omega4 provides one 1.8 V output (PIN5) and one 3.3 V output (PIN26) for external peripherals. These rails are intended for light loads:

  • VCC_1V8 (PIN5): up to 100 mA
  • VCC_3V3 (PIN26): up to 100 mA

Do not exceed 100 mA on either rail to avoid impacting the module's internal power rails. For higher-current devices, generate the required supplies on the carrier board.

1.8 V output (PIN5)3.3 V output (PIN26)
note

For camera designs, see Section 4.7 for MIPI-CSI 1.8 V signaling and level-shifting guidance.

4.3 RTC Power Input​

RV1103B integrates a dual-channel diode path from VCC_3V3 and VCC_RTC (PIN28). The RTC module can automatically select the active power source. It is recommended to connect VCC_RTC (PIN28) to an external supply such as a coin cell or lithium battery.

VCC_RTC requires a series resistor of 100 Ξ© or higher.

note

The RTC input is rated to a maximum of 3.63 V, so it cannot connect directly to a lithium battery (3.7 V to 4.2 V). Use a series resistor (for example 390 kΞ©) to drop the voltage before using it as VCC_RTC.

RTC power input resistor guidanceRTC power input resistor guidance detail

4.4 Pins That Affect System Boot​

PIN29 (FSPI_D0) is sampled during boot. If this pin is held low, the module enters MaskROM programming mode for recovery and firmware flashing.

You can connect FSPI_D0 to a momentary button (to ground) or expose it as a test point. Ensure the signal is not unintentionally pulled low during normal operation.

FSPI_D0 boot mode (MaskROM) circuit
note

If your design does not require a button, reserve a test point instead. This simplifies factory test and field recovery.

4.5 Debug UART​

The system default debug UART is RV1103B UART0 M0 on PIN39 (TX) and PIN40 (RX). The Wi-Fi chip also provides a debug UART on PIN49 and PIN50.

note

If the product does not require a UART header, reserve test points so it is easier to perform factory testing or issue commands during FCC/CE certification.

Debug UART pin referenceDebug UART pin reference detail

4.6 Audio & MIC​

The built-in ACODEC of the RV1103B provides:

  • One line-out output on PIN19.
  • One differential MIC input on PIN31 and PIN32.

ACODEC_AVSS (PIN18) can be combined with Lineout to form a pseudo-differential signal. This can connect to the input of an external differential power amplifier (PA) for improved audio output.

Audio line-out and mic pin referenceAudio line-out and mic pin reference detail

High-Speed and RF​

4.7 MIPI-CSI Pin Voltage​

The MIPI-CSI pins use 1.8 V logic. If you need to interface to 3.3 V devices, add level shifting.

Use case: If your design uses Omega4's MIPI_I2C to control a 3.3 V I2C peripheral, add a bidirectional I2C level shifter. A reference circuit is shown below:

MIPI I2C level shifter (1.8 V to 3.3 V)

4.8 Ethernet Port​

Reference circuit: You can use an Ethernet jack with integrated magnetics, as shown below.

Ethernet reference schematic (integrated magnetics)

4.9 Antenna Design​

Choose one antenna path, and keep the option open to support either a U.FL connector or a chip antenna on the same PCB.

Option A: Use the on-module U.FL connector for an external antenna.

Option B: Route to a chip antenna (or another RF connector) on WL_ANT (PIN58).

To support both options on a single design, add a 0-ohm resistor tied to WL_ANT:

  • U.FL mode: leave the 0-ohm resistor unpopulated.

  • Chip-antenna mode: populate the 0-ohm resistor and route to the antenna footprint.

    Two-antenna selection (0-ohm resistor option)
note

Only one of WL_ANT or the U.FL connector should be active at a time. If both are connected, transmit power is split and performance drops.

note

In a dual-use design, the trace to WL_ANT can detune the U.FL path. Keep that trace short and place the 0-ohm resistor as close to WL_ANT as possible.

4.9.1 Antenna keepout area​

The antenna keepout area is a clearance zone around the antenna footprint where you avoid copper pours, high-speed traces, and noisy components. This helps reduce detuning and RF loss.

  • Minimum required keepout: 6 x 6 mm
  • Omega4 EVB reference keepout: 7 x 25 mm

Best practices:

  • Keep the antenna at the board edge with clear line-of-sight away from metal enclosures or large ground planes.
  • Avoid stitching vias, ground pours, or signal traces inside the keepout on all layers.
  • Maintain a continuous ground reference under the RF feed trace, then transition cleanly into the keepout zone.
  • Keep the RF feed trace short; gentle curves are fine, but avoid sharp bends and stubs.

4.10 USB 2.0​

The USB port supports both Host and Device modes. During normal operation, the USB port defaults to Device mode. It can be switched to Host mode via software commands or the BOOT button.

To improve signal integrity, place a 2.2 Ξ© series resistor on both USB DP and DM.

note

If the product does not need the USB port, reserve test points so it is easier to upgrade Omega4 firmware.

USB DP/DM series resistor placement

4.11 Extended Storage​

Omega4 exposes an SDIO interface and can support Micro SD, SD NAND flash, or eMMC as extended storage.

Add pull-up resistors to the SDIO signals as required by your chosen storage device. A typical value is 10 kOhm.

4.11.1 Micro SD Card​

Use the card-detect pin (SD_DET) to detect whether a card is inserted.

By default, SD_DET is active-low: a low level indicates a card is inserted.

Add a pull-up resistor to SD_DET (typically 10 kOhm).

note

SD_DET is active-low.

Micro SD reference schematic (pull-ups and detect)

4.11.2 eMMC (TBD)​

4.11.3 SD NAND Flash (TBD)​

4.12 Integration checklist​

Use this checklist to consolidate high-level integration requirements.

4.12.1 High-speed and RF​

  • MIPI-CSI: keep pairs short, match differential pairs, and keep intra-pair skew minimal.
  • MIPI control lines are 1.8 V; add level shifting for 3.3 V peripherals.
  • USB D+/D-: 90 ohm differential, short stubs, and ESD near the connector.
  • USB-C: use a standard CC configuration or controller for the product’s fixed role.
  • Ethernet: keep differential pairs short with a solid reference plane and add ESD if external.
  • RF: 50 ohm controlled impedance with an RF keepout near the antenna region.

4.12.2 Analog and low-speed​

  • Audio: keep traces away from switching nodes and use proper AC coupling/filtering.
  • SDIO: add required pull-ups; SD_DET is active-low with a pull-up.

5. PCB Layout Design Guide​

5.1 Omega4 Footprint​

Omega4 package land pattern (top view)Omega4 package dimensions

5.2 Impedance of the PCB Line​

For best signal integrity, control the impedance of the following traces:

RF trace: 50 ohm single-ended.

note

Add ground stitching vias along the RF trace to provide a solid return path.

RF trace 50 ohm impedance example

USB D+/D- pair: 90 ohm differential.

USB differential 90 ohm impedance example

5.3 Test Points​

If your carrier PCB has enough space, add test points for key rails and signals (power, debug UART, and boot straps). A 2.0 mm or 2.54 mm pitch is typical.

6. Design Checklist​

Use this checklist to review a carrier-board design before PCB layout freeze.

6.1 Power​

  • 5 V input supply can support worst-case load (see Peak Current Requirement in Section 1.1), including any downstream peripherals powered from the carrier board.
  • Input decoupling is placed close to PIN23/PIN24 with a low-impedance ground return (Section 4.1).
  • VCC_1V8/VCC_3V3 loads stay within the limits in Section 4.2.
  • All external peripherals use the correct I/O voltage domain (1.8 V vs 3.3 V) and include level shifting where required (Section 4.7).

6.2 Boot, Recovery, and Debug​

  • FSPI_D0 (PIN29) is accessible via a test point or button and is not inadvertently held low during normal boot (Section 4.4).
  • UART debug access is available (for example, expose UART0 TX/RX plus GND on a header or test points).
  • Key rails and reset/boot strap signals have test points for manufacturing and bring-up (Section 5.3).

6.3 RF​

  • Only one RF path is active: either the on-module U.FL connector or WL_ANT (PIN58) (Section 4.9).
  • RF trace impedance is controlled (50 ohm) and the RF keepout/grounding strategy is reviewed (Section 5.2).

6.4 High-Speed Routing​

  • USB D+/D- are routed as a 90 ohm differential pair with short stubs and good reference plane continuity (Section 4.10 and Section 5.2).
  • MIPI-CSI routing, connector placement, and return paths are reviewed (Section 4.7).
  • Ethernet routing and magnetics/jack selection are reviewed (Section 4.8).

7. Bring-Up and Debug​

During early development, it is helpful to expose the following signals on an accessible header or test pads:

  • UART console TX/RX and GND (use the UART pins indicated for debug in the pin table).
  • FSPI_D0 (PIN29) test point for MaskROM entry.
  • 5 V input and a ground test point for current measurement.

7.2 First Power-On Procedure​

  1. Power the carrier board from a current-limited bench supply at 5 V.
  2. Verify no shorts on the 5 V rail and check that the steady-state current is in a reasonable range relative to the No-load Running Current in Section 1.1 (peripheral load will increase this).
  3. Verify the module boots with FSPI_D0 not asserted.
  4. If a UART console is available, capture the boot log for baseline reference.

7.3 Recovery (MaskROM)​

If the module does not boot due to firmware or storage issues:

  1. Assert FSPI_D0 (PIN29) low during boot to enter MaskROM programming mode (Section 4.4).
  2. Use your flashing/recovery toolchain to reprogram the module.
  3. Remove the assertion and reboot to return to normal boot.