Connecting ESP32-S3-OTG to HID device

vapisoft
Posts: 12
Joined: Sun Sep 03, 2023 6:12 am

Connecting ESP32-S3-OTG to HID device

Postby vapisoft » Mon Sep 18, 2023 1:22 pm

Hi,

I purchased ESP32-S3-WROOM from Freenove in order to ccreate a BLE bridge from my HID sensor to a PC.
I programmed the device to send data continuesly so I can see that the ESP can read the data from the sensor.
I used several HID exampes but in none of them I can see any data.

The example I use now is: ble_hidd_demo from:
https://github.com/espressif/esp-idf/bl ... /README.md

I expect to see something in my event callback.
static void hidd_event_callback(esp_hidd_cb_event_t event, esp_hidd_cb_param_t *param)

This is the "Terminal outout that I receive"
PS C:\Users\shlomoa\esp-idf\examples\bluetooth\bluedroid\ble\ble_hid_device_demo> set IDF_PATH=C:\Users\shlomoa\espPS C:\Users\shlomoa\esp-idf\examples\bluetooth\bluedroid\ble\ble_hid_device_demo> C:\Users\shlomoa\.espressif\python_env\idf5.0_py3.8_env\Scripts\python.exe C:\Users\shlomoa\esp\esp-idf\tools\idf_monitor.py -p COM22 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --target esp32s3 c:\Users\shlomoa\esp-idf\examples\bluetooth\bluedroid\ble\ble_hid_device_demo\build\hidd_demos.elf
--- WARNING: GDB cannot open serial ports accessed as COMx
--- Using \\.\COM22 instead...
--- idf_monitor on \\.\COM22 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x2b (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3810,len:0x165c
load:0x403c9700,len:0xbe0
load:0x403cc700,len:0x2d9c
entry 0x403c9900
I (25) boot: ESP-IDF v5.0.2-dirty 2nd stage bootloader
I (25) boot: compile time 14:57:48
I (25) boot: chip revision: v0.1
I (27) boot.esp32s3: Boot SPI Speed : 80MHz
I (32) boot.esp32s3: SPI Mode : DIO
I (37) boot.esp32s3: SPI Flash Size : 2MB
I (41) boot: Enabling RNG early entropy source...
I (47) boot: Partition Table:
I (50) boot: ## Label Usage Type ST Offset Length
I (58) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (73) boot: 2 factory factory app 00 00 00010000 00100000
I (80) boot: End of partition table
I (84) esp_image: segment 0: paddr=00010020 vaddr=3c080020 size=1f53ch (128316) map
I (116) esp_image: segment 1: paddr=0002f564 vaddr=3fc96400 size=00ab4h ( 2740) load
I (117) esp_image: segment 2: paddr=00030020 vaddr=42000020 size=76c84h (486532) map
I (209) esp_image: segment 3: paddr=000a6cac vaddr=3fc96eb4 size=02eb8h ( 11960) load
I (212) esp_image: segment 4: paddr=000a9b6c vaddr=40374000 size=12384h ( 74628) load
I (238) boot: Loaded app from partition at offset 0x10000
I (239) boot: Disabling RNG early entropy source...
I (250) cpu_start: Pro cpu up.
I (250) cpu_start: Starting app cpu, entry point is 0x40375334
0x40375334: call_start_cpu1 at C:/Users/shlomoa/esp/esp-idf/components/esp_system/port/cpu_start.c:141

I (0) cpu_start: App cpu up.
I (265) cpu_start: Pro cpu start user code
I (265) cpu_start: cpu freq: 160000000 Hz
I (265) cpu_start: Application information:
I (268) cpu_start: Project name: hidd_demos
I (273) cpu_start: App version: v5.2-dev-1128-g03d4fa2869-dirty
I (280) cpu_start: Compile time: Sep 18 2023 14:57:02
I (286) cpu_start: ELF file SHA256: 7c374bf3b59bbd6f...
I (292) cpu_start: ESP-IDF: v5.0.2-dirty
I (297) cpu_start: Min chip rev: v0.0
I (302) cpu_start: Max chip rev: v0.99
I (307) cpu_start: Chip rev: v0.1
I (312) heap_init: Initializing. RAM available for dynamic allocation:
I (319) heap_init: At 3FC9DCB8 len 0004BA58 (302 KiB): DRAM
I (325) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DRAM
I (332) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (338) heap_init: At 600FE010 len 00001FF0 (7 KiB): RTCRAM
I (345) spi_flash: detected chip: gd
I (349) spi_flash: flash io: dio
W (353) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (366) coexist: coexist rom version e7ae62f
I (371) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (412) BT_INIT: BT controller compile version [80abacd]
I (412) phy_init: phy_version 540,a5d905b,Oct 20 2022,19:36:11
I (452) system_api: Base MAC address is not set
I (452) system_api: read default base MAC address from EFUSE
I (452) BT_INIT: Bluetooth MAC: 34:85:18:77:3d:12

I (472) HID_DEMO: hidd_event_callback
I (472) HID_DEMO: hidd_event_callback
I (482) HID_LE_PRF: esp_hidd_prf_cb_hdl(), start added the hid service to the stack database. incl_handle = 40
I (482) HID_DEMO: gap_event_handler: 0
I (492) HID_LE_PRF: hid svc handle = 2d
I (492) HID_DEMO: gap_event_handler: 6

bidrohini
Posts: 202
Joined: Thu Oct 27, 2022 12:55 pm

Re: Connecting ESP32-S3-OTG to HID device

Postby bidrohini » Wed Sep 20, 2023 12:54 pm

Here is a thread about the same warning message:
viewtopic.php?t=20113

Who is online

Users browsing this forum: Baidu [Spider], ESP_Roland, Heggico and 97 guests