The Sona MT320 is a 5.4 spec Dual-Mode Bluetooth radio. The primary Bluetooth features are:

• BDR + EDR + BLE (Classic + BLE)
• LE 2 Mbps PHY
• LE Long Range (LE-LR)
• Adaptive Frequency Hopping (AFH)
• Secure Simple Pairing (SSP)
• UART baud rates upto 4 Mbps
• 7 x Classic Bluetooth links
• 16 x BLE links
• Secure connection (AES128 & ECC256)

The Sona MT320 uses SDIO 3.0 for both Wi-Fi and Bluetooth.

The Sona MT320 was built specifically to work with the Mediatec Genio line of processors as well as Ezurio's Mediatec based System On Modules.

For that reason, as of January 1st, 2025, support for the Sona MT320 has not been added to Ezurio's backport package.

The Sona MT320 was designed to specifically work with Mediatek Genio processors.

As of January 1st, 2025, the Sona MT320 has been tested on these processors/EVKs

• Mediatek Genio 510
• Mediatek Genio 700

Note: If you are using either the Ezurio Tungsten510 SMARC SOM or the Ezurio Tungsten700 SMARC SOM , the Sona MT320 is already built in. The code is available here:

• Tungsten510 SMARC
• Tungsten700 SMARC

As of January 1st, 2025, the MT320 supports the following regulatory domains:

• FCC (USA)
• ISED (Canada)
• UKCA (UK)
• ETSI (EU)

Please check the Regulatory Information Guide under Documentation/Certification on the MT320 webpage.

The power tables are built into the device tree. A patch needs to be added to your kernel recipe. The patch can be downloaded here: Patch. Add the patch as is to your kernel using bbappend. You will then need to create a patch for your DTS. It will look similar to this:
From 6b74d5a3c7801d4a3a5d77b4ef7d4b4c68a10425 Mon Sep 17 00:00:00 2001
From: Gary Bisson
Date: Thu, 28 Mar 2024 12:06:10 +0100
Subject: [PATCH] arm64: dts: mt83x0-tungsten-smarc: include mt320 power tables

Signed-off-by: Gary Bisson
arch/arm64/boot/dts/mediatek/mt83x0-tungsten-smarc.dtsi | 1 +
1 file changed, 1 insertion(+)

diff --git a/arch/arm64/boot/dts/mediatek/mt83x0-tungsten-smarc.dtsi b/arch/arm64/boot/dts/mediatek/mt83x0-tungsten-smarc.dtsi
index 6b0ad0c76841..1a0414052fa0 100644
--- a/arch/arm64/boot/dts/mediatek/mt83x0-tungsten-smarc.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt83x0-tungsten-smarc.dtsi
@@ -669,6 +669,7 @@
    vmmc-supply = <&sdio_fixed_3v3>;
    vqmmc-supply = <&mt6359_vcn18_ldo_reg>; // VCN18_WIFI
    mmc-pwrseq = <&wifi_pwrseq>;
+#include "mt7921-mt320-tables.dtsi"
};

&spi0 {

The above is an example. Your file will be specific to your device tree settings.

Note: To Leverage Ezurio's regulatory grants, you must use our power tables

An Ezurio Wi-Fi module can be configured for AP-Sta mode with the following nmcli commands:

• iw dev wlan0 interface add wlan1 type __ap
• nmcli con add con-name myap ifname wlan1 type wifi ssid myapssid autoconnect yes 802.11-wireless.mode ap ipv4.method shared
• nmcli con add con-name mysta ifname wlan0 type wifi ssid mystassid

This is assumes that you have the iw and dnsmasq packages installed in your build.

Note: In the above configuration, the Access Point will follow the channel that the station associates to. Therefore it is reccomended that the client is configured to use a 2.4 GHz channel or the U-NII-1 channels in the 5 GHz band as the Ezurio radios will not work as DFS masters and do not support AP mode in the rest for the 5 GHz channels nor in the 6 GHz band.>

One of the new features in Wi-Fi 6 is a longer guard interval. The guard interval is used to help mitigate multipath or overlapping transmissions. This is done by adding a delay between symbols (set of 0s and 1s). The shorter the guard interval theoretically the faster the throughput but you are more susceptible to multipath due to metal and other reflective surfaces.

Wi-Fi 4 and 5 supported two guard intervals:

• Short - 0.4 microseconds
• Long - 0.8 microseconds

Wi-Fi 6 supports 3 guard intervals:

• Normal - 0.8 microseconds
• Double - 1.6 microseconds
• Quadruple - 3.2 microseconds

In Wi-Fi 6 the 1024-QAM allows up to a 4x longer symbol duration than in Wi-Fi 5, so the efficiency is still similar to Wi-Fi 5 even with Quadruple guard interval.

What guard interval should I use for various use cases?

A general rule of thumb should be:

• Normal - Use this in a clean open area without a lot of metal. This would also best be used outdoors. Normal Guard Interval is the best choice when throughput is of the utmost importance.
• Double - This is a good compromise between Normal and Quadruple. It will not provide as good of throughput as Normal but will reduce the likelihood of multipath in areas that are smaller or have some metal.
• Quadruple - This would be used in small areas or areas with a lot of metal. This would also be the best choice in areas with a lot of clients to reduce the overhead of retrying packets.

All of the Wi-Fi 6 features are supported in the 2.4 GHz band in a Wi-Fi 6 radio.

This was not the case in Wi-Fi 5. It reverted back to Wi-Fi 4 in the 2.4 GHz channels.

Yes, Laird Wifi modules can be integrated with OpenWRT like with other Linux operating systems.

See Lairds "Guide" Section for an example:

https://www.ezurio.com/documentation/application-note-how-to-integrate-the-60-series-wifi-module-with-openwrt