So if it helps, here is the entirety of the skeleton code that I've reduced this to, which still doesn't show anything but the two generic services I described above. I'm at a complete loss. If I put any firmware into the SPBTLE-1S module other than what is shipped with it, the BLE.begin() call fails. If I put the default firmware into the SPBTLE-1S module, then BLE gets initialized but the added custom services don't show up on any tools I use to inspect BLE devices (such as ST BLE Toolbox).
#include <STM32duinoBLE.h>
BLEService customService("0000FF00-0000-1000-8000-00805F9B34FB"); // Custom service UUID
BLECharacteristic customCharacteristic("0000FF01-0000-1000-8000-00805F9B34FB", BLEWrite | BLERead, 32); // Custom characteristic UUID
SPIClass SpiHCI(PC3, PD3, PD1);
HCISpiTransportClass HCISpiTransport(SpiHCI, SPBTLE_1S, PD0, PD4, PA8, 1000000, SPI_MODE1);
BLELocalDevice BLEObj(&HCISpiTransport);
BLELocalDevice& BLE = BLEObj;
void setup() {
Serial.begin(115200);
while (!Serial);
Serial.print("Starting BLE\n");
// Initialize BLE
if (!BLE.begin()) {
Serial.print("BLE Init failed.\n");
while(1);
}
// Set advertised local name and service UUID
BLE.setLocalName("myRemoteDevice");
BLE.setAdvertisedService(customService);
BLE.addService(customService);
// Add the characteristic to the service
customService.addCharacteristic(customCharacteristic);
// Start advertising
BLE.advertise();
Serial.print("Exiting Setup()\n");
}
void loop() {
// Handle BLE events
BLE.poll();
// Check if data has been received
if (customCharacteristic.written()) {
Serial.print("Remote received data\n");
}
}
