FakeTec v3 / ProMicro NRF52840 — Companion BLE not discoverable with MeshCore v1.17.1 and v1.18.0
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 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時間
- マージ済み PR（30日）
- 24
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- 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 件 ·
メンテナーはふだん 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対応中かも このイシューにリンクされたプルリクエストがオープン中、またはマージ済みです。 オープン
難易度 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)対応中かも このイシューにリンクされたプルリクエストがオープン中、またはマージ済みです。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
meshcore-dev/MeshCore#3513 ·
メンテナーはふだん 1 日以内に返信
meshcore-dev/MeshCore の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
sumatrapdfreader/sumatrapdf#6403 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
followup
難易度 1/5 1時間未満 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
bytecodealliance/StarlingMonkey#343 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
oetiker/rrdtool-1.x#1392 ·