Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

FakeTec v3 / ProMicro NRF52840 — Companion BLE not discoverable with MeshCore v1.17.1 and v1.18.0

Geschlossen
  • Stimmt etwas nicht?
#3,618 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
c
Bereich
embedded-iot, networking

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

  1. Is ProMicro_companion_radio_ble fully supported on the FakeTec v3 hardware revision using the nRF52840-promicro board and OTAFIX 2.2 bootloader?
  2. Are there any known BLE initialisation or SoftDevice compatibility issues with this hardware configuration?
  3. Is a specific firmware build, board definition, bootloader version, or hardware modification required?
  4. Is there a recommended diagnostic procedure to determine why the Companion BLE firmware does not advertise?

Thank you for your help.

Vorherrschende Sprache
C
Sterne
3.9k
Forks
1.5k
Ø Merge
1 T. 8 Std.
Gemergte PRs (30 T.)
25

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus meshcore-dev/MeshCore

Alle Issues in meshcore-dev/MeshCore

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.