QM33120WDK2 custom Tag additional Firmware with Leaps System

Wireless Connectivity Ultra-Wideband
1

Hello Community,

I am working on a custom hardware design based on the Murata Type 2AB module, which functionally covers the core features of the QM33120WDK2 Developer Kit.

I also own the QM33120WDK2 hardware kit and successfully flashed the original developer kit firmware onto my custom board. The firmware runs correctly, and the device appears in the LEAPS Manager and remains fully manageable there.

Currently, I am using LEAPS-UWBS-Firmware v1.1.0.

My goal is to extend the existing firmware with custom functionality on the local API level, specifically to support additional SPI and I2C peripherals connected to my board.

This is where I am running into limitations:

  • The developer kit firmware is only available to me as a HEX/BIN image.
  • I have access to the LEAPS Git repositories and can build a fully custom software stack.
  • However, when building a custom firmware from the LEAPS Git sources, the device no longer appears in the LEAPS Manager and the LEAPS integration is lost.

What I am trying to achieve:

  • Develop custom firmware on top of the existing firmware stack
  • Add application-specific SPI/I2C functionality
  • While keeping full compatibility with LEAPS so that the device remains visible and manageable in the LEAPS Manager

My questions:

  1. Is there a supported way to extend or build upon the QM33120WDK2 firmware (e.g. via a local application layer) while preserving LEAPS Manager compatibility?
  2. Is there a reference workflow or example for adding custom functionality on custom hardware that is still recognized as a LEAPS device?
  3. Are there specific requirements (device descriptors, firmware structure, signing, versioning, etc.) that must be preserved to maintain LEAPS integration when building from the LEAPS Git sources?

Any guidance, documentation, or best practices would be highly appreciated.

Thank you very much.

Thorlak

2

Hello @ToTatz
the LEAPS demo firmware is proprietary and developed/owned by LEAPS company. The SW provided to QM33120WDK2 is demo firmware and it is not licensed to be used as End product. Also it came up 48Hrs up time limitation. It will automatically power off after this period. To make it work you just need to turn it on again.

To answer your questions:
re 1) No that is not supported.

re 2) You need to use external MCU to control the 2AB with LEAPS firmware and your peripherals. The 2AB acts here as Ready to go radio module - like WIFI.

re 3) The provided GIT repository contain only modified QORVO UWB examples for the Zephyr OS and adjusted for the purposes of the Demokit. There is no relation to the LEAPS SW stack.

If you want more information’s drop us a message here: https://www.leapslabs.com/about - scroll down to Get in touch form.

Cheers
JK