- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2136570_en-US
2136570_en-US
- RSS フィードを購読する
- 新着としてマーク
- 既読としてマーク
- ブックマーク
- 購読
- 印刷用ページ
- 不適切なコンテンツを報告
2136570_en-US
2136570_en-US
Hi,
We are trying to get started with openthread using an IW610G module but having some troubles during the initial SPI communication.
How do I know if the firmware is compatible with 802.15.4? We are using the latets binary (sduartspi_iw610.bin.se, ver: SDIW610---18.99.5.p61-MM6X18505.p7.1-(FP92)) from the nxp-imx/imx-firmware github.
Is there something more that must be done while building ot-daemon than adding the build options? (-DOT_APP_RCP=ON, -DOT_RCP=ON, -DOT_TRANSPORT=spi, -DOT_POSIX_RCP_SPI=ON, DOT_POSIX_RCP_SPI_BUS=ON)
I have attached the system log and a logic analyzer capture of the SPI signals.
Any help is much appreciated,
Cheers!
Hi,
More information about the SW for Wireless can be found here: Linux Software Reference Manual for NXP Wireless Connectivity
Hope this helps!
Regards,
Ricardo
Hi Ricardo,
Thank you for your reply.
I can see from the document RN00104 that iw610 is running FP99. It confuses me however that the feature pack is defined by the second version section, i.e. "99" in 18.99.5.p61, while my driver is outputting "wlan: version = SDIW610---18.99.5.p21-MM6X18505.p7.1-(FP92)". What is "FP92" in this case?
What also confuses me is that the same firmware binary that I am using gives the output "wlan: version = SDIW610---18.99.5.p21-MX6X18475-(FP99)" on a developers kit provided by EmbeddedArtists, where 802.15.4 supposedly works (note the "FP99"). This leads me to think that the feature pack "FP92"/"FP99" is decided also by the linux driver (moal?)?
Hello,
Hope you are doing well. You can check the Feature Thread list for our different devices here: NXP Wireless SoC Features and Release Notes for Linux
You can check a description of the firmware's on this document: Getting Started with IW610 module on FRDM i.MX 91 development board running Linux OS. Also, I would recommend checking section 11, that is related 802.15.4.
Hope this helps.
Best Regards,
Ricardo