Skip to content

Add nRF52 2.4GHz wireless bridge - #3514

Open
recrof wants to merge 1 commit into
meshcore-dev:devfrom
recrof:nrf52-wireless-bridge
Open

recrof wants to merge 1 commit into
meshcore-dev:devfrom
recrof:nrf52-wireless-bridge

Conversation

@recrof

@recrof recrof commented Sep 27, 2026 •

Copy link
Copy Markdown
Member

NRF52RadioBridge: an ESP-NOW-like broadcast bridge that drives the RADIO peripheral directly (1Mbit GFSK, custom framing) and reuses the ESP-NOW payload format, secret and Fletcher-16 isolation.

  • compile repeater with WITH_NRF52_WIRELESS_BRIDGE
  • bridge.channel 1/2/3 -> 2482/2450/2424 MHz
  • new bridge.txpower setting (-20..8 dBm, default 4)
  • bridge.type reports "nrf52-wireless", advert feature flag 0x05
  • listen-before-talk with random backoff
  • fixed whitening seed: frequency-derived seeds made the hardware CRC check fail on some channels
  • move xorCrypt into BridgeBase (also fixes divide-by-zero on an empty secret)
  • bridge envs: RAK4631, RAK3401, Heltec T114/T096, Xiao nRF52, SenseCAP Solar, ProMicro, Wio Tracker L1

NRF52RadioBridge: an ESP-NOW-like broadcast bridge that drives the
RADIO peripheral directly (1Mbit GFSK, custom framing) and reuses the
ESP-NOW payload format, secret and Fletcher-16 isolation.

- compile repeater with WITH_NRF52_WIRELESS_BRIDGE
- bridge.channel 1/2/3 -> 2482/2450/2424 MHz
- new bridge.txpower setting (-20..8 dBm, default 4)
- bridge.type reports "nrf52-wireless", advert feature flag 0x05
- listen-before-talk with random backoff
- fixed whitening seed: frequency-derived seeds made the hardware CRC
  check fail on some channels
- move xorCrypt into BridgeBase (also fixes divide-by-zero on an empty
  secret)
- bridge envs: RAK4631, RAK3401, Heltec T114/T1/T096, Xiao nRF52,
  SenseCAP Solar, ProMicro, Wio Tracker L1
@recrof

recrof commented Sep 27, 2026

Copy link
Copy Markdown
Member Author

@jbrazio can you review please?

@liamcottle

liamcottle commented Sep 28, 2026 •

Copy link
Copy Markdown
Member
Screenshot 2026-09-28 at 1 03 21 PM

I've tested with the following setup, and it appears to be working:

  • 1x RAK4631 repeater with 917MHz LoRa and nRF52 2.4GHz bridge enabled
  • 1x RAK4631 repeater with 918MHz LoRa and nRF52 2.4GHz bridge enabled
  • 1x Wio Tracker L1 Pro companion with 917MHz LoRa
  • 1x Wio Tracker L1 Pro companion with 918MHz LoRa

I'm able to send private messages between both companions, and can see the traffic being passed across both 91xMHz frequencies.

I don't have an SDR that can show 2.4GHz, but I can see the packets being logged in the repeater bridge debug logs.

Logging in to both repeaters via either companion, on either frequency is also working.

This will be a nice alternative to serial bridge via TX/RX pins, allowing for cross frequency LoRa bridging on nRF devices without needing to do hardware modification.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants