Choosing a chip is only the first step when developing a wireless sensor, smart-home endpoint or Bluetooth peripheral. Buyers and product owners also need to establish whether it fits the application, what development work remains, and what to check before ordering.

The Nordic Semiconductor nRF52840 is a multiprotocol wireless SoC with a 64 MHz Arm Cortex-M4 processor, 1 MB Flash and 256 KB RAM. It supports Bluetooth LE, Thread and Zigbee, and includes USB. See Nordic's official product information.

1. Connecting to a phone: define the data first

Consider evaluating nRF52840 if the product sends temperature readings, button states, sensor measurements or settings to a phone. However, “needs Bluetooth” is not a complete requirement. Establish:

  • How much data is transmitted, and how often?

  • Does the phone stay connected or connect occasionally?

  • Must the phone update the device firmware?

  • Is the device battery-powered or externally powered?

Sending a temperature reading once a minute is different from continuously transmitting a large data stream. Clear requirements help engineers assess communication and power consumption.

2. For smart homes, choose the ecosystem and protocol first

Multiprotocol support does not mean one firmware image automatically connects to every smart-home platform. Features require appropriate software and system design. Identify the target ecosystem, gateway or border-router requirements, remote-update needs and applicable certification requirements. These decisions affect installation, storage planning, cost and launch timing.

For Matter, check the hardware and memory requirements of the selected SDK version. Nordic's Matter documentation specifies external Flash requirements for nRF52840, so 1 MB of internal Flash should not be interpreted as eliminating external storage. Confirm capacity and conditions for your version in the Matter hardware and memory requirements.

3. How can you estimate battery life?

Do not estimate battery life from a “low-power” label or a sleep-current figure alone. Calculate consumption over a complete operating cycle:

Average current ≈ sum of current × duration for each state, divided by total cycle time.

For a hypothetical device operating once every 60 seconds, assume 10 mA for 0.1 seconds and a whole-device sleep current of 0.01 mA for the remaining 59.9 seconds. Average current is approximately 0.0267 mA. A simple calculation with a 220 mAh battery gives approximately 343 days.

This is an illustrative calculation, not an nRF52840 measurement or battery-life promise.Actual results also depend on usable battery capacity, self-discharge, temperature, radio retries, regulators and sensors. Measurements on the actual board running the intended firmware are more useful purchasing inputs.

4. Choose a bare IC, wireless module or development board

  • Rapid functional evaluation:consider a development board.

  • Limited RF design experience:evaluate an nRF52840-based module to reduce some hardware development work.

  • RF design expertise and tight size or BOM requirements:evaluate a bare-IC design.

A module may integrate RF components or an antenna; check its documentation. Module certification has conditions and does not automatically remove end-product compliance obligations. Include engineering, testing and rework in cost comparisons. The difference in unit price is not the same as the difference in total product cost.

5. Why is “NRF52840” insufficient on a purchase order?

It is not a complete ordering specification. Nordic lists several package codes:

  • QI: aQFN, 7 × 7 mm, 73 pins.

  • QF: QFN, 6 × 6 mm, 48 pins.

  • CK: WLCSP, 3.544 × 3.607 mm, 94 balls.

These packages are not interchangeable simply because they share the nRF52840 name. Refer to Nordic's ordering information.

If a supplier proposes another variant, check the full ordering code against the BOM, PCB footprint, required pins and interfaces, function variant, chip revision and assembly packing requirements. Obtain engineering approval before changing the order.

6. What remains after the sample works?

Freeze the material specification.Record the complete part number in the BOM and define which changes require approval.

Prepare production programming.Plan firmware version control, programming interfaces, verification and debug-access protection settings. Prepare the fixture and software process before assembly.

Retain incoming-material records.Keep required labels, lot information and receiving records so issues can be linked to specific deliveries.

Validate before scaling purchases.For a new supplier or changed material, arrange samples or a pilot lot according to project risk. Acceptance should address real functions and agreed requirements; visual inspection does not replace functional validation.

7. A reusable RFQ checklist

  • Product: Nordic nRF52840; complete ordering code approved by engineering.

  • Sample quantity, first production quantity and expected follow-on demand.

  • Packing requirements, target arrival date and delivery destination.

  • Label, lot and traceability requirements.

  • Substitution rule: all part-number or revision changes require prior approval.

Ask suppliers to specify the complete code, quoted quantity, packing conditions and the basis for the lead time. Separate immediately deliverable quantities from expected arrivals. For quote evaluation, read how to compare chip supplier quotations.

Send these details with your WOMAiELEC inquiry to clarify the supply conditions for the exact material. Pricing, quantities and delivery dates are subject to the actual quotation.