Issues using ESP32_S3_BLE target with ESP32ESP32-S3 with Wifi & BLE

[W3THS]

Hi,
I've had a look through the existing discussions but can't seem to find anything that answers my question. When I flash the ESP32_S3_BLE target onto my device, windows device manager constantly refreshes as it can't seem to see the device properly. Flashing ESP32_S3 onto the device makes it work fine. Am I doing something wrong? or is it just incompatible?

I'm trying to deploy some code that uses nanoFramework.Device.Bluetooth nuget but can't deploy it as The connected target does not have support for nanoFramework.Device.Bluetooth.

Update
I was able to flash ESP32_S3_BLE when I specified a different version (1.9.0.981) and I was able to upload my code. Once it uploaded and rebooted, Device Manager then started constantly refreshing. So I made some progress but still facing issue's

Update 2
I've discovered that by using the --masserase with nanoff that I can get the device back working using the BLE firmware. The problem seems to start happening once I flash some code that uses the Bluetooth capabilities. In this particular scenario I'm flashing the BluetoothLESample1 project to my device which triggers the device to become unstable in device manager.

Nanoff Device Info:

ESP32-S3 (ESP32-S3 (revision v0.2))
Features WiFi, BLE
Flash size 16MB unknown from TENX (manufacturer 0x94 device 0x16408)
PSRAM: undetermined
Crystal 40MHz
MAC <Removed>

Device capabilities below:

HAL build info: nanoCLR running @ ESP32_S3 built with ESP-IDF v4.4.6
  Target:   ESP32_S3
  Platform: ESP32

Firmware build Info:
  Date:        Dec 22 2023
  Type:        MinSizeRel build, support for PSRAM
  CLR Version: 1.9.0.178
  Compiler:    GNU ARM GCC v8.4.0

OEM Product codes (vendor, model, SKU): 0, 0, 0

Serial Numbers (module, system):
  00000000000000000000000000000000
  0000000000000000

Target capabilities:
  Has nanoBooter: NO
  IFU capable: NO
  Has proprietary bootloader: YES

AppDomains:

Assemblies:
  nanoFramework.Runtime.Events, 1.11.15.0
  nanoFramework.Hardware.Esp32, 1.6.12.0
  nanoFramework.Device.Bluetooth, 1.1.60.0
  nanoFramework.System.Text, 1.2.54.0
  mscorlib, 1.15.6.0
  nanoFramework.System.Collections, 1.5.31.0
  nanoFramework.Runtime.Native, 1.6.12.0
  nanoFramework.Graphics.Core, 1.2.4.0
  System.Device.Gpio, 1.1.38.0
  nanoFramework.Hardware.Esp32.Rmt, 2.0.7.0

Native Assemblies:
  mscorlib v100.5.0.19, checksum 0x445C7AF9
  nanoFramework.Runtime.Native v100.0.9.0, checksum 0x109F6F22
  nanoFramework.Hardware.Esp32 v100.0.10.0, checksum 0x6A20A689
  nanoFramework.Hardware.Esp32.Rmt v100.0.4.0, checksum 0x608C5658
  nanoFramework.Networking.Sntp v100.0.4.4, checksum 0xE2D9BDED
  nanoFramework.ResourceManager v100.0.0.1, checksum 0xDCD7DF4D
  nanoFramework.System.Collections v100.0.1.0, checksum 0x2DC2B090
  nanoFramework.System.Text v100.0.0.1, checksum 0x8E6EB73D
  nanoFramework.System.IO.Hashing v100.0.0.1, checksum 0xEBD8ED20
  nanoFramework.System.Security.Cryptography v100.0.0.1, checksum 0xC71CFC75
  nanoFramework.Runtime.Events v100.0.8.0, checksum 0x0EAB00C9
  EventSink v1.0.0.0, checksum 0xF32F4C3E
  System.IO.FileSystem v1.0.0.2, checksum 0x545A6C79
  System.Math v100.0.5.5, checksum 0x9F9E2A7E
  System.Net v100.1.5.0, checksum 0x5BAB8CB3
  System.Device.Adc v100.0.0.0, checksum 0xE5B80F0B
  System.Device.Gpio v100.1.0.6, checksum 0x097E7BC5
  System.Device.I2c v100.0.0.2, checksum 0xFA806D33
  System.Device.I2c.Slave v1.0.0.0, checksum 0x4238164B
  System.Device.I2s v100.0.0.1, checksum 0x478490FE
  System.Device.Pwm v100.1.0.4, checksum 0xABF532C3
  System.IO.Ports v100.1.6.1, checksum 0xB798CE30
  System.Device.Spi v100.1.2.0, checksum 0x3F6E2A7E
  System.Runtime.Serialization v100.0.0.0, checksum 0x0A066871
  System.Device.Wifi v100.0.6.4, checksum 0x00A058C6
  Windows.Storage v100.0.2.0, checksum 0x954A4192



++++++++++++++++++++++++++++++++
++        Memory Map          ++
++++++++++++++++++++++++++++++++
  Type     Start       Size
++++++++++++++++++++++++++++++++
  RAM   0x3fcaa968  0x00018800
  FLASH 0x00000000  0x01000000



+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++                   Flash Sector Map                        ++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  Region     Start      Blocks   Bytes/Block    Usage
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
      0    0x00010000       1      0x1A0000     nanoCLR
      1    0x001B0000       1      0x2E0000     Deployment
      2    0x00490000       1      0x300000     Configuration


+++++++++++++++++++++++++++++++++++++++++++++++++++
++              Storage Usage Map                ++
+++++++++++++++++++++++++++++++++++++++++++++++++++
  Start        Size (kB)           Usage
+++++++++++++++++++++++++++++++++++++++++++++++++++
  0x00490000    0x300000 (3072kB)   Configuration
  0x00010000    0x1A0000 (1664kB)   nanoCLR
  0x001B0000    0x2E0000 (2944kB)   Deployment



Deployment Map
Empty

[Ellerbach]

I had same issue last week. I originally though it was because my code was too big. But my issue is the same as described.

[Iguins]

Facing the same issue when using. As you suggested --masserase help put the board back on track. will update if I have new finding with ble usage.