A sketch that includes BTstackLib on a CYW43 board fails with arduino-pico's static_assert: "This library needs Bluetooth enabled. Use the 'Tools->IP/ Bluetooth Stack' menu in the IDE to enable it." There is no such menu here, so it reads as a setting we forgot to expose. What is actually true is simpler: the CYW43439's Bluetooth controller is not emulated — only its WiFi side is — so there is nothing to switch on. Appends that, leaving the compiler's own diagnostic intact above it because the developer still needs the real text. Deliberately a separate helper from humanize_cli_error, which REPLACES arduino-cli's own failures; this one only adds context under a compiler message. Worth knowing for whoever picks up the BT work: this is the honest-failure milestone. Making a BT sketch compile at all means flipping this board's FQBN to ipbtstack=ipv4btcble, which swaps liblwip.a for liblwip-bt.a and costs every sketch on the board ~71 KB flash and ~18 KB RAM — and leaves it reaching HCI_STATE_WORKING while advertising to nobody. The mechanism is mapped in project/pimoroni-pico-plus-2w/STATUS.md. |
||
|---|---|---|
| .. | ||
| app | ||
| board-indexes | ||
| scripts | ||
| sdk | ||
| tests | ||
| .env.example | ||
| Dockerfile | ||
| debug_qemu.py | ||
| mcp_server.py | ||
| mcp_sse_server.py | ||
| requirements.txt | ||