FakeTec v3 / ProMicro NRF52840 — Companion BLE not discoverable with MeshCore v1.17.1 and v1.18.0
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- c
调研方向
Start by locating the ProMicro companion BLE board definition and its BLE initialization and advertising entry points, then compare the MeshCore build configuration with the reported nRF52840 board and SoftDevice details. Reproduce the firmware on the FakeTec v3 if possible and inspect BLE scan results and startup diagnostics. Done means identifying why Companion BLE does not advertise on this configuration or documenting a supported build or diagnostic path.
由索引模型根据 Issue 内容生成。
描述
Hardware
• Board: FakeTec v3
• MCU: Nordic nRF52840, ProMicro form factor
• LoRa module: Heltec HT-RA62, SX1262, 868 MHz variant
• Bootloader: UF2 Bootloader 0.9.2-OTAFIX2.2-BP1.3
• Board ID: nRF52840-promicro
• SoftDevice: S140 6.1.1
• Bootloader build date: April 13, 2026
Firmware tested
Flashed using the official MeshCore FakeTec web flasher:
https://flasher.meshcore.io/promicro-nrf52-faketec/
• ProMicro_companion_radio_ble-v1.17.1-d929643.uf2
• Companion BLE firmware v1.18.0, also selected from the official FakeTec flasher
Both versions exhibit the same behaviour.
The bootloader was also updated to promicro_nrf52840_bootloader-0.9.2-OTAFIX2.2.uf2. Flashing and erasing were repeated multiple times, with no improvement.
Problem
After flashing MeshCore Companion BLE, the device is not discoverable over Bluetooth Low Energy.
• Android cannot find the device using nRF Connect for Mobile, even when scanning close to the board.
• The device does not appear in the BLE scan results at all.
• The blue LED blinks after flashing MeshCore.
• The USB serial device remains visible on macOS as /dev/cu.usbmodem11401.
• Re-entering the UF2 bootloader works, and INFO_UF2.TXT reports the board and bootloader details listed above.
Control test: Meshtastic works
When I flash Meshtastic firmware for NRF52_PROMICRO_DIY onto the same hardware, Bluetooth works normally and the device is discoverable.
This strongly suggests that the hardware, USB connection, and Bluetooth radio are functional. The problem appears specific to the MeshCore firmware or its compatibility with this FakeTec/ProMicro hardware configuration.
Host and test environment
• Host used for flashing: macOS on a Mac mini
• BLE scanning device: Android phone
• BLE scanner: nRF Connect for Mobile
• USB product name: ProMicro NRF52840
• USB vendor string: Nologo
• USB Vendor ID: 9114 (0x239A)
• USB Product ID: 179 (0x00B3)
• USB serial number: 8DEDEAFD8E94B8EE
Expected behaviour
After flashing Companion BLE and rebooting, the device should advertise over BLE and be discoverable by nRF Connect and the MeshCore mobile app.
Actual behaviour
No BLE advertisements from the device are visible, with either MeshCore v1.17.1 or v1.18.0. Meshtastic BLE works normally on the same board.
Questions
- Is ProMicro_companion_radio_ble fully supported on the FakeTec v3 hardware revision using the nRF52840-promicro board and OTAFIX 2.2 bootloader?
- Are there any known BLE initialisation or SoftDevice compatibility issues with this hardware configuration?
- Is a specific firmware build, board definition, bootloader version, or hardware modification required?
- Is there a recommended diagnostic procedure to determine why the Companion BLE firmware does not advertise?
Thank you for your help.
- 主要语言
- C
- 星标
- 3.9k
- 派生
- 1.5k
- 平均合并
- 1 天 3 小时
- 30 天内合并 PR
- 24
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
meshcore-dev/MeshCore 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 63/100
meshcore-dev/MeshCore#3622 ·
维护者通常 1 天内回复
-
[Feature Request] Set Australia (Mid) Preset to automatically enable 2 byte default path hash size未关闭
难度 2/5 1-3 小时 新手友好度 62/100
meshcore-dev/MeshCore#3571 · 5 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
meshcore-dev/MeshCore#3567 · 1 条评论 ·
维护者通常 1 天内回复
-
RTC_RX8130CE writes and reads the one-hot WEEK register as a number可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
meshcore-dev/MeshCore#3549 ·
维护者通常 1 天内回复
-
Repeater: CLI reply to 'setperm <key> 0' is lost when the removed ACL entry sits before the requester (stale ClientInfo* after array shift)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 77/100
meshcore-dev/MeshCore#3513 ·
维护者通常 1 天内回复
查看 meshcore-dev/MeshCore 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
valkey-io/valkey#4979 · 1 个 reaction ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
colbymchenry/codegraph#2770 ·
维护者通常 1 天内回复
-
area/ysql kind/enhancement priority/medium status/awaiting-triage
难度 2/5 1-3 小时 新手友好度 73/100
yugabyte/yugabyte-db#35578 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
test_announce_and_connect_via_dns binds a fixed port that other tests' nodes can be handed可能已有人在做 @ksedgwic 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 83/100
ElementsProject/lightning#9642 ·
维护者通常 2 天内回复