Open aircable opened 1 week ago
This hardware bug seems to be on a ESP32S3 chip with revision v0.1. I was successfully working with only channel 39 on revision v0.2 on a ESP32-S3-WROOM-1 module, not on a XIAO-ESP32-S3 module. If you can verify, it's probably ok to close this issue.
@aircable Could you provide me with a full log?
Log of what? There is no error. All commands are executing correctly. You just look on a Bluetooth scanner or write your own scanner code for another ESP32 or use LightBlue on your Android. On the ESP32S3 v0.1 there is just no microwaves generated.
I would like to obtain the startup log information to identify various details about the chip(v0.1). This information is very helpful to me.
Answers checklist.
IDF version.
IDF 5.4
Espressif SoC revision.
ESP32S3
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
Seeed ESP32S3 module
Power Supply used.
USB
What is the expected behavior?
I configured the advertisement like this:
After setting the advertisement data esp_ble_gap_config_adv_data_raw() it starts advertising. Confirming with a spectrum analyzer as well as a BLE scanner app on the phone (LightBlue) the chip is not advertising. There are no error reports, all events are occurring correctly.
Chainging the channel_map to either ADV_CHNL_38 or ADV_CHNL_ALL works ok. I can see the advertisments.
Unfortunately I have no way to control the receiving channels to listen only on channel 39 for example. There is no API, unless you know how to do that. I would appreciate it. So I use external instruments and receivers to check for any channel 39 only advertisements and there are none.
What is the actual behavior?
no error, just does not do what it suppose to do
Steps to reproduce.
I only tested Bluedroid, not Nimble. To reproduce, use the iBeacon demo app in the IDF examples and change the advertisement config to channel 39 only.
Debug Logs.
More Information.
No response