conga-SMX8 HD Wireless SPB228

This section applies to the conga-SMX8 variants with onboard SBP228 Wifi option only (that is congatec part number 051005 and 051025).

Configuring the Wifi connection

The onboard Wifi module is connected via the 2nd PCIe interface (pcieb) of the i.MX 8 SOC. This interface is disabled by default and has to be activated by
the corresponding DTB file during kernel boot. To do this, either imx8qm-cgtsmx8-pcieb.dtb or imx8qm-cgtsmx8-hdmi-pcieb.dtb have to be specified for the
bootloader environment variable "fdt_file".

On bootloader level, specify:

=> setenv fdt_file imx8qm-cgtsmx8-pcieb.dtb
=> savee

Or, in case HDMI output is desired:

=> setenv fdt_file imx8qm-cgtsmx8-hdmi-pcieb.dtb
=> savee

In the root filesystem of the target system, edit the file <code>/etc/wpa_supplicant.conf</code> and configure the wifi network
(replace \<SSID-of-WIFI-NETWORK> and \<KEY> with proper values).

A) For Yocto BSP Sumo (2.5) with Kernel 4.14 use:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1

network={
        ssid="<SSID-of-WIFI-NETWORK>"
        proto=WPA2
        key_mgmt=WPA-PSK
        psk="<KEY>"
}

B) For Yocto BSP Zeus (3.0) with Kernel 5.4 use:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=DE

network={
        ssid="<SSID-of-WIFI-NETWORK>"
        proto=WPA2
        key_mgmt=WPA-PSK
        psk="<KEY>"
}

Instead of specifying the key directly in ASCII in the configuration file, the tool "wpa_passphrase" can be used to pre-compute a PSK from the ASCII
passphrase and the SSID:

# wpa_passphrase <SSID-of-WIFI-NETWORK> <KEY>

Copy the result of the command and paste it into the /etc/wpa_supplicant.conf

Testing the Wifi connection

If everything is configured properly, the connection can be established:

# wpa_supplicant -B -i mlan0 -c /etc/wpa_supplicant.conf
# udhcpc -i mlan0

A dhcp address should be assigned and access to the network should be possible, e.g. via ping, ssh, e.g.:

# ssh devel@192.168.2.1

The connection to the network can be verified via:

# iw dev mlan0 link
Connected to 18:83:bf:66:d4:e5 (on mlan0)
        SSID: MyWiFiSSID
        freq: 5180
        RX: 11003 bytes (97 packets)
        TX: 6130 bytes (55 packets)
        signal: -65 dBm
        tx bitrate: 175.6 MBit/s VHT-MCS 2 80MHz VHT-NSS 2

        bss flags:
        dtim period:    3
        beacon int:     100

Testing the bluetooth connection

Start the bluetoothctl command line interface and list the controllers. Make sure the SPB228 is the selected default, this is important if there is already an internal controller on your PC:

# bluetoothctl
[bluetooth]# list
Controller 78:C4:0E:A0:82:AF imx8qm-cgtsmx8 [default]
[bluetooth]# select 78:C4:0E:A0:82:AF

Start and stop scanning:

[bluetooth]# power on
[bluetooth]# scan on
Discovery started
[CHG] Controller 78:C4:0E:A0:82:AF Discovering: yes
[...]
[NEW] Device C4:42:02:64:9C:CA BT-Device
[...]
[bluetooth]# scan off

Pair and connect to the device:

[bluetooth]# pair C4:42:02:64:9C:CA
Attempting to pair with C4:42:02:64:9C:CA
[CHG] Device C4:42:02:64:9C:CA Connected: yes
[CHG] Device C4:42:02:64:9C:CA UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device C4:42:02:64:9C:CA ServicesResolved: yes
[CHG] Device C4:42:02:64:9C:CA Paired: yes
Pairing successful
[BT-Device]# connect C4:42:02:64:9C:CA
Attempting to connect to C4:42:02:64:9C:CA
Connection successful
[CHG] Device C4:42:02:64:9C:CA UUIDs: 00001101-0000-1000-8000-00805f9b34fb