I want to use the QPG6095 SoC as a ZigBee communications controller.
Just the ZigBee controller stack - without the Matter stack.
I’d like to be able to flash this SoC with my own custom firmware, including a ZigBee controller stack.
To do this, I’m looking for the following:
The full technical reference - SoC registers, I/O map, programming information, etc.
An SDK, BSP or OS support library (RTOS, Linux, bare metal, etc.)
Do you want to implement a Zigbee coordinator role with QPG6095? We don’t have the SDK for QPG6095 for a controller role. Instead we have SDK for QPG6095 for various endnode applications e.g. Light, Switch, SmartPlug and Door/Window Sensor in the SDK.
Not all the register info are included, but peripheral (I/O map) registers/guide are included in the QPG6095 user manual.
Yes, I would like to implement Zigbee coordinator, or maybe a router.
I am considering splitting up the Zigbee stack between the QPG6095 a different Cortex-M4 based MCU, which will also run our own application.
I briefly looked through the Qorvo github repository and I saw the QMatter and QGateway repos, but I didn’t see the endnode applications or documentation for the QPG6095.
Where can I download the QPG6095 SDK and user manual?
Have you also looked at our QPG7015M?
The QPG7015M is our go-to platform for Zigbee coordinators. It is platform certified and is even given golden unit status for both Zigbee Pro 2023 and Zigbee Direct.
In addition to Zigbee, it also supports Thread/Matter (Thread Border Router for Matter) and Bluetooth Low Energy concurrently using Qorvo’s ConcurrentConnect Technology.
If you want to learn more about this part, please reach out to a Qorvo sales person using the QPG7015M Product Page on our website to request a development kit for this platform.
We had a meet with your engineering team on the QPG6095 ZC. I explained both platforms (QPG6095 & QPG7015M) and their architectural differences. Please schedule a call to discuss further.
Just so you are aware, I have met with both Brian and Ben. They asked me to follow-up with Qorvo. They have higher engineering priorities that preempt the QPG6095 project. Also, Ben gave me the QPG6106DK to work with, as well.
And Brian let me know that the QPG6105 is Qorvo’s preferred platform going forward.
At this point, I have evaluated the QPG6105 and am impressed with it. However, it remains necessary that I also evaluate the QPG6095 in order to report my findings and recommendations. And without the development tools to the evaluate QPG6095, I am unable to finalize my report.