CircuitPython 9.2.4-154-gbd572f86f9` → BLE File Transfer **does not appear**

[zachar-apps]

CircuitPython version and board name

* ✅ A: `CircuitPython 9.1.0-beta.3-6-gc2443f993f` → BLE File Transfer Service (UUID `0xFEBB`) **appears as expected**
* ❌ B: `CircuitPython 9.2.4-154-gbd572f86f9` → BLE File Transfer **does not appear**, despite identical board configuration and settings

Code/REPL

*Expected**: BLE service UUID `0xFEBB` should be visible on  CircuitPython 9.2.4-154-gbd572f86f9 after preforming 
1. Custom UF2 built with the following settings:

   * In `mpconfigboard.mk`:

     
     CIRCUITPY_BLEIO = 1
     CIRCUITPY_BLE_FILE_SERVICE = 1
     CIRCUITPY_BLE_WORKFLOW = 1
     
   * `settings.toml` on CIRCUITPY contains:

     
     CIRCUITPY_BLE_ENABLED = 1

Behavior

🐛 BLE File Service Missing in Custom Build (Regression from 9.1.0-beta.3 to 9.2.4)

Board: Custom nRF52840-based board

Bootloader: raytac_mdbt50q_db_40

CircuitPython Version Comparison:

• ✅ A: CircuitPython 9.1.0-beta.3-6-gc2443f993f → BLE File Transfer Service (UUID 0xFEBB) appears as expected
• ❌ B: CircuitPython 9.2.4-154-gbd572f86f9 → BLE File Transfer does not appear, despite identical board configuration and settings

Description

No response

Additional information

1. Custom UF2 built with the following settings:

   • In mpconfigboard.mk:

     CIRCUITPY_BLEIO = 1
     CIRCUITPY_BLE_FILE_SERVICE = 1
     CIRCUITPY_BLE_WORKFLOW = 1

   • settings.toml on CIRCUITPY contains:

     CIRCUITPY_BLE_ENABLED = 1

[tannewt]

Both 9.1.0 and 9.2.4 are old. Please try it with main which is a 10.0.0 beta.

[dhalbert]

See #10522 (comment)

As of #9344 (included in 9.1.0-beta.4), we no longer always start the BLE workflow, including the file transfer service you mention. Read that PR and see https://docs.circuitpython.org/en/latest/docs/workflows.html#ble for information about how to enable the BLE workflow when booting.

try pressing the reset button as described in the link above:

The BLE workflow is enabled for Nordic boards. By default, to prevent malicious access, it is disabled. To connect to the BLE workflow, press the reset button while the status led blinks blue quickly after the safe mode blinks.

[zachar-apps]

from this explanation i didnt undersdtand what i need to do when build circuitpython image and inside ciircuitpy drive need add to enable frp ?

The BLE workflow is enabled for Nordic boards. By default, to prevent malicious access, it is disabled. To connect to the BLE workflow, press the reset button while the status led blinks blue quickly after the safe mode blinks. The board will restart and broadcast the file transfer service UUID (0xfebb) along with the board’s Creation IDs. This public broadcast is done at a lower transmit level so the devices must be closer. On connection, the device will need to pair and bond. Once bonded, the device will broadcast whenever disconnected using a rotating key rather than a static one. Non-bonded devices won’t be able to resolve it. After connection, the central device can discover two default services. One for file transfer and one for CircuitPython specifically that includes serial characteristics.

To change the default BLE advertising name without (or before) running user code, the desired name can be put in the settings.toml file. The key is CIRCUITPY_BLE_NAME. It’s limited to approximately 30 characters depending on the port’s settings and will be truncated if longer.

i have custom pcb board base on raytec module

[dhalbert]

You don't need to change anything in the build, or add anything special to settings.toml unless you want to change the advertised name. But now, what you do need to do is to press the reset button when your status LED blinks blue. If you don't have an RGB status LED, then I think the plain status LED blinks.

We changed this so you have to take an action to start using the BLE workflow, because it was otherwise a security issue. Once you're paired/bonded, then it should start up automatically subsequently. If the pairing/bonding info on either side is deleted, you will again need to do the "reset when blue".

It will also not attempt to start up if it is connected via USB to the host computer, since then you could just use the CIRCUITPY drive directly.

The code for all this is in supervisor/shared/bluetooth/bluetooth.c.

EDIT:
PR #9344 made the "click reset to bond" change.

If this is an issue for your board design, we could add a compilation flag that does not require the extra reset push, but it would be less secure.

[dhalbert]

Closing for now.