Depending on WGM160P part number chosen by customer, WGM160P features or not an integrated chip antenna.
The WGM160P is certified for FCC/ISED and CE with the integrated antenna (see section 4.7 of the datasheet) or with an external antenna (See section 11.1 of the datasheet https://www.silabs.com/documents/login/data-sheets/wgm160p-datasheet.pdf). The WGM160P certification ID is provided in the datasheet so that certificates can directly be downloaded from the web (See section 11 of the datasheet).
The external antenna used for certification on RF port is 50 ohms connectorized coaxial dipole antenna with maximum gain of 2.14dBi, achieving at least -10dB return loss over WiFi frequency band. An example of such external antenna, is the Pulse Part Number W1030.
Any external antenna of the same kind and with equal or less gain and at least same -10dB VSWR over the WiFi frequency band should be fine and should not void FCC/ISED certifications as long as spot-check testing is performed to verify that no performance changes compromising compliance have been introduced.
Any other antenna (such as a chip antenna, a PCB trace antenna or a patch) will require the customer to do some testing and apply for a C2PC (Class 2 Permissive Change) as indicated by the customer’s TCB (Telecommunication Certification Body).
With CE, anyway, customer has to perform certification test with the end-product.
You could find some explanations in the section 10.3 Power On, Reset, and Boot in the WF200 datasheet :
Moreover there is also some details in https://www.silabs.com/documents/login/user-guides/ug382-wf200-hardware-design-ug.pdf in section 4,.
When device is not supplied yet, pin RESETn shall be set to LOW and No HIGH voltage is expected to be applied to input pin LP_CLK.
Once power supplies have settled, a delay of 100µs is recommended before releasing pin RESETn to HIGH.
When powering down the device, it is recommended to set RESETn pin back to LOW before shutting down its power supplies.
The power down step sets the WF(M)200 in standby mode according to these two ways below:
The BRD8022A provides a way to do current measurement (the same way is possible with the BRD8023A for WFM200).
In the blue circle, there is a way to do current measurement of the WF200. The schematic of this part is described below :
The R616 is a 0.1 Ohm resistor which connects the VMCU with the VMCU_NCP (WF200).
The J1 could be used to solder a HE10 connector (2.54mm) useful to do measurements.
So using R616 and J1, there are two ways to do WF200 current measurements during Tx, Rx or averaged on DTIM3:
Removing the R616 resistor, you could alternatively use a monitored power supply using J1, like described in the snapshot below:
To better understand the current consumption provided in the WF200 datasheet, I recommend to read the following KBA : https://www.silabs.com/community/wireless/wi-fi/knowledge-base.entry.html/2019/03/05/kba_wfx200_dtim3-tmpo
Moreover, to get the average sleep current consumption of 22uA, you should :
In order to do WF200 current measurements in Tx, Rx or in sleep state, we have used the Keysight DC power analyzer N6705C set in 2-wire sensing for short supply cables (voltage is monitored at supply output terminals) else set in in 4-wire sensing for longer twisted supply cables (voltage is monitored at the load and automatically compensate for any voltage drop within supply cables).
For more details you could read this Application Note : https://www.silabs.com/documents/public/application-notes/an1219-power-consumption-wfm200.pdf
In the datasheet, the current consumption of 337 μA in DTIM3 provides the WFx200 average current consumption when there is no TX/RX of data frame (only receiving Beacon with the DTIM interval and using the sleep state).
So with this consumption, the WFx200 stays associated with the Wi-Fi Access Point ready to transmit or receive data frame and it goes in sleep state between two Rx beacons with a current consumption of only 22 μA.
The 337 μA current are measured in DTIM3 when the WFX200 receives only one over 3 beacons with a beacon interval of 102ms and a beacon time duration of 1ms.
In theory, yes, since the driver is compatible with Linux kernel from 4.4.1 up to 4.19.
Has it been tested? Not yet.
Linux applications use
Android uses different applications for AP/STATION management, therefore testing would be required to make sure there is no unexpected behavior in an Android application.
The WF200 Linux driver (available at https://github.com/SiliconLabs/wfx-linux-driver) is API compliant with all kernel versions from 4.4.1 upwards.
The wfx-linux-driver is in 'staging' state in the mainstream Linux kernel as from 5.5 (see https://elixir.bootlin.com/linux/v5.5/source/drivers/staging/wfx),
The official source for updates is (https://github.com/SiliconLabs/wfx-linux-driver).
Files used by WF200 under Linux on Raspberry Pi (Debian)
Driver & Firmware: https://github.com/SiliconLabs/wfx-fullMAC-driver