Multi Source Translation Content

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Multi Source Translation Content

讨论

排序依据:
APF-HMB-T2467 - Wireless Charging Outline current wireless charging market situation and the trend. Outline current wireless charging market situation and the trend.
查看全文
EUF-NET-T2471 - Layerscape Update Do you plan to secure your data transmission keeping high data throughput, low power and CPU load? Layerscape family is your best choice. Do you plan to secure your data transmission keeping high data throughput, low power and CPU load? Layerscape family is your best choice.
查看全文
DES-N1916 I2C 总线缓冲器的来龙去脉 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> I2C总线的应用已从20世纪80年代蹩脚的家电扩展至现代世界的大小型系统。 应用范围涵盖智能手机和服务器场,对于需要其它I2C总线组件扩大、调整或缓冲那些信号的原始简易信令协议就是如此。 我们来深入了解一下简易总线缓冲器的技术。 经常被需要,很少被了解。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> I2C总线的应用已从20世纪80年代蹩脚的家电扩展至现代世界的大小型系统。 应用范围涵盖智能手机和服务器场,对于需要其它I2C总线组件扩大、调整或缓冲那些信号的原始简易信令协议就是如此。 我们来深入了解一下简易总线缓冲器的技术。 经常被需要,很少被了解。 观看视频演示 设计 | 软件与服务
查看全文
NET-N1863 QorIQ 的下一步发展方向 - 产品组合和路线图 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 快来了解 QorIQ 多核处理器平台的下一步发展。您将获得有关我们的网络解决方案的最新详细信息,包括有关我们解决方案重点的市场更新。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 快来了解 QorIQ 多核处理器平台的下一步发展。您将获得有关我们的网络解决方案的最新详细信息,包括有关我们解决方案重点的市场更新。 智能网络
查看全文
HMB-N1903 NFCおよびBluetooth Low Energyスマートデバイスとのトータル相互運用性 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ホスピタリティ業界、ホームリーダー、またはスマートフォンやタブレットに接続するアプリケーションの分野で活躍するお客様は、現在市場に出回っているすべてのスマートフォンとのシステムの相互運用性を保証するという課題に直面しています。その答えは、NFCおよびBLEターンキーソリューション、つまりPN7462およびQN902x Bluetooth 4.0 Low Energyファミリに基づくNXPのNFC/BLEリファレンスデザイン(OM27462NBR)として提供されます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ホスピタリティ業界、ホームリーダー、またはスマートフォンやタブレットに接続するアプリケーションの分野で活躍するお客様は、現在市場に出回っているすべてのスマートフォンとのシステムの相互運用性を保証するという課題に直面しています。その答えは、NFCおよびBLEターンキーソリューション、つまりPN7462およびQN902x Bluetooth 4.0 Low Energyファミリに基づくNXPのNFC/BLEリファレンスデザイン(OM27462NBR)として提供されます。 スマートホーム&ビル
查看全文
Example MPC5777C-PinToggleStationery GHS714 ******************************************************************************** * Detailed Description: * Application performs basic initialization, initializes interrupts, blinking * one LED by Core0, second by Core1 (by interrupt), initializes and display * notice via UART terminal and then terminal ECHO. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  ETPUA30 (PortP P23-15) --> USER_LED_1 (P7-1) *                  ETPUA31 (PortP P23-14) --> USER_LED_2 (P7-2) * ******************************************************************************** ******************************************************************************** * Detailed Description: * Application performs basic initialization, initializes interrupts, blinking * one LED by Core0, second by Core1 (by interrupt), initializes and display * notice via UART terminal and then terminal ECHO. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  ETPUA30 (PortP P23-15) --> USER_LED_1 (P7-1) *                  ETPUA31 (PortP P23-14) --> USER_LED_2 (P7-2) * ******************************************************************************** General Re: Example MPC5777C-PinToggleStationery GHS714 It is configured at the very beginning in the file init.s, comments say # configure PLL0 to 192MHz (40MHz XOSC reference) # configure PLL1 to 264MHz (48MHz PLL0 PHI1 output reference) Re: Example MPC5777C-PinToggleStationery GHS714 Hi, Thanks for this example,could you help me about the clock source to the PIT Timer . what is the out put clock friquency of phi and phi1. please help on . Thanks!
查看全文
カリフォルニア大学デービス校チーム The One テクニカルレポート <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
查看全文
示例 S32K311 SPI Sbc_fs23 MCAL S32DS3.5.8 RTD4.0.0 ***************************************************************************** *Detailed Description: *This example will show you how to configure Sbc_fs23 Driver. *It initialization of Sbc_fs23 with watchdog window disabled. The Sbc_fs23_InitDevice() must be done within the dedicated 256 ms INIT window. *It Disable regulator V2, then re-enable it again. FS0b pin is asserted due to V2 Undervoltage reaction setting configured in FailSafe Init Configuration tab. *If the example runs without errors, the D12 LED on S32K31XEVB-Q100 will light up Green; otherwise, it will light up Red. *The SPI data between FS23 and S32K311 are captured and attached to the project. *Use the analog input of a logic analyzer or an oscilloscope to monitor the signals of FS23_V2 (TP27) and FS23_FS0 (TP8) on the KITFS23SKTEVM board. *------------------------------------------------------------------------------ *Test HW: * S32K31XEVB-Q100 Board SCH-55131 REV A P32K311HV 0P98C * KITFS23SKTEVM Dev-kit SCH-53096 REV B2 MFS2320BMBB1EP * My S32K31XEVB-Q100 has an onboard PFS2320A0L1W1, but Step 13/14 of AN14041 mention that A0 devices are not supported, so S32K311 communicate with the FS23 on the KITFS23SKTEVM. *Connections: KITFS23SKTEVM | S32K31XEVB-Q100 ------------------------------|-------------------- SPI_CSB J28-2 | J12-5(PTB-17) SPI_MOSI J29-2 | J12-7(PTB-16) SPI_SCK J31-2 | J12-11(PTB-14) SPI_MISO J32-2 | J12.9(PTB-15) VCC J6-1 | J40-15 GND J6-2 | J40-13 - KITFS23SKTEVM: SW1 - position 2-3 , J30 - ON, J26 5-6 ON, J26 9-10 ON . - Connect KITFS23SKTEVM Dev-kit and S32K3 MCU via on-board Arduino headers. *SDK: * S32K3 RTD 4.0.0 (SW32K3_S32M27x_RTD_R21-11_4.0.0_D2311_DS_updatesite.zip) * FS23 RTD 1.0.0 (S32K3xx_SBC_FS23_R21-11_1.0.0_D2508_DesignStudio_updatesite.zip) *Debugger: S32DS 3.5.8, OpenSDA/ PEmicro Multilink Universal FX *Target: internal_FLASH *Reference Documentation: * AN14041 FS23 quick start guide (Rev. 2.0 — 23 January 2025) * AN14129 FS23 implementation and behaviors (Rev. 2.0 — 13 December 2024) * FS23, Safety System Basis Chip (SBC) with Power Management, CAN FD and LIN Transceivers Data Sheet (Rev. 8.0 — 30 June 2025) * RTD_SBC_FS23_UM.pdf C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32K3\SW32K3_FS23_R21-11_1.0.0_D2312\Sbc_fs23_TS_T40D34M10I0R0\doc * This example is migrated from Sbc_fs23_example_HLD_S32K344. The method of migrating refers to the video "2.S32DS CT MCAL demo porting K344 to K312 based on RTD500": https://community.nxp.com/t5/S32K-Knowledge-Base/S32K3-Tools-Part-How-to-port-RTD-s-existing-MCAL-demo-to-other/ta-p/1966315 ***************************************************************************** * Revision History: * Ver Date Author Description of Changes * 0.0 10-26-2025 Robin Shen Initial version * 0.1 11-21-2025 Robin Shen Upgrade FS23 RTD 1.0.0 from S32K3xx_SBC_FS23_R21-11_1.0.0_DS_updatesite_D2402_updated_D250115.zip to S32K3xx_SBC_FS23_R21-11_1.0.0_D2508_DesignStudio_updatesite.zip *****************************************************************************
查看全文
Enabling USB Device Mode in U-Boot on RDB3 for eMMC Boot Hi, Recently, several customers have inquired about how to program the eMMC on the RDB3 development board directly via USB in U-Boot. These customers are designing custom boards based on RDB3 without using an SD card or Ethernet, and therefore need a method to flash the eMMC through USB during the setup stage. By default, USB device mode is not enabled in U-Boot on RDB3. To achieve this functionality, it is necessary to modify the U-Boot and ATF (Arm Trusted Firmware) source code, as well as adjust the USB configuration to enable USB device support in U-Boot. In addition, the document provides guidance on testing the configuration, demonstrating how to use U-Boot commands to verify that the USB storage device is recognized, load the image from the USB into memory, and write it to the eMMC. In this article, I will share my experience using BSP42 to implement and test this feature. I hope this guide will be helpful to others who are looking to enable USB device in uboot for eMMC programming on RDB3. S32G
查看全文
IMX95EvkをPCIeエンドポイントとして設定し、PCIeエンドポイントテストフレームワークを使用してテストする方法 このブログでは、iMX95EVKをPCIeエンドポイントとして構成し、iMX8MMをRCとして使用してテストする方法について解説します。 ハードウェア・コンポーネント iMX95EVK iMX8MM PCIe M.2 Key Eブリッジ イーサネット接続     ソフトウェア・コンポーネント Linux Factory 6.12.20 BSP linux-imxソースコード(https://github.com/nxp-imx/linux-imx/tree/lf-6.12.20-2.0.0) システム・セットアップ ステップ1:iMX95EVKのeMMC/SDカードに6.12.20 BSPを書き込み、それで起動します。 ステップ2:GitHubからlinux-imx 6.12.20のソースコードを取得します。 GitHub - nxp-imx/linux-imx at lf-6.12.20-2.0.0 ステップ3:次のdiffに従って、arch/arm64/boot/dts/freescale/imx95-19x19-evk-pcie1-ep.dtsoに以下の変更を加えます。   diff --git a/arch/arm64/boot/dts/freescale/imx95-19x19-evk-pcie1-ep.dtso b/arch/arm64/boot/dts/freescale/imx95-19x19-evk-pcie1-ep.dtso インデックス a8e3bbc53894..d082688fc1c2 100644 --- a/arch/arm64/boot/dts/freescale/imx95-19x19-evk-pcie1-ep.dtso +++ b/arch/arm64/boot/dts/freescale/imx95-19x19-evk-pcie1-ep.dtso @@ -11,12 +11,12 @@ &smmu {  }; -&pcie1 { +&pcie0 {         status = "無効";  }; -&pcie1_ep { +&pcie0_ep {         pinctrl-names = "default"; - pinctrl-0 = <&pinctrl_pcie1>; + pinctrl-0 = <&pinctrl_pcie0>; status = "オーケー";  };   ご覧のとおり、ここではiMX95EVKのM.2 PCIe 0で「エンドポイント」モードを有効にしようとしています。デフォルトのdtbではPCIe 1に対して有効化されています。カーネルをビルドすると、dtsoの変更内容からこのdtbが生成されます。 ステップ4:dtbをボードにSCPで転送し、混乱を避けるために「imx95-19x19-evk-pcie0-ep.dtb」に名前を変更します。 ステップ5:U-Bootで「fdtfile」変数を変更し、このdtbを使ってボードを起動します。 このdtbでカーネルが起動すると、コンソールに次のようなPCIe dmesgログが表示され、変更が反映されたかを確認できます。 root@imx95evk:~# dmesg | grep pcie-ep [    3.142123] imx6q-pcie 4c300000.pcie-ep: iATU: アンロール T、8 ob、8 ib、アライン 4K、リミット 1024G [    3.151767] imx6q-pcie 4c300000.pcie-ep: eDMA: unroll T, 4 wr, 4 rd root@imx95evk:~# 0x4c300000は、pcie0コントローラのアドレスです ステップ6:このスクリプト「conf_pcie0_ep」をiMX95EVK上で実行します ステップ7:このdtb(imx8mm-evk.dtb)を使用してiMX8MMボードを起動します。 ステップ8:iMX8MM上で「lspci」を実行すると、以下の出力が表示されます。 これがiMX8MM RCのlspci出力に表示されているiMX95EVKエンドポイントです。   アドレス空間の変換ウィンドウは、以下に記載されている情報を使用して設定されます。 arch/arm64/boot/dts/freescale/imx8mm.dtsi PCIeノードの「ranges」プロパティとして記載されているアドレス変換ウィンドウの情報を理解したい場合は、「Demystifying the PCIe and CPU address space translation in Linux - NXP Community」の記事をご覧ください。ここでは、裏側で何が行われているのかが詳しく説明されています。       IMX95EVK
查看全文
i.MX 6ULZ:2秒未満でLinuxをブートする方法 この記事では、i.MX 6ULZにおいてLinuxのブート時間を2秒未満に短縮する方法について説明します。 ソフトウェア:Linux BSP 6.12.20-2.0.0 ブートデバイス:SDカード 添付のimx6ulz-fast-boot.tar.gz アーカイブには、i.MX 6ULZのブート時間を約1.9秒まで短縮するための一連のパッチが含まれています。アーカイブには以下のものが含まれています。 U-Bootパッチ: U-BootのBOOTDELAYを0に設定します。 CPU周波数を396 MHzから792 MHzに引き上げます。 ブート中のカーネル出力を抑制するために、カーネルのbootargsにquietを追加します。 カーネルパッチ: カーネルを削減して最小限のバージョンを作成します。 カーネルイメージにLZ4圧縮方式を使用します。 BusyBoxをベースにした最小のrootfs ハウツー 1. i.MX Yocto Projectユーザーズガイドのセクション3、4、5に従って、Yocto環境を準備します。バージョンは「6.12.20-2.0.0」です。他のバージョンでは、調整が必要な場合があります。 2. 作成したYocto環境のsourcesディレクトリで、「imx6ulz-fast-boot.tar.gz」アーカイブを解凍します。 cd ~/imx-yocto-bsp/sources tar -xvpzf imx6ulz-fast-boot.tar.gz -C . 3. 追加のマシン機能を削除します。以下の設定を「conf/local.conf」に追加します。 MACHINE_FEATURES:remove = "\ optee \ alsa \ touchscreen screen \ wifi bluetooth \ bcm4339 bcm43455 \ nxp8987-sdio nxpwifi-all-sdio \ rtc qemu-usermode" 4. イメージをビルドします。 bitbake core-image-busybox その結果、core-image-busybox-imx6ulz-14x14-evk.rootfs.wicは約38Mになるはずです。 5. イメージをSDカードに書き込み、ブートします。リセットからプロンプトが表示されるまで、2秒未満でブートするはずです。ボードのシリアルポートに接続している場合は、U-Bootを停止するために任意のキーを押し続けます。
查看全文
フラッシュから CodeWarrior for MCU ver11.x に基づくファイルにコードまたはデータをダンプします。 MCU用CodeWarrior ver11.xFlashコンテンツをファイルにコピーするための専用ツールを提供し、ドキュメントは手順を段階的に提供し、対応するスクリーンショットを提供して、ユーザーがタスクを簡単に完了できるようにします。 MCU用CodeWarrior ver11.xDSP56800E コアと DSP56800EX コアの DSC のみをサポートします。
查看全文
HCP - How to This page summarizes all Model-Based Design Toolbox topics related to the HCP Product Family. Model-Based Design Toolbox for HCP - Release Notes: Rev 1.3.0 - NXP Model-Based Design Toolbox for High-Performance Computing Platform (HCP) - version 1.3.0 RFP  Rev 1.2.0 - NXP Model-Based Design Toolbox for High-Performance Computing Platform (HCP) - version 1.2.0 RFP  Rev 1.1.0 - NXP Model-Based Design Toolbox for High-Performance Computing Platform (HCP) - version 1.1.0 RFP  Rev 1.0.0 - Model-Based Design Toolbox for High-Performance Computing Platform (HCP) - version 1.0.0 EAR 
查看全文
Kinetis KV3xマイクロコントローラ搭載Tower System TWR-KV31F120M <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> デモオーナー: Gregory Camuzat   Kinetis KV3xマイクロコントローラを搭載したTWR-KV31F120M Tower Systemの概要について説明します。 このデモでは、PMSMセンサレスFOCアルゴリズムを使用して三相モーターを回転させる方法と、KV3 Tower Systemボードを使用してWindows PC上で回転スピードを制御する方法をご紹介します。       顔立ち Kinetis KV3xマイクロコントローラを搭載したTWR-KV31F120M Tower Systemの概要について説明します。 このデモでは、PMSM Sensorless FOC 制御アルゴリズムを使用して低電圧 3 相モータを回転させる方法と、KV3 Tower System ボードと Windows PC を使用してその速度を制御する方法を示します 注目のNXP製品 製品 リンク Kinetis® KV3xファミリTower® Systemモジュール TWR-KV31F120M|Tower Systemボード|Kinetis®マイクロコントローラ |NXPの  FreeMASTERランタイム・デバッグ・ツール https://www.nxp.com/design/software/development-software/freemaster-run-time-debugging-tool:FREEMASTER?&tid=vanFREEMASTER リンクス PEMicro Windows USBドライバ IAR Embedded Workbench for ARM   インダストリアル
查看全文
[802.11] Wi-Fi Basic concepts Different 802.11 standards are used in Wi-Fi and they differ in terms of operating frequency and data rates. This post provides information about the different terms used in Wi-Fi, 802.11 standards and the three types of 802.11 MAC frames. Wi-Fi Standard basic terms Station (STA): Stations comprise of all devices that are connected to the wireless LAN. Station is any device that contains 802.11-compliant MAC and PHY interface to the wireless medium. A station may be a laptop, desktop PC, Access Point (AP) or smartphone. A station may be fixed, mobile or portable. Access Point (AP): An access point is a device that creates a wireless local area network. It has station functionality and provides access to the distribution services via the wireless medium. An access point is a device that allows Wi-Fi clients and Wi-Fi enabled routers to connect to a wired network. Access point connects to a wired router, switch or hub via an Ethernet cable and projects Wi-Fi signal to the defined area. An access point receives data by wired Ethernet, and converts to a 2.4GHz or 5GHz wireless signal. It communicates with nearby wireless clients. In a Wi-Fi network, wireless client communicate to other wireless clients via the AP. Client: A device that connects to a Wi-Fi (wireless) network. Any device that transmits and receives Wi-Fi signals, such as a laptop, printer, smartphone is a Wi-Fi client. Basic Service Set (BSS): A group of stations that are successfully synchronized for 802.11 communications. BSS contains one AP and one or more client stations. In BSS, stations have layer 2 connection with AP and are known as associated. Basic Service Set Identifier (BSSID): All basic service sets can be identified by a 48-bit (6-octet) MAC address known as the Basic Service Set Identifier (BSSID). The BSSID address is the layer 2 identifier of each individual basic service set. Most often the BSSID address is the MAC address of the access point. Distribution System (DS): A system that interconnects a set of basic service sets and integrated Local Area Networks (LANs) to create an Extended Service Set (ESS). It is used to extend wireless network coverage. Extended Service Set (ESS): In extended service set, one or more basic service sets are connected. An extended service set is a collection of multiple access points and their associated clients. Independent Basic Service Set (IBSS): An IBSS consists only of client stations that do peer-to-peer communications. An IBSS is a self-contained network that does not have an access point. SSID/ESSID: The logical network name of an Extended Service Set (ESS) is often called a Service Set Identifier (SSID). This name allows stations to connect to the desired network when multiple independent networks operate in the same physical area. Roaming: It is a process of a client moving from one access point to another access point within the same Extended Service Set (ESS) without losing connection. It is described in detail in 802.11 connection disconnection process post: [802.11] Wi-Fi Connection/Disconnection process . Below figure shows DS, AP, Station, BSS, SSID, BSSID and ESS. Figure 1. Overview of Distribution system 802.11 Standards / Wi-Fi Generations 802.11 standard defines an over the air communication interface between the wireless base station and clients. The 802.11 family has various specifications and it has been categorized in several versions as shown in table below. Details of Wi-Fi generations with 802.11 specifications Table 1. Wi-Fi Generation Overview Generation Technology Operating Frequency Data rates - 802.11b 2.4 GHz 1 - 11 Mbps - 802.11a 5 GHz Up to 54 Mbps - 802.11g 2.4 GHz Up to 54 Mbps Wi-Fi 4 802.11n 2.4 and 5 GHz Up to 600 Mbps Wi-Fi 5 802.11ac 2.4 and 5 GHz Up to 3.5 Gbps Wi-Fi 6 802.11ax 2.4 and 5 GHz Up to 9.6 Gbps   802.11b: This technology is focused on achieving higher data rates within the 2.4GHz ISM band and that is achieved by using a different spreading/coding technique called Complementary Code Keying (CCK) and modulation methods using the phase properties of the RF signal. 802.11b devices support data rates of 1, 2, 5.5 and 11 Mbps. 802.11a: This technology uses 5GHz frequency band. It supports data rate up to 54Mbps with the use of a spread spectrum technology called Orthogonal Frequency Division Multiplexing (OFDM). 802.11a can coexist in the same physical space with 802.11b and 802.11g devices as these devices are using different frequency ranges (5GHz and 2.4GHz respectively). 802.11g: This Technology is an enhancement of 802.11b Physical layer to achieve the greater bandwidth yet remain compatible with 802.11 MAC. The technology that was originally defined by the 802.11g amendment is called Extended Rate Physical (ERP), So the term ERP can be used in the place of 802.11g. Data rate differs with different 802.11g PHY technology, there are two mandatory ERP PHYs and two optional ERP PHYs. The First mandatory PHY technology called Extended Rate Physical-OFDM (ERP-OFDM) is used to achieve data rate up to 54Mbps. Second mandatory PHY technology called Extended Rate Physical DSSS (ERP-DSSS/CCK) is used to maintain backward compatibility and achieve data rate up to 11Mbps. ERP-PBCC and DSSS-OFDM are the two optional PHYs. ERP-PBCC PHY offers same data rates as the ERP-DSSS/CCK physical layer. It is used to provide higher performance in the range (the 5.5 and 11 Mbps rates) by using DSSS technology with Packet Binary Convolution Code (PBCC) scheme. DSSS-OFDM PHY is a hybrid combination of DSSS and OFDM. The transmission of packet physical header is done by DSSS, whereas the transmission of packet payload is performed by OFDM. Usage of this physical layer is to cover interoperability aspects. 802.11n: This Technology is an improvement of the 802.11 standard to get the higher throughput. 802.11n has a new operation known as High Throughput (HT) which provides MAC and PHY enhancements to provide data rates up to 600Mbps. 802.11n supports Multiple-Input Multiple-Output (MIMO) technology in unison with OFDM technology. MIMO uses multiple radios and transmitting and receiving antennas called radio chains. It capitalizes on the effects of multipath as opposed to compensating for or eliminating them. Transmit Beamforming can be used in MIMO system to steer beams & provide greater range & throughput. 802.11ac: Wi-Fi certified 802.11ac devices are dual band, operating in both 2.4 GHz and 5 GHz. 802.11ac is built on the foundation of 802.11n. 802.11ac devices use the 5 GHz band, while 802.11n products use the 2.4 GHz frequency band, so 802.11b and 802.11g compatibility can be achieved with 802.11ac. 802.11ac provides high-performance through Multi-User Multiple Input Multiple Output (multi-user MIMO), wider channels, and support for four spatial streams. 802.11ax: Wi-Fi certified 802.11ax provides improved data rates, power efficiency and support for eight spatial streams. Target Wake Time (TWT) feature helps to improve battery performance.   802.11 Frame types 802.11 frames are used for wireless communication and is much more involved because the wireless medium requires several management features and corresponding frame types that are not found in wired networks. There are three major frame types that are discussed below. For details regarding 802.11 layer architecture, please refer to [802.x.x] IEEE 802.x.x and Wi-Fi basics. Management Frames Management frames are used by wireless stations to join and leave the basic service set. 802.11 management frame is also called Management MAC Protocol Data Unit (MMPDU). It has a MAC header, a frame body, and a trailer. It doesn’t carry any upper layer information. There is no MAC Service Data Unit (MSDU) encapsulated in the MMPDU frame body, it carries only layer 2 information fields and information elements, it does not carry higher layer (Layer 3 to 7 of OSI model) data. A management frame must have fixed length information fields and it may have information elements that are variable in length. Management/MMPDU frame body content depends on the sub type field, based on the sub type field it has payload like Status/Reason code, device capability information etc. Few of the management frames i.e. Beacon, Authentication, Association are described in the Connection setup process post [802.11] Wi-Fi Connection/Disconnection process. Below figure shows management frame structure. Figure 2. Management Frame structure Type field available in frame control field, that is set to 00 for the management frame. Management frames have 24-bytes long MAC header and header contains three addresses. DA field is the destination address of the frame, it can be broadcast or unicast depending upon frame subtype. SA field is MAC address of the station transmitting the frame. BSSID is MAC address of AP. Frame body is variable size. Size and content of the body depend on the management frame subtype. Figure 3. Management Frame   Table 2. Management Frame description Frame SubType SubType Value [B7 B6 B5 B4] Initiator (AP/Station) Association request 0 Station Association response 1 AP Reassociation request 10 Station Reassociation response 11 AP Probe request 100 Station Probe response 101 AP/Station Beacon 1000 AP Announcement Traffic Indication Message (ATIM) 1001 Station (IBSS) Disassociation 1010 AP Authentication 1011 Station Deauthentication 1100 AP/Station Action 1101 AP/Station Action no ack 1110 AP/Station Control Frames Control frames are associated with the delivery of data and management frames, it does not have a frame body. Control frames contain PHY, preamble, layer 2 header and trailer. Control frames can be transmitted at different data rates as they perform many different functions. All control frames use the same Frame Control field that is shown in the figure below. Figure 4. Control Frame structure   Figure 5. Control Frame   The type field value for the control frame is 01 and subtype fields identify the function of a frame. Table below shows the different types of control frames.   Table 3. Control Frame description Subtype description Subtype value [B7 B6 B5 B4] Reserved 0000 - 0110 Control wrapper 0111 Block ack request (BlockAckReq) 1000 Block ack (BlockAck) 1001 PS-Poll 1010 RTS 1011 CTS 1100 ACK 1101 CF-End 1110 CF-End and CF-Ack 1111 Data Frames Data frames carry the higher level protocol data in the frame body. Data frames are categorized according to function. Total 15 sub types of data frames are defined in 802.11 standard. Type field value for the data frames is 10. One such distinction is between frame that carries data and frame that does not carry data (perform management function). Figure below shows data frame structure. Figure 6. Data Frame structure   Figure 7. Data Frame Each bit of the SubType field available in the frame control field has specific meaning as below. Bit 4 (B4): Changing it from 0 to 1 indicates the data subtype includes +CF-Ack. Bit 5 (B5): Changing it from 0 to 1 indicates the data sub type include +CF-Poll. Bit 6 (B6): Changing it from 0 to 1 indicates that the frame contains no data, specifically, that it contains no Frame Body field. Bit 7 (B7): Changing it from 0 to 1 indicates Quality of Service (QoS) data frame. Data frames that appear only in the contention-free period can never be used in an IBSS. Below is the list of data frames. Table 4.Data Frame Details Frame SubType SubType Value B7 B6 B5 B4 Consists Data Contention Free Service Data (simple data frame) 0 Yes No Data + CF-Ack 1 Yes Yes Data + CF-Poll 10 Yes Yes(AP only) Data + CF-Ack + CF-Poll 11 Yes Yes(AP only) Null 100 No It can be contention based and free both CF-Ack 101 No Yes CF-Poll 110 No Yes(AP only) CF-Ack + CF-Poll 111 No Yes(AP only) QoS Data 1000 Yes No QoS Data + CF-Ack 1001 Yes Yes QoS Data + CF-Poll 1010 Yes Yes(AP only) QoS Data + CF-Ack + CF-Poll 1011 Yes Yes(AP only) Qos Null 1100 No It can be contention based and free both QoS CF-Poll 1110 No Yes(AP only) QoS CF-Ack + CF-Poll 1111 No Yes(AP only) References 802.11 Specification: https://ieeexplore.ieee.org/document/7786995 Certified Wireless Analysis Professional: https://www.oreilly.com/library/view/cwap-certified-wireless/9781118075234/ Community posts [802.x.x] IEEE 802.x.x and Wi-Fi basics   [802.11] Wi-Fi Connection/Disconnection process
查看全文
パスワード保護下での NDEF メッセージの読み取り <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このビデオでは、パスワード保護の下でNDEFメッセージを読み取る方法を示します。詳細については、以下をご覧ください https://community.nxp.com/docs/DOC-347622  (マイビデオで視聴)
查看全文
MCUXPresso IDE SWO 跟踪功能 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MCUXpresso IDE SWO 跟踪功能是一项特殊功能,它使用户能够观察变量更新、中断进入/退出时序、中断事件统计,并在 MCU 运行时在 SWO ITM 控制台中打印信息。MCUXpresso IDE SWO 跟踪功能是对 MCUXpresso IDE 调试器的补充。主要优点是在 MCU 运行时显示变量、打印信息、列出中断进入/退出/返回。  文档介绍了实现SWO功能的硬件连接、MCUXpresso配置以及实现该功能的源代码。
查看全文
APF-SNT-T1358 - 南京、深圳 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍全新的 QorIQ LS1 系列,这是 QorIQ LS 系列中第一个基于双 ARM ® Cortex ® -A7 内核的设备系列。您将收到 LS1 处理器的概述——优势、差异化以及网络和工业应用的功能。主讲人:尤鹏 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍全新的 QorIQ LS1 系列,这是 QorIQ LS 系列中第一个基于双 ARM ® Cortex ® -A7 内核的设备系列。您将收到 LS1 处理器的概述——优势、差异化以及网络和工业应用的功能。主讲人:尤鹏
查看全文
禁用 i.MX6 的 SD 时钟门控 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 一些 SDIO 卡需要 SD 时钟在 4 位模式下有效,以便产生中断。 但是 i.MX6 SD 控制器默认启用 SD 时钟门控,附加的补丁是禁用 SD 时钟门控的示例。 可以通过 SD 控制器的寄存器“uSDHCx_PRES_STATE:SDOFF”检查时钟门控是否启用。 i.MX6_全部
查看全文
フリースケール・カップ2013 EMEAチャンピオンのご紹介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> リチャード・バロー教授と彼の学生たちが、フリースケール・カップの課題をどのように克服し、今年3月に2013年のEMEAタイトルを獲得したかを説明します。 ブラチスラバのスロバキア工科大学のFEI-Minetorsチームは、この夏、中国のハルビンで開催されたフリースケールカップ・ワールドワイド・チャレンジにも参加しました。 イベントのスケジュールについては、フリースケールのGoogle+ページ(https://www.google.com/+freescale)をご覧ください
查看全文