Building on Qorvo silicon? We're the team that builds Qorvo's SDK

Q: Can needCode develop firmware on Qorvo QM33 and QM35?

Yes - QM33 and QM35 are needCode's home silicon: we're a certified Qorvo partner with 9 hardware-platform bring-ups, and we build the QM35 SDK that Qorvo publishes on GitLab. Engagements span custom board bring-up, SDK and application firmware, FiRa and CCC session stacks, and complete positioning systems on QM33-based hardware. There is no shorter path to this silicon than the team that writes its SDK.

Q: Do you support legacy Decawave DW1000 and DW3000 designs?

Yes - needCode supports the Decawave-heritage DW1000 and DW3000 parts still shipping in deployed products, and runs the migration path to current-generation QM33/QM35 silicon without breaking what's in the field. Migration covers firmware porting, ranging-behaviour validation against the legacy system, and a staged rollout plan. Legacy depth is chipset knowledge paying twice.

Q: Can you bring up our custom board built on Qorvo UWB silicon?

Yes - custom board bring-up is a core engagement: clocks, power domains, RF layout review, antenna integration, and getting first ranging on your hardware, backed by nine consecutive Qorvo platform bring-ups. We also design custom hardware ourselves - miniaturised QM33-based tags and PoE anchors - so the review comes from a team that ships boards, not just firmware.

Q: Can you take a Qorvo-based product through FiRa or CCC certification?

Yes - needCode implements FiRa and CCC Digital Key session stacks on Qorvo silicon and supports the certification path through pre-certification testing and conformity preparation, as an active FiRa contributor with interoperability test events on two continents. Certification is handled with our Standards & Certification service; this page's depth is what makes the stack certifiable in the first place.

Q: Does needCode work with Qorvo's multi-protocol connectivity SoCs?

Yes - beyond UWB, needCode has shipped product firmware on Qorvo connectivity SoCs with ConcurrentConnect™ technology, including a dual-protocol BLE + Zigbee remote control documented in a public case study. That platform story extends naturally to Matter-era devices. Multi-protocol coexistence is a dedicated needCode competence, not a side effect.

Q: How do you debug UWB problems on Qorvo silicon?

With our own instrument: needCode's UWB Protocol Sniffer was developed and tested against Qorvo silicon across all nine bring-ups, capturing and dissecting live 802.15.4a/z traffic with FiRa and CCC decoders. When ranging misbehaves, we see the frames instead of guessing from device logs. No silicon vendor ships an equivalent tool.

Q: How fast can a Qorvo project start delivering?

Faster than chipset-new teams, because the learning curve is already behind us: a feasibility consultation delivers measured results on real silicon in 2-4 weeks, and bring-up or firmware engagements start from working knowledge of the errata, timing corners, and reference-design gaps. The months teams normally spend discovering a chipset's unpublished behaviour are the months this partnership saves.

Q: Should we choose QM33/QM35, or migrate from DW3000 now?

It depends on your product's ranging requirements, AoA needs, certification targets, and field-installed base - which is why the honest answer is a measured feasibility assessment rather than a blanket recommendation. As the team building on both generations daily, needCode advises from hardware results, and a staged migration often beats both extremes. The 2-4 week consultation exists exactly for this decision.

Q: Do you also work on non-Qorvo UWB and wireless silicon?

Yes - needCode works across UWB and wireless silicon per engagement, and chipset pages for other vendors are part of this cluster. The Qorvo relationship is our deepest and it's publicly documented, but engagements are scoped to your product's silicon, not to our partnerships. If you're mid-selection, the feasibility consultation compares candidates on measured behaviour.

needCode is a certified Qorvo partner with 30+ engineers embedded in Qorvo R&D across Belgium, France, and Ireland for 8 years - 9 hardware-platform bring-ups, the public QM35 SDK, and our own UWB protocol sniffer tested against the silicon. Whether you're shipping on QM33 or QM35, migrating from legacy DW1000/DW3000, or building multi-protocol products on Qorvo's connectivity SoCs, your project starts where other teams hope to end up: inside the chipset.

Book a discovery call

The Qorvo silicon we work on

We work with Industry Leaders

Chipset knowledge doesn't come from the datasheet. It comes from years inside it

Every chipset has two documents: the datasheet, and the one nobody publishes - the errata you learn by hitting them, the timing corners that only appear under real radio traffic, the configuration that works in the reference design and fails in yours. Teams new to a chipset pay for that second document in months of schedule; the first ranging demo takes a week, and the next quarter goes to everything the datasheet didn't say.

On Qorvo silicon, needCode already paid that cost - nine platform bring-ups deep, across an 8-year partnership working inside Qorvo R&D itself. We build the QM35 SDK that's public on GitLab, we've shipped products on Qorvo's multi-protocol connectivity SoCs, and when something on the air looks wrong, we capture it with our own UWB sniffer instead of guessing. That's what "one step from the source" means in practice: your questions land somewhere they've usually been answered before.

Inside the silicon

8 years embedded in Qorvo R&D, 9 platform bring-ups - the unpublished errata document, already read.

Publicly verifiable

The QM35 SDK we build for Qorvo is on GitLab - clone the proof before you book the call.

Instrumented

Our own UWB protocol sniffer, developed against Qorvo silicon - when ranging misbehaves, we see why.

The Qorvo silicon we work on

From the current UWB flagships to the legacy parts still shipping in the field - and the multi-protocol SoCs beyond UWB.

QM33 Series

Qorvo's current UWB ranging and AoA platform - the family behind digital key, secure ranging, and precision RTLS designs, including custom tag and anchor hardware we've built on QM33 integration. If your product is being designed on QM33 today, this is the silicon our benches run daily.

Digital Keys & Access

Indoor Positioning (RTLS)

QM35 Series

The platform whose SDK needCode builds and maintains publicly - drivers, ranging stack, examples, and release machinery, visible on GitLab. There is no shorter path to QM35 competence than the team that writes its SDK.

UWB SDK Development

Legacy DW1000 / DW3000

The Decawave-heritage parts still carrying thousands of deployed RTLS and ranging products - we support them, and we run the migration path to current-generation silicon without breaking what's in the field. Legacy support and migration is where chipset depth pays twice.

UWB RTLS Design & Deployment

Multi-Protocol Connectivity SoCs

Beyond UWB: Qorvo's connectivity SoCs with ConcurrentConnect™ technology for simultaneous protocol operation - the silicon behind our shipped dual-protocol BLE + Zigbee product work, and the platform story for Matter-era devices.

Multi-Protocol / Coexistence

Remote control

Not sure which silicon to choose?

Book a discovery call with our CEO

Book a discovery call

What we build on Qorvo silicon

The full stack of engagements, all of them already exercised on this exact silicon.

Board Bring-Up & Custom Hardware

Getting your custom Qorvo-based board to boot, range, and behave - clocks, power, RF layout review, and antenna integration for tags and anchors - from a team that has done it nine platforms in a row.

Platform Bring-Up & SDK

SDKs & Application Firmware

From the SDK layer (drivers, ranging stacks, FiRa/CCC sessions) to the application firmware your product ships - the same four-layer discipline behind the public QM35 SDK, applied to your codebase.

UWB SDK Development

Positioning Systems End to End

Complete RTLS on Qorvo silicon - custom QM33-based tags and PoE anchors, ranging algorithms, sensor fusion, deployment, and integration with the systems that run your operation.

Indoor Positioning (RTLS)

UWB RTLS Design & Deployment

Test, Debug & Certification

Protocol-level debugging with our own UWB sniffer, automated test batteries on real Qorvo boards, and the FiRa/CCC certification path - run by a team that attends the interop test events where the spec meets reality.

UWB Sniffer

Standards & Certification

One step from the source

The team that builds the vendor's SDK

The QM35 SDK is needCode's work, public on GitLab - which means the API conventions, the ranging stack behaviour, and the release discipline you'll build on are ones we wrote.

Eight years inside Qorvo R&D

30+ engineers embedded across Belgium, France, and Ireland - proximity that shows up as answered questions, familiar errata, and a network inside the vendor when something genuinely new appears.

Certified, not self-described

A certified Qorvo partner and UWB Alliance member, active in FiRa with interop test events on two continents - the relationship is on Qorvo's record, not just our website.

Instruments the vendor doesn't ship

Our UWB protocol sniffer was developed and tested against Qorvo silicon across all nine bring-ups - on a Qorvo project, protocol-level visibility isn't a wish, it's on the bench.

Four ways to bring needCode in

From a chipset-level question to a standing team. We match the engagement to where your Qorvo project is.

01 Feasibility & Chipset Consultation

Duration:
2-4 weeks
Best for:
Validating that QM33/QM35 (or a migration from DW1000/DW3000) fits your product - measured on hardware, not promised from the datasheet
Deliverable:
Feasibility assessment on real silicon, architecture recommendation, migration path if applicable, leadership readout

02 Bring-Up & Firmware Build

Duration:
Phased
Best for:
Custom board bring-up and the SDK/application firmware your product ships on
Deliverable:
Working firmware on your hardware, test harness, documentation, release ownership

03 System Delivery

Duration:
Phased
Best for:
Complete positioning or digital-key systems on Qorvo silicon - hardware, firmware, deployment, integration
Deliverable:
A deployed, validated system with handover

04 Embedded Team

Duration:
Multi-year, retainer-based
Best for:
Companies that want standing Qorvo-silicon depth inside their programme
Deliverable:
An embedded team in your cadence - the model that has run inside Qorvo itself for 8 years

What we ship on

The Qorvo stack, end to end - silicon to standards to instruments

Silicon

QM33 series

QM35 series

legacy DW1000 / DW3000

Qorvo multi-protocol connectivity SoCs

Standards

IEEE 802.15.4z / 4ab

FiRa

CCC Digital Key

Aliro

omlox

Zigbee / Matter

Ranging

DS-TWR / SS-TWR

TDoA (UL/DL)

AoA

dynamic STS

multi-anchor sessions

RTOS & platforms

Zephyr

FreeRTOS

ThreadX

bare-metal

Hardware

Custom QM33-based tags

PoE anchors

antenna integration

low-power design

Tooling

UWB Protocol Sniffer (in-house, Qorvo-proven)

board-matrix CI

HIL rigs

Wireshark dissectors

Case studies

On this page, the evidence isn't transferable-competence framing - it's direct.

Qorvo: RF Leadership

Context: Rapid scaling for new chipset bring-up.

Scale: Grew from <10 to 30 FTEs.
Output: Supported bring-up of 9 new hardware platforms (SDKs, Drivers, Stacks).
Retention: Zero-churn core team retained for 5+ years.

Dedicated Development Center for RF Solutions

Bluetooth Mesh Smart Lighting Control System

Smart Lighting: Core R&D Extension

Context: Client needed deep, specialized expertise to pivot from proprietary tech to a new global standard.

Service: Deployed a dedicated squad of embedded engineers to function as the client's core R&D team.
Output: Co-authored official Bluetooth SIG protocols and delivered the world’s first certified BLE Mesh stack.
Value: Enabled the client to secure Series A funding and defined the industry standard for smart buildings.

Creative Werks: Innovation rescue

Context: Hardware obsolescence threatened production shutdown.

Action: Full-stack takeover (PCB redesign + Firmware + Mobile App).
ROI: 1230% ($1.6M value generated).
Speed: Payback period of 2-3 months.

NeedCode-case study - IoT Solution for Boat Lift Modernization - cover2s

PowerPollen: AgTech automation

Context: Lack of internal expertise stalled a critical automation project.

Action: Re-architected system using unified MCU and ISOBUS standards.
ROI: 13.8x ($2.9M value generated).
Impact: Enabled $1.9M increase in harvester value.

Strategic Partnership

needCode is an official business partner of Qorvo, bringing over 8 years of proven expertise and trusted service to the technology sector.

Check our performance

Members of the UWB Alliance

In 2025 we became a member of the UWB Alliance. This strategic step reinforces our commitment to pioneering Ultra-Wideband (UWB) technology.

Proudly Certified for Excellence and Security

needCode is officially certified for:
ISO 9001:2015 – Quality Management
ISO/IEC 27001:2022 – Information Security

ISO certifications reflect our focus on delivering reliable IoT solutions, smart product development, and secure technology services.

Testimonials

“I think the key takeaway from needCode is their ability to adapt and understand the customer's requirements. That took away probably a large portion of what could have been a lot of development time and expense for both companies.”

Bob Folkestad

President at Creative Werks

“One aspect that truly sets needCode apart is its profound expertise in firmware development. Their proficiency in various programming languages, embedded systems and hardware architecture is truly impressive. When faced with difficult problems, their strong problem-solving skills and analytical mindset shine through, allowing them to overcome obstacles with remarkable ease.”

Semeh Sarhan

CEO at Xtrava

“I worked with needCode while leading the NWTN-Berlin team in 2018. A big chunk for our FW development has been outsourced to them and they had proven to iterate very quickly, following specs and deliver on time. It was great working with them. I recommend working with needCode’s team on any Embedded SW development.”

Marco Salvioli Mariani

CTO at NWTN Berlin GmbH

“needCode Team proved to be one of the best engineers I have ever met. The part I like the most about the team is the more difficult an obstacle seems to be, the more motivated they were to find a solution and a way forward.”

Szymon Słupik

CTO at Silvair

“needCode is an outstanding partner. Their quick follow-up, scalability, and extensive professional network set them apart. Their expertise in wireless technologies has been valuable, supporting us from low-level drivers to architecture discussions.”

Tim Allemeersch

Director at Qorvo, Inc.

“needCode did a great job improving the firmware of the Vai Kai connected toys and developing new features, surpassing our expectations multiple times. I would definitely recommend hiring Bartek and needCode for the embedded software projects!”

Matas Petrikas

CEO & Co-founder at Vai Kai UG

Insights

Basics of UWB indoor location systems (indoor RTLS)

Introduction to real-time location systems (RTLS) using ultra-wideband technology RTLS stands for Real Time Location System. As you may guess, such a system aims to provide real-time information about the location of “an object” with respect to “a coordinate system”. This loose definition raises three questions: – Provide information to whom? – What is “an […]

FAQ

Yes - QM33 and QM35 are needCode's home silicon: we're a certified Qorvo partner with 9 hardware-platform bring-ups, and we build the QM35 SDK that Qorvo publishes on GitLab. Engagements span custom board bring-up, SDK and application firmware, FiRa and CCC session stacks, and complete positioning systems on QM33-based hardware. There is no shorter path to this silicon than the team that writes its SDK.

Yes - needCode supports the Decawave-heritage DW1000 and DW3000 parts still shipping in deployed products, and runs the migration path to current-generation QM33/QM35 silicon without breaking what's in the field. Migration covers firmware porting, ranging-behaviour validation against the legacy system, and a staged rollout plan. Legacy depth is chipset knowledge paying twice.

needCode is a certified Qorvo partner with 30+ engineers embedded in Qorvo R&D across Belgium, France, and Ireland over an 8-year partnership - including 9 hardware-platform bring-ups and building the publicly available QM35 SDK. The relationship is documented in a public case study and on Qorvo's partner record. It means your Qorvo questions land somewhere they've usually been answered before.

Yes - custom board bring-up is a core engagement: clocks, power domains, RF layout review, antenna integration, and getting first ranging on your hardware, backed by nine consecutive Qorvo platform bring-ups. We also design custom hardware ourselves - miniaturised QM33-based tags and PoE anchors - so the review comes from a team that ships boards, not just firmware.

Yes - needCode implements FiRa and CCC Digital Key session stacks on Qorvo silicon and supports the certification path through pre-certification testing and conformity preparation, as an active FiRa contributor with interoperability test events on two continents. Certification is handled with our Standards & Certification service; this page's depth is what makes the stack certifiable in the first place.

Yes - beyond UWB, needCode has shipped product firmware on Qorvo connectivity SoCs with ConcurrentConnect™ technology, including a dual-protocol BLE + Zigbee remote control documented in a public case study. That platform story extends naturally to Matter-era devices. Multi-protocol coexistence is a dedicated needCode competence, not a side effect.

With our own instrument: needCode's UWB Protocol Sniffer was developed and tested against Qorvo silicon across all nine bring-ups, capturing and dissecting live 802.15.4a/z traffic with FiRa and CCC decoders. When ranging misbehaves, we see the frames instead of guessing from device logs. No silicon vendor ships an equivalent tool.

Faster than chipset-new teams, because the learning curve is already behind us: a feasibility consultation delivers measured results on real silicon in 2-4 weeks, and bring-up or firmware engagements start from working knowledge of the errata, timing corners, and reference-design gaps. The months teams normally spend discovering a chipset's unpublished behaviour are the months this partnership saves.

It depends on your product's ranging requirements, AoA needs, certification targets, and field-installed base - which is why the honest answer is a measured feasibility assessment rather than a blanket recommendation. As the team building on both generations daily, needCode advises from hardware results, and a staged migration often beats both extremes. The 2-4 week consultation exists exactly for this decision.

Yes - needCode works across UWB and wireless silicon per engagement, and chipset pages for other vendors are part of this cluster. The Qorvo relationship is our deepest and it's publicly documented, but engagements are scoped to your product's silicon, not to our partnerships. If you're mid-selection, the feasibility consultation compares candidates on measured behaviour.

Let's work on your next project together

Book a demo and discovery call with our CEO to get a look at:

Strategic Expertise

End-to-End Solutions

Advanced Technology

Custom Hardware Devices

Bartek Kling / CEO

Book a discovery call

Partnerships

Qorvo UWB Alliance Creative Werks

Resources

Blog E-books About

Case studies Contact

Building on Qorvo silicon? We're the team that builds Qorvo's SDK

We work with Industry Leaders

Chipset knowledge doesn't come from the datasheet. It comes from years inside it

Inside the silicon

Publicly verifiable

Instrumented

The Qorvo silicon we work on

QM33 Series

QM35 Series

Legacy DW1000 / DW3000

Multi-Protocol Connectivity SoCs

Not sure which silicon to choose?

What we build on Qorvo silicon

Board Bring-Up & Custom Hardware

SDKs & Application Firmware

Positioning Systems End to End

Test, Debug & Certification

One step from the source

The team that builds the vendor's SDK

Eight years inside Qorvo R&D

Certified, not self-described

Instruments the vendor doesn't ship

Four ways to bring needCode in

01

Feasibility & Chipset Consultation

02

Bring-Up & Firmware Build

03

System Delivery

04

Embedded Team

What we ship on

Silicon

Standards

Ranging

RTOS & platforms

Hardware

Tooling

Case studies

Qorvo: RF Leadership

Smart Lighting: Core R&D Extension

Creative Werks: Innovation rescue

PowerPollen: AgTech automation

Strategic Partnership

Members of the UWB Alliance

Proudly Certified for Excellence and Security

Testimonials

Insights

FAQ

Can needCode develop firmware on Qorvo QM33 and QM35?

Do you support legacy Decawave DW1000 and DW3000 designs?

What is needCode's relationship with Qorvo?

Can you bring up our custom board built on Qorvo UWB silicon?

Can you take a Qorvo-based product through FiRa or CCC certification?

Does needCode work with Qorvo's multi-protocol connectivity SoCs?

How do you debug UWB problems on Qorvo silicon?

How fast can a Qorvo project start delivering?

Should we choose QM33/QM35, or migrate from DW3000 now?

Do you also work on non-Qorvo UWB and wireless silicon?

Let's work on your next project together