GPIO Fixed Function |
GP_H11/AVS_I2S2_SCLK | I/O | For CNVi: Unused For standard CNV with UART host support: Optional Bluetooth I2S bus clock |
GP_H12/AVS_I2S2_SFRM/CNV_RF_RESET_N | I/O | For CNVi: RF companion (CRF) reset signal, active low. Require a 75KOhm Pull-Down on platform/motherboard level. Recommended not use it for bootstrapping during early Platform init flows. For standard CNV with UART host support: Optional Bluetooth I2S bus sync |
GP_H13/AVS_I2S2_TXD/MODEM_CLKREQ | O | For CNVi: Clock request signal. Used to request the RF companion clock (38.4M Ref clock); In PCH this function is not used, BUT this signal is also used for CNVi Init flow, so it must be connected on platform level even when clk sharing ability is not used/feasible. PCH is using internal clk (38.4 MHz clk) and NOT taking this clk from the CRF (as was optional in previous generations) For standard CNV with UART host Bluetooth* support: Optional Bluetooth* I2S bus data output (input to BT module). |
GP_H14/AVS_I2S2_RXD | I | For CNVi: Unused. For standard CNV with UART host support: Optional Bluetooth* I2S bus data output (input to BT module) |
GP_E20/CNV_BRI_DT | O | For CNVi: BRI bus TX. For standard CNV CNV with UART host support: BT UART RTS# Require a 100-50-20KOhm (any of) Pull-up on platform/motherboard level. Recommended not use it for bootstrapping during early Platform init flows |
GP_E21/CNV_BRI_RSP | I | For CNVi: BRI bus RX. For standard CNV CNV with UART host support: BT UART RXD |
GP_E22/CNV_RGI_DT | O | For CNVi: RGI bus TX. For standard CNV with UART host support: BT UART TXD |
GP_E23/CNV_RGI_RSP | I | For CNVi: RGI bus RX. For standard CNV with UART host support: BT UART CTS# |
GP_H01/SD_SDIO_PWR_EN_N/CNV_RF_RESET_N | O | For CNVi (main): RF companion (CRF) reset signal, active low. Require a 75KOhm Pull-Down on platform/motherboard level. Recommended not use it for bootstrapping during early Platform Init flows. |
GP_H02/MODEM_CLKREQ | O | For CNVi(main): Clock request signal. Used to request the RF companion clock (38.4M Ref clock); In PCH this function is not used, BUT this signal is also used for CNVi Init flow, so it must be connected on platform level even when clk sharing ability is not used/feasible. PCH using internal clk (38.4 MHz clk) and NOT taking this clk from the CRF (as was optional in previous generations) |
GP_D21/CNV_PA_BLANKING | I | For CNVi and standard CNV: Optional WLAN/BT-WWAN coexistence signal COEX3. Used to be co-existence signal for external GNSS solution |
GP_D19/CNV_MFUART2_RXD | I/O | For CNVi and standard CNV: Optional WLAN/BT-WWAN coexistence signal COEX (Input) |
GP_D20/CNV_MFUART2_TXD | I/O | For CNVi and standard CNV: Optional WLAN/BT-WWAN coexistence signal COEX (Output) |
Fixed Special Purpose I/O |
CNV_WT_CLKP | O | CNVio bus TX CLK+ |
CNV_WT_CLKN | O | CNVio bus TX CLK- |
CNV_WT_D0P | O | CNVio bus Lane 0 TX+ |
CNV_WT_D0N | O | CNVio bus Lane 0 TX- |
CNV_WT_D1P | O | CNVio bus Lane 1 TX+ |
CNV_WT_D1N | O | CNVio bus Lane 1 TX- |
CNV_WR_CLKP | I | CNVio bus RX CLK+ |
CNV_WR_CLKN | I | CNVio bus RX CLK- |
CNV_WR_D0P | I | CNVio bus Lane 0 RX+ |
CNV_WR_D0N | I | CNVio bus Lane 0 RX- |
CNV_WR_D1P | I | CNVio bus Lane 1 RX+ |
CNV_WR_D1N | I | CNVio bus Lane 1 RX- |
CNV_WT_RCOMP | O | WiFi DPHY RCOMP, analog connection point for an external bias resistor to ground |
Selectable Special Purpose I/O |
USB2P_8 | | Bluetooth USB host bus (positive) for standard CNV. Optional to connect to a Bluetooth USB+ pin on the Bluetooth module. Port 8 is the recommended port . |
USB2N_8 | | Bluetooth USB host bus (negative) for standard CNV. Optional to connect to a Bluetooth USB- pin on the Bluetooth module. Port 8 is the recommended port. |
W_disable1#(GPIO) | I | Used for Wi-Fi* RF-Kill control. This pin can be connected to a platform switch or to SoC GPIOs (recommendation- if possible do not use GPIOs that have Platform impact as “bootstraps” during platform init). |
W_disable2#(GPIO) | I | Used for BT RF-Kill control. This pin can be connected to a platform switch or to SoC GPIOs (recommendation- if possible do not use GPIOs that have Platform impact as “bootstraps” during platform init). |