BLE SDK development that nails the hard parts

Q: Do you develop BLE 6.0 Channel Sounding firmware?

Yes - needCode develops BLE 6.0 Channel Sounding firmware, including proprietary PBR (phase-based ranging) solvers for the integer-ambiguity problem that makes Channel Sounding ranging accurate. This is the secure-ranging layer behind digital keys and proximity, where signal-strength estimates fall short. needCode also builds BLE 5.4 stacks and the connection firmware around them.

Q: What are PBR solvers and why do they matter?

PBR solvers resolve the integer-ambiguity problem in phase-based ranging - the mathematical step that turns a BLE 6.0 Channel Sounding phase measurement into an accurate distance. They matter because without them Channel Sounding ranging isn't reliable enough for a digital key, and per needCode's experience the major silicon vendors don't solve this internally. needCode's solvers are proprietary and a core BLE differentiator.

Q: Can you optimise our BLE power consumption and battery life?

Yes - needCode runs a dedicated BLE Power Optimization Lab where battery life is measured and tuned across connection parameters, sleep behaviour, and radio scheduling, rather than estimated. Power is where most BLE products succeed or fail, so it is treated as an instrumented engineering discipline. The output is a measured improvement, not a datasheet figure.

Q: Can you fix multi-connection stability issues?

Yes - needCode has solved documented BLE multi-connection stability problems on NXP, TI, and Infineon platforms, where a stack that works with a few connections degrades under dozens. This is exactly the kind of unglamorous depth that decides whether a product ships. It is a common reason teams bring needCode into an existing SDK.

Q: Which BLE chipsets and SDKs do you work with?

needCode works across the BLE silicon and SDKs used in production, including Nordic (nRF Connect SDK), NXP (MCUXpresso), Silicon Labs (Simplicity Studio), Infineon (ModusToolbox), Espressif (ESP32), and Qorvo. Our engineers include people who shipped at these vendors. We pick the toolchain that matches your silicon and lifecycle.

Q: Do you do BLE Mesh?

Yes - needCode's team co-authored official Bluetooth SIG mesh specifications and delivered the world's first certified BLE Mesh stack, with mesh proven at 1,000 nodes and 99.9% delivery. This covers smart-building and industrial mesh networks at scale. BLE Mesh at scale is also available as a dedicated service.

Q: Can you build BLE digital-key and secure-ranging firmware?

Yes - needCode builds BLE 6.0 Channel Sounding distance bounding for digital keys and relay-attack resistance, using its proprietary PBR ranging solvers. This is the BLE side of a secure access system, often paired with UWB for the highest-assurance use cases. It supports CCC and Aliro digital-key designs.

Q: How is this different from the chip vendor's BLE SDK?

A vendor SDK gets you connected; a production SDK ships a product that meets its power, stability, and ranging targets - which is where vendor SDKs typically stop. needCode builds production-grade firmware tuned for battery life and stability, with Channel Sounding and qualification handled, and you own the result. The difference shows up in the field, not the demo.

Q: Do you handle BLE certification and qualification?

Yes - needCode runs Bluetooth SIG qualification and has automated the PTS process, taking it from weeks of manual testing to an overnight job. This shortens the path to a qualified product and reduces first-attempt failures. Qualification is treated as part of SDK delivery, not a separate scramble at the end.

Q: Can you take over our existing BLE SDK?

Yes - needCode modernises and maintains existing BLE SDKs, including power-optimization passes, Channel Sounding upgrades, multi-connection stability fixes, RTOS portability, and ongoing release management. This suits an SDK that has outgrown the team maintaining it. The engagement runs as fixed-scope modernisation or an ongoing team extension.

needCode builds production BLE SDKs and firmware where it's genuinely hard - power consumption, multi-connection stability, and BLE 6.0 Channel Sounding ranging. Proprietary PBR solvers for the integer-ambiguity problem NXP, TI, and Infineon don't solve internally; a dedicated BLE Power Optimization Lab; and SDK work by Bluetooth SIG contributors who delivered the world's first certified BLE Mesh stack.

Book a discovery call

Explore BLE

We work with Industry Leaders

BLE is easy to start and hard to ship. The hard parts are where SDKs fail.

A "hello world" BLE connection takes an afternoon. A shippable BLE product is a different problem: battery life that meets the spec under real traffic, a stack that stays stable across dozens of simultaneous connections, and - increasingly - Channel Sounding ranging accurate enough for a digital key. These are the parts where a generic SDK quietly underperforms, and where a chipset's getting-started demo stops being enough.

needCode builds for exactly those parts. Our BLE engineers came from the silicon vendors, co-authored Bluetooth SIG specifications, and run a dedicated Power Optimization Lab — and our proprietary PBR solvers close the integer-ambiguity gap that makes Channel Sounding ranging viable, a gap the major vendors don't fill themselves.

Proprietary ranging solvers

PBR solvers for the integer-ambiguity problem in BLE 6.0 Channel Sounding - depth NXP, TI, and Infineon don't have internally.

A dedicated Power Lab

Battery life tuned and measured in a real lab, not estimated - because power is where BLE products live or die.

Built by standards authors

SDK work by Bluetooth SIG contributors who shipped the world's first certified BLE Mesh stack.

What a production BLE SDK includes

A BLE SDK that ships products is four layers - and needCode builds all four, including the ones a quick demo skips.

Stack & Connection Firmware

BLE 5.4 and 6.0 firmware: GATT/GAP, multi-connection stability, PAwR, and the connection management that holds under real traffic. Documented stability issues solved on NXP, TI, and Infineon platforms.

BLE

Channel Sounding & Ranging

BLE 6.0 Channel Sounding with proprietary PBR solvers for integer-ambiguity resolution - phase-based ranging accurate enough for digital keys and proximity, where signal-strength estimates aren't.

BLE Channel Sounding

Power Optimization

Battery life tuned and measured in the BLE Power Optimization Lab - across connection parameters, sleep, and radio scheduling. The difference between a datasheet figure and a product that actually lasts in the field.

SDK, Tooling & Maintenance

Demo apps, clean APIs, docs-as-code, and SDK maintenance across nRF Connect, ModusToolbox, and MCUXpresso - owned across releases, with automated Bluetooth qualification.

Automated Testing & CI/CD

Need a BLE SDK that survives production?

Book a discovery call with our CEO

Book a discovery call

What your BLE SDK powers

needCode builds the SDK with the product on top in view, across the BLE use cases.

Digital Keys & Secure Ranging

BLE 6.0 Channel Sounding distance bounding for digital keys and relay-attack resistance - the secure-ranging layer that makes phone-as-key trustworthy.

Digital Keys & Access

Relay Attack Prevention

Automotive & SDV

BLE Mesh at Scale

Mesh firmware proven at 1,000 nodes, 99.9% delivery - smart buildings and industrial sites.

BLE Mesh Networks

BLE Mesh at Scale

Industrial IoT & RTLS

Connected & Wearable Products

Low-power BLE for medical, consumer, and IoT devices where battery life is the product.

Across the ICP

Chipset SDKs for semiconductor vendors, in-vehicle BLE for automotive, device connectivity for IoT.

Semiconductor Manufacturers

Automotive & SDV

Why teams bring needCode in for BLE SDKs

Engineers from the BLE silicon vendors

Our team includes engineers with production experience at Nordic Semiconductor, Texas Instruments, and Silicon Labs. They know the stack and the silicon's behaviour - not a learning curve you fund.

Proprietary PBR ranging solvers

We close the integer-ambiguity gap in BLE 6.0 Channel Sounding that the major vendors don't solve internally - making Channel Sounding ranging viable for digital keys and proximity. It's the hardest part of BLE ranging, and it's ours.

A dedicated Power Optimization Lab

Battery life measured and tuned in a real lab. Power is where BLE products succeed or fail, so we treat it as an engineering discipline with instruments, not an estimate.

Standards authors

Active in the Bluetooth SIG, co-authors of BLE Mesh specifications and the world's first certified BLE Mesh stack - your SDK is built to the spec by a team shaping it.

Four ways to bring needCode in

From a one-month audit to a multi-year partnership. We tailor the engagement to where the SDK is in its lifecycle.

01 SDK Audit & Roadmap

Duration:
2–4 weeks
Best for:
An existing BLE SDK needing external assessment - often a power or stability review
Deliverable:
Audit report, prioritised remediation roadmap, leadership readout

02 Greenfield BLE SDK & Bring-Up

Duration:
Phased
Best for:
New BLE silicon or a new product where the SDK is built from zero
Deliverable:
Stack and connection firmware, Channel Sounding, demo apps, working reference

03 SDK Modernisation

Duration:
Phased
Best for:
A mature BLE SDK needing a power-optimization pass, a Channel Sounding upgrade, or multi-connection stability fixes
Deliverable:
Measured power gains, stability fixes, refactored components, updated CI and docs

04 Long-Term Team Extension

Duration:
Multi-year, retainer-based
Best for:
Vendors who want needCode integrated with the full SDK release process
Deliverable:
An embedded BLE engineering team inside your cadence - the model behind the 30-FTE Qorvo programme

What we ship on

No religious wars - we pick the silicon, SDK, and toolchain that match your product and its lifecycle.

BLE silicon

Nordic nRF52 / nRF54

NXP

Texas Instruments

Silicon Labs

Espressif (ESP32)

Qorvo

Stack & standards

BLE 5.4

BLE 6.0 Channel Sounding

GATT / GAP

PAwR

BLE Mesh

Bluetooth SIG

Ranging

BLE 6.0 Channel Sounding

proprietary PBR (phase-based ranging) solvers

SDKs & toolchains

nRF Connect SDK

ModusToolbox

MCUXpresso

Simplicity Studio

Zephyr

FreeRTOS

Tooling, security & OTA

BLE Power Optimization Lab

CI/test

PSA Crypto

automated Bluetooth qualification (PTS)

secure boot

signed firmware

TF-M

Case studies

A PoC is only worth the honesty of its measurement, and that rests on a real lab and real practice.

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

Automating Bluetooth Qualification: From Weeks of PTS to an Overnight Job

There is a particular ritual in Bluetooth product development that anyone who has been through it remembers vividly. It is the manual qualification regression: sitting in front of a Windows machine running the Profile Tuning Suite, clicking through hundreds of test cases over the course of a week or two, interpreting results that range from […]

Monolithic, meta-tool, or registry: choosing how to ship your embedded SDK

Most SDK teams do not consciously choose a delivery model. They inherit one. The first release of a new platform ships as a single archive because that’s the fastest way to get something into customers’ hands. The next few releases follow the same pattern because it works. By the time the team has five product […]

Documentation as a product: how good SDKs treat docs as code

The deliverable customers interact with most often is the one most commonly treated as a secondary artifact. Six document types, six audiences, and one release gate that fixes most of the failure modes. A semiconductor SDK can have an exemplary architecture, a thoughtfully versioned C API, a security framework that maps cleanly to PSA Certified […]

FAQ