UM11483 Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS Rev. 2 — 21 January 2021 User manual Document information Information Content Keywords i.MX 8M Quad Evaluation Kit (EVK), 88W8987-based wireless module, 88W8997-based wireless module Abstract Details the bring-up of Wi-Fi and Bluetooth on NXP-based wirelesss modules connected with i.MX 8M Quad EVK running on Linux OS
41
Embed
Getting Started with NXP Wireless Modules for i.MX 8M-Quad ...Getting Started with NXP Wireless Modules for i.MX 8M-Quad Platforms Please be aware that important notices concerning
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
UM11483Getting Started with NXP-based Wireless Modules on i.MX 8MQuad EVK Running Linux OSRev. 2 — 21 January 2021 User manual
Abstract Details the bring-up of Wi-Fi and Bluetooth on NXP-based wirelesss modulesconnected with i.MX 8M Quad EVK running on Linux OS
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
Rev Date Description
v.1 20201015 Initial version
v.2 20210121 Modifications• Extended the scope to 88W8987- and 88W8997-based wireless modules• Updated the document title and overall document structure
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
1 About this document
1.1 Purpose and scopeThis document details the enabling of wireless solutions on i.MX 8M Quad evaluationkit. The i.MX 8M Quad EVK is powered by Linux and the NXP Linux drivers are used forNXP-based wireless modules. The manual covers the bring-up of i.MX 8M Quad EVK,the configurations for the BSP image and the hardware connection with NXP-basedwireless modules. The later chapters describe how to bring up the Wi-Fi and Bluetoothinterfaces.
This document specifies the hardware interconnection and software support for the i.MX8M Quad evaluation kit and AzureWave AW-CM358-uSD, AW-CM358MA, and AW-CM276MA modules to enable Wi-Fi/Bluetooth functionality. Note that the Azurewavemodule AW-CM358-uSD only supports Wi-Fi with the i.MX 8M Quad EVK.
Once you have enabled the Wi-Fi and/or Bluetooth interfaces, refer to the user manualUM11490 that details the Wi-Fi and Bluetooth features and configurations for i.MX 8MQuad EVK.
Note: This document does not provide a detailed description of the i.MX 8M Quad BSPnor how to generate an image and rootfs as these are covered in i.MX Yocto ProjectUser's Guide.
1.2 References
Reference type Description
Datasheet NXP - DS - 88W8987 - 2.4/5 GHz Dual-Band 1x1 Wi-Fi 5 and Bluetooth 5 Solution (link)
Datasheet AzureWave - AW-CM358SM - IEEE 802.11a/b/g/n/ac WLAN with Bluetooth 5 Combo Stamp LGAModule (link)
Datasheet AzureWave - AW-CM276MA-PUR - IEEE 802.11a/b/g/n/ac Wireless LAN 2T2R and Bluetooth 5.0Combo Module (M.2 2230) (link)
Fact sheet NXP - FS - 88W8997-802.11ac wave 2 2x2 Wi-Fi Dual-band with Bluetooth 5 SoC (link)
Fact sheet NXP - Evaluation Kit Based on i.MX 8M Quad Application Processors (link)
User guide AzureWave - AW-CM358-uSD - uSD-1212 Adapter Board for AW-AM281-uSD and AW-CM358-uSD(link)
User manual NXP - UM - i.MX Yocto Project User's Guide (link).
User manual NXP - UM - i.MX Linux® User's Guide (link).
User manual NXP - UM11490 - Feature Configuration Guide for NXP-based Modules with i.MX 8M Quad EVK (link)
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
2 i.MX 8M Quad evaluation kit (EVK)
2.1 I.MX 8M Quad EVK overviewNXP i.MX 8M Quad Evaluation Kit (EVK) provides a platform for rapid evaluation of thei.MX 8MQuad, i.MX 8MDual and i.MX 8MQuadLite application processors, utilizing dualto quad Arm Cortex-A53s and single Cortex-M4 cores.
The EVK includes the hardware design files, tools and board support packages (BSPs)for Linux where:
• The i.MX 8M Quad Linux Board Support Package (BSP) supports the Linux OperatingSystem (OS) on the i.MX 8M Quad application processors. The purpose of thissoftware package is to enable Linux support on the i.MX 8M Quad family of IntegratedCircuits (ICs) and their associated platforms. It provides the necessary software tointerface the standard open-source Linux kernel to the i.MX 8M Quad hardware.
• The i.MX 8M Quad BSP is based on the latest long-term stable (LTS) version ofthe Linux kernel, which is enhanced with the features provided by NXP and can beaccommodate customized Linux kernel configurations.
2.2 i.MX 8M Quad evaluation boardThe i.MX 8M Quad evaluation board is based on the NXP i.MX 8M Quad applicationprocessor. The i.MX 8M Quad processor features an advanced implementation ofthe Quad Arm Cortex-A53+ ARM Cortex-M4 core which operates at speeds up to1.5 GHz and 266 MHz respectively. The i.MX 8M Quad features an integrated powermanagement module that reduces the complexity of an external power supply andsimplifies the power sequencing. Each processor provides a 32-bit LVDDR3L/DDR4/LPDDR4 memory interface and other interfaces to connect peripherals such as HDMI,LCD, Wi-Fi, Bluetooth, GPS and camera sensors.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
2.4 i.MX 8M Quad switch settingsFigure 4 shows the two switches on i.MX 8M Quad evaluation board. The Boot DeviceSwitch is used to select the boot drive while the Boot Mode Switch is used to set the bootmode.
Figure 4. Boot device switch and boot mode switch on i.MX 8M Quad evaluation board
Table 3 shows the settings of the boot mode switch.
D1 D2 Boot mode
0 1 Serial downloader
1 0 Internal boot
Table 3. Boot mode switch settings
Table 4 shows the settings of the boot device switch to boot from eMMC.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
3 NXP-based wireless modules
This document revision addresses 88W8987-based and 88W8997-based wirelessmodules.
• 88W8987: refer to 88W8987 short datasheet and 88W8987 product overview on NXPwebsite.
• 88W8997: refer to 88W8997 fact sheet and 88W8997 product overview on NXPwebsite.
3.1 Interface with i.MX 8M Quad application processorFigure 5 shows the high-level block diagram of i.MX 8M Quad application processor withthe Wi-Fi (SDIO/PCIe) and Bluetooth (UART) hardware interfaces used to communicatewith NXP-based wireless module.
Figure 5. Interface between the i.MX 8M Quad application processor and NXP-based wireless module
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
3.2 Wi-Fi layer interfacesThe wireless module requires a kernel driver loaded on the i.MX 8M Quad host systemand a firmware running on 88W8987/88W8997 SoC. The MLAN module downloadsthe firmware binary to the SD8987/PCIE8997 adapter when the SDIO/PCIe bus driverdetects the SDIO/PCIe interface of the module. The kernel driver (SD8987/PCIE8997) isloaded between the bus driver and the network stack from the cfg80211 subsystem in thekernel. NXP kernel driver includes a set of controls and configurations to communicatewith the user space through one of the following interfaces:
• Input/output control (IOCTL)• Wireless Extension (Wext)• CFG80211
The IOCTL provides a path to the user space applications iwconfig and iwprivwhereas cfg80211 interface provides a different path to the user space applicationswpa_supplicant, hostapd and iw.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
3.3 Bluetooth layer interfacesFigure 7 illustrates the layers between the user applications and the NXP-basedBluetooth module. The NXP-based wireless module requires a kernel driver loaded onthe i.MX 8M Quad host system and a firmware running on NXP SoC. The Wi-Fi driverloads the combo firmware. The hci_uart driver provides the HCI interface between thefirmware and user application.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
3.4 88W8987-based Azurewave AW-CM358-uSD moduleAzurewave provides a micro-SD card interface adapter (uSD-1212) with AW-CM358SMmodule that is compatible with the i.MX 8M Quad EVK. The AW-CM358-uSD supportsWi-Fi through a uSD device interface that conforms to the industry SDIO Full-Speedcard specification and allows a host controller using the SDIO bus protocol to accessthe Wireless SoC device. The AW-CM358-uSD acts as the device on the SDIO bus, andfeatures the following:
• SDIO 3.0 standard• On-chip memory used for CIS• Supports 1-bit SDIO and 4-bit SDIO transfer modes• Special interrupt register for information exchange
3.4.1 Recommended antenna part
MAG.LAYERS: MSA-4008-25GC1-A2
3.4.2 Supported I/O signal level
• SDIO (3.0/2.0) supports 1.8V for I/O signal
3.4.3 Supported RF standard
I/O voltage level Wi-Fi Bluetooth
AW-CM358-uSD 1x1 Wi-Fi 5 (2.4/5 GHz) 5.0
Table 5. Supported RF standard
3.4.4 Supported Wi-Fi features
AW-CM358-uSD and AW-CM358MA modules share the same Wi-Fi feature set. Refer toAzurewave AW-CM358SM Datasheet.
Note: Azurewave AW-CM358-uSD supports both Wi-Fi and Bluetooth RF standards. Butas i.MX 8M Quad EVK does not include the FFC connector for Bluetooth interface, onlyWi-Fi is supported for i.MX 8M Quad platform with AW-CM358-uSD module combination.
3.4.6 Azurewave AW-CM358-uSD module jumpers and power supply
This section provides the jumper settings to configure the module with 1.8V SDIO voltagelevel for Wi-Fi. Connect the jumper J2 between the 1 and 2 header pins to select theSDIO module power source and connect the jumper J4 between the 1 and 2 header pinsfor 1.8V SDIO voltage as shown in Figure 9.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
3.5 88W8987-based AzureWave AW-CM358MA moduleThe AW-CM358MA module supports a SDIO device interface that conforms to theindustry standard SDIO Full-Speed card specification and allows a host controller usingthe SDIO bus protocol to access the Wireless SoC device.
The AW-CM358MA is a Wi-Fi 5 and Bluetooth 5 combo stamp module with the M.2adaptor board that features:
• SDIO 3.0 standard• On-chip memory used for CIS• 1-bit SDIO and 4-bit SDIO transfer modes• A special interrupt register for information exchange
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
3.5.6 i.MX 8M Quad rework for SDIO support on M.2
The M.2 connector on AW-CM358MA wireless module supports SDIO interface for Wi-Fi whereas the i.MX 8M Quad M.2 connector supports PCIe interface by default. Thissection shows how to rework i.MX 8M Quad resistors to support SDIO on M.2 connectorfor the AW-CM358MA module.
Note: The hardware rework instructions reroute the SDIO interface from the SD cardconnector to the M.2 connector. A software change is also required to enable thererouted SDIO interface. Please refer to Section 4.5.3 "Enabling SDIO on M.2 (AW-CM358MA module only)" to enable the SDIO interface on the M.2 connector using a DTBfile. Note that the SDIO on the Micro SD card slot will be disabled after the rework.
• Silkscreen of PCBA SCH-38820 / PCBA SCH-29615
• Remove the following 0Ω 0402 resistors: R1603, R1617, R1618, R1619, R1620 andR1621 (micro SD card J1601)
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
3.6 88W8997-based AzureWave AW-CM276MA moduleAzureWave AW-CM276MA supports PCIe and high-speed UART interfaces to the hostprocessor for Wi-Fi and Bluetooth. Refer to AzureWave AW-CM276MA-PUR Datasheet.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
4 i.MX 8M EVK Linux image setup
The i.MX 8M Quad Linux BSP is a collection of binary files, source code, and supportfiles used to create a U-Boot bootloader, a Linux kernel image, and a root file system fori.MX 8M Quad development platforms.
All the information on how to set up the Linux OS host, how to run and configure a YoctoProject, generate an image, and generate a rootfs, are covered in the i.MX Yocto ProjectUser's Guide. On i.MX 8M Quad, four elements are needed:
• imx-boot (built by imx-mkimage), which includes SPL, U-Boot, Arm Trusted Firmware,DDR firmware, and HDMI firmware
• Linux kernel image• A device tree file (.dtb) for the board being used• A root file system (rootfs) for the specific Linux image
Read more in section 4.1 of i.MX Linux® User's Guide, document number “IMXLUG”.
4.1 Using the pre-built imageThis section describes the steps to prepare eMMC to boot up an i.MX 8M Quad EVKusing a Linux host machine. The pre-built image can be downloaded from the pageEmbedded Linux for I.MX Application Processors on NXP website. Accept NXP softwarelicense agreement when prompted.
The release contains a pre-built image that is built specifically for the board configuration.It does not run on other boards unless U-Boot, the device tree, and rootfs are changed.
Note: A pre-built image contains all the image elements and does not require to buildthe image using the Yocto setup. So the user can skip Section 4.2 "Setting up the host",Section 4.3 "Building the image", and Section 4.3.3 "Image deployment".
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
4.2 Setting up the hostInstall the packages and utilities to set up Ubuntu 16 Linux host machine. The hard diskspace required is about 50 GB. It is recommended that at least 120 GB is provided,which is enough to compile all the backends. The recommended minimum Ubuntuversion is 16.04 or later.
4.2.1 Installing the host packages
Install the host packages on the build machine to set up the build environment.
The configuration tool uses the default version of grep that is on your build machine.
4.2.2 Setting up Repo utility
Repo is a tool built on top of Git that makes it easier to manage projects that containmultiple repositories which do not need to be on the same server.
Follow these steps to install the repo utility:
• Create a bin folder in the home directory
ubuntu@ubuntu-desktop:/# mkdir ~/bin (this step may not be needed if the bin folder already exists)ubuntu@ubuntu-desktop:/# curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repoubuntu@ubuntu-desktop:/# chmod a+x ~/bin/repo
• Add the following line to the .bashrc file to ensure that the ~/bin folder is in your PATHvariable
The following example shows how to download the i.MX Yocto Project Community BSPrecipe layers. For this example, a directory called imx-yocto-bsp is created for the project.You can use any other name.
Refer to i.MX Release Manifest for the list of all manifest files supported in this release.
ubuntu@ubuntu-desktop:/# repo sync
When this process is completed, the source code is checked out into the directory imx-yocto-bsp/sources. Use repo sync periodically to update to the latest code. The repo initis configured for the latest patches.
Note: Check the section Yocto Project Setup in i.MX 8M Yocto Project User's Guide incase some newer source code is available.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
4.3 Building the imageThis section provides the information along with the instructions to build an image.
4.3.1 Build configurations
The i.MX BSP provides the script imx-setup-release.sh, which simplifies the process ofcreating a new built target for the i.MX BSP. A built target is any combination of targeti.MX chipset, and distribution. The script sets up a directory and the configuration files forthe specified machine and backend.
i.MX 8M Quad machine configuration file is imx8mqevk and the distro configuration is fsl-imx-xwayland.
The syntax for the imx-setup-release.sh script is as follows:
When the script is running, it prompts the user to accept EULA license agreement. Oncethe EULA is accepted, the acceptance is stored in local.conf inside each build folder andthe EULA acceptance query is no longer displayed for that build folder.
4.3.2 Command to build an image
The Yocto Project build uses the bitbake command. For example, bitbake<component> builds the named component. Each component build has multiple tasks,such as fetching, configuring, compiling, packaging, and deploying to the target rootfs.The bitbake image build gathers all the components required by the image and buildfollowing the order of the dependency per task.
The filesystem images are deployed to <build directory>/tmp/deploy/images/imx8mqevk/.An image is, for the most part, specific to the machine set in the environment setup.Each image build creates a U-Boot, a kernel, and an image type based on theIMAGE_FSTYPES defined in the machine configuration file. Most machine configurationsprovide an SD card image (.wic) and a rootfs image (.tar).
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
4.4 Flashing the image to eMMCThe Universal Update Utility (UUU) runs on a Windows or Linux OS host and is used todownload images to different devices on an i.MX board.
Download UUU
Download UUU version 1.2.135 or later from https://github.com/NXPmicro/mfgtools/releases.
Copy UUU
Copy the uuu binary into the /usr/bin/ directory and change the permission to executable.
Follow these instructions to use UUU for i.MX 8M Quad:
• Connect a USB cable from a computer to the USB OTG/TYPE C port on the board• Connect a USB cable from the OTG-to-UART port to the computer for console output• Open a Terminal emulator program (for example minicom)• Set the boot pin to serial download mode (refer to Section 2.4 "i.MX 8M Quad switch
Note: This section only applies to AW-CM358MA module based on M.2 connector. TheSDIO on M.2 DTB is necessary to enable the SDIO interface on the M.2 connector. Bydefault the SDIO support is enabled for the SD Card slot connector. The hardware reworkinstructions are given in Section 3.5.6 "i.MX 8M Quad rework for SDIO support on M.2".
4.5.4 Software package release version information
The software package release version information is provided in the release notes.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
5 Bring-up of Wi-Fi interfaces
This section describes the bring-up steps for the Wi-Fi interfaces of the NXP-basedwireless module connected to i.MX 8M Quad EVK.
5.1 Bring-up of 88W8987-based wireless module (AW-CM358MA)Follow these instructions to load the driver modules and bring up the 88W8987-basedwireless module
• Use the nano editor included in the pre-built image to edit and verify the moduleparameters in wifi_mod_para.conf configuration file
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
5.2 Bring-up of 88W8997-based wireless module (AW-CM276MA)Follow these instructions to load the driver modules and bring up the 88W8987-basedwireless module
• Use the nano editor included in the pre-built image to edit and verify the moduleparameters in wifi_mod_para.conf configuration file
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
6 Bring-up of Bluetooth interfaces
Note: You must first load the combo firmware and initialize the Wi-Fi driver prior toinitializing the Bluetooth interface. Refer to Plugging the wireless module and Section 5.3"Bring up the Wi-Fi interface" .
Use the following steps to bring up the Bluetooth interfaces.
NXP Semiconductors UM11483Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS
9 Legal information
9.1 DefinitionsDraft — A draft status on a document indicates that the content is stillunder internal review and subject to formal approval, which may resultin modifications or additions. NXP Semiconductors does not give anyrepresentations or warranties as to the accuracy or completeness ofinformation included in a draft version of a document and shall have noliability for the consequences of use of such information.
9.2 DisclaimersLimited warranty and liability — Information in this document is believedto be accurate and reliable. However, NXP Semiconductors does notgive any representations or warranties, expressed or implied, as to theaccuracy or completeness of such information and shall have no liabilityfor the consequences of use of such information. NXP Semiconductorstakes no responsibility for the content in this document if provided by aninformation source outside of NXP Semiconductors. In no event shall NXPSemiconductors be liable for any indirect, incidental, punitive, special orconsequential damages (including - without limitation - lost profits, lostsavings, business interruption, costs related to the removal or replacementof any products or rework charges) whether or not such damages are basedon tort (including negligence), warranty, breach of contract or any otherlegal theory. Notwithstanding any damages that customer might incur forany reason whatsoever, NXP Semiconductors’ aggregate and cumulativeliability towards customer for the products described herein shall be limitedin accordance with the Terms and conditions of commercial sale of NXPSemiconductors.
Right to make changes — NXP Semiconductors reserves the right tomake changes to information published in this document, including withoutlimitation specifications and product descriptions, at any time and withoutnotice. This document supersedes and replaces all information supplied priorto the publication hereof.
Suitability for use — NXP Semiconductors products are not designed,authorized or warranted to be suitable for use in life support, life-critical orsafety-critical systems or equipment, nor in applications where failure ormalfunction of an NXP Semiconductors product can reasonably be expectedto result in personal injury, death or severe property or environmentaldamage. NXP Semiconductors and its suppliers accept no liability forinclusion and/or use of NXP Semiconductors products in such equipment orapplications and therefore such inclusion and/or use is at the customer’s ownrisk.
Applications — Applications that are described herein for any of theseproducts are for illustrative purposes only. NXP Semiconductors makesno representation or warranty that such applications will be suitablefor the specified use without further testing or modification. Customersare responsible for the design and operation of their applications andproducts using NXP Semiconductors products, and NXP Semiconductors
accepts no liability for any assistance with applications or customer productdesign. It is customer’s sole responsibility to determine whether the NXPSemiconductors product is suitable and fit for the customer’s applicationsand products planned, as well as for the planned application and use ofcustomer’s third party customer(s). Customers should provide appropriatedesign and operating safeguards to minimize the risks associated withtheir applications and products. NXP Semiconductors does not accept anyliability related to any default, damage, costs or problem which is basedon any weakness or default in the customer’s applications or products, orthe application or use by customer’s third party customer(s). Customer isresponsible for doing all necessary testing for the customer’s applicationsand products using NXP Semiconductors products in order to avoid adefault of the applications and the products or of the application or use bycustomer’s third party customer(s). NXP does not accept any liability in thisrespect.
Export control — This document as well as the item(s) described hereinmay be subject to export control regulations. Export might require a priorauthorization from competent authorities.
Evaluation products — This product is provided on an “as is” and “with allfaults” basis for evaluation purposes only. NXP Semiconductors, its affiliatesand their suppliers expressly disclaim all warranties, whether express,implied or statutory, including but not limited to the implied warranties ofnon-infringement, merchantability and fitness for a particular purpose. Theentire risk as to the quality, or arising out of the use or performance, of thisproduct remains with customer. In no event shall NXP Semiconductors, itsaffiliates or their suppliers be liable to customer for any special, indirect,consequential, punitive or incidental damages (including without limitationdamages for loss of business, business interruption, loss of use, loss ofdata or information, and the like) arising out the use of or inability to usethe product, whether or not based on tort (including negligence), strictliability, breach of contract, breach of warranty or any other theory, even ifadvised of the possibility of such damages. Notwithstanding any damagesthat customer might incur for any reason whatsoever (including withoutlimitation, all damages referenced above and all direct or general damages),the entire liability of NXP Semiconductors, its affiliates and their suppliersand customer’s exclusive remedy for all of the foregoing shall be limited toactual damages incurred by customer based on reasonable reliance up tothe greater of the amount actually paid by customer for the product or fivedollars (US$5.00). The foregoing limitations, exclusions and disclaimers shallapply to the maximum extent permitted by applicable law, even if any remedyfails of its essential purpose.
Translations — A non-English (translated) version of a document is forreference only. The English version shall prevail in case of any discrepancybetween the translated and English versions.
9.3 TrademarksNotice: All referenced brands, product names, service names andtrademarks are the property of their respective owners.
CM358MA module ...........................................163.5.1 Recommended antenna part ........................... 163.5.2 Supported RF standards ................................. 163.5.3 Supported Wi-Fi features .................................163.5.4 Supported Bluetooth features .......................... 163.5.5 AW-CM358MA module view ............................173.5.6 i.MX 8M Quad rework for SDIO support on
M.2 ...................................................................183.5.7 AW-CM358MA module setup with iMX 8M
CM276MA module ...........................................223.6.1 Recommended antenna part ........................... 223.6.2 Supported RF standards ................................. 223.6.3 Supported Wi-Fi features .................................223.6.4 Supported Bluetooth features .......................... 224 i.MX 8M EVK Linux image setup ......................234.1 Using the pre-built image ................................ 234.2 Setting up the host .......................................... 254.2.1 Installing the host packages ............................ 254.2.2 Setting up Repo utility ..................................... 254.2.3 Setting up Yocto project ...................................264.3 Building the image ...........................................274.3.1 Build configurations ......................................... 274.3.2 Command to build an image ........................... 274.3.3 Image deployment ........................................... 274.4 Flashing the image to eMMC .......................... 28
4.5 Booting from eMMC ........................................ 294.5.1 Serial console setup ........................................ 294.5.2 Linux OS login .................................................294.5.3 Enabling SDIO on M.2 (AW-CM358MA
module only) .................................................... 294.5.4 Software package release version
information ....................................................... 295 Bring-up of Wi-Fi interfaces .............................305.1 Bring-up of 88W8987-based wireless
module (AW-CM358MA) ..................................305.2 Bring-up of 88W8997-based wireless
module (AW-CM276MA) ..................................335.3 Bring up the Wi-Fi interface .............................356 Bring-up of Bluetooth interfaces ..................... 367 Contact information .......................................... 378 Acronyms and abbreviations ...........................389 Legal information ..............................................39
Please be aware that important notices concerning this document and the product(s)described herein, have been included in section 'Legal information'.