Question:
Hello,
I am working on the i.MX8ULP-9X9-LPDDR4-EVK and have successfully created and deployed a Matter Accessory on the board. Here is what I have done so far:
Built the imx-image-core using Yocto for the i.MX8ULP-9X9-LPDDR4-EVK.
Created a Matter Accessory binary and transferred it to the board using scp.
https://www.nxp.com/docs/en/user-guide/GSG-IMX8MMINI-MATTER.pdf
Successfully established communication with the Matter Accessory using the chip-tool Matter controller from x86.
Now, I want to move forward with enabling multi-protocol support in a single binary.
Goal:
Create a single Matter Accessory binary that supports multiple protocols — BLE, Zigbee, Thread, and Wi-Fi. At runtime, I want to be able to select a specific protocol or end device through a command-line argument or configuration — for example:
Run the binary as a BLE-based Matter accessory,
Or as a Thread-based device,
Or Zigbee, etc.
Questions:
Is it possible to compile and include all four protocol stacks (BLE, Thread, Zigbee, Wi-Fi) into one Matter Accessory binary for i.MX8ULP?
If yes, how should I structure the Matter application and the build system (Yocto or GN) to support this?
How can the runtime protocol selection be implemented cleanly (e.g., via CLI or config)?
Are there known limitations on the i.MX8ULP platform related to RAM, flash, or stack coexistence that could impact this?
Are there any reference examples or documentation that show how to implement this kind of multi-protocol Matter accessory on NXP SoCs?
Any guidance, tips, or links to reference implementations would be very helpful.
Thank you!
