How to know which button is being pressed？ about bluepad32 HOT 20 CLOSED

Copy the content of sketch.cpp to main.c then build

from bluepad32.

4.4

from bluepad32.

from bluepad32.

which board are you using ? is it a Unijoysticle?
Please type: version on the console and copy & paste the output.

add as much info as possible

from bluepad32.

not any board just esp32 wroom

from bluepad32.

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6664
load:0x40078000,len:14944
load:0x40080400,len:3804
entry 0x40080698
I (27) boot: ESP-IDF v4.4.4 2nd stage bootloader
I (27) boot: compile time 14:32:53
I (27) boot: chip revision: v1.0
I (30) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (37) boot.esp32: SPI Speed : 40MHz
I (41) boot.esp32: SPI Mode : DIO
I (46) boot.esp32: SPI Flash Size : 4MB
I (51) boot: Enabling RNG early entropy source...
I (56) boot: Partition Table:
I (59) boot: ## Label Usage Type ST Offset Length
I (67) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (74) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (82) boot: 2 factory factory app 00 00 00010000 00100000
I (89) boot: 3 coredump Unknown data 01 03 00110000 00010000
I (97) boot: End of partition table
I (101) boot_comm: chip revision: 1, min. application chip revision: 0
I (108) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=1dab8h (121528) map
I (161) esp_image: segment 1: paddr=0002dae0 vaddr=3ffbdb60 size=02538h ( 9528) load
I (165) esp_image: segment 2: paddr=00030020 vaddr=400d0020 size=6dd70h (449904) map
I (329) esp_image: segment 3: paddr=0009dd98 vaddr=3ffc0098 size=031c0h ( 12736) load
I (334) esp_image: segment 4: paddr=000a0f60 vaddr=40080000 size=17eb8h ( 97976) load
I (387) boot: Loaded app from partition at offset 0x10000
I (387) boot: Disabling RNG early entropy source...
I (399) cpu_start: Pro cpu up.
I (399) cpu_start: Starting app cpu, entry point is 0x400812f4
I (0) cpu_start: App cpu up.
I (415) cpu_start: Pro cpu start user code
I (415) cpu_start: cpu freq: 160000000
I (415) cpu_start: Application information:
I (420) cpu_start: Project name: bluepad32-app
I (425) cpu_start: App version: release_v3.7.0-rc.0
I (431) cpu_start: Compile time: Apr 17 2023 14:31:53
I (437) cpu_start: ELF file SHA256: 429f1f7b7be7c0d8...
I (443) cpu_start: ESP-IDF: v4.4.4-dirty
I (449) heap_init: Initializing. RAM available for dynamic allocation:
I (456) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (462) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (468) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (474) heap_init: At 3FFD2558 len 0000DAA8 (54 KiB): DRAM
I (481) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (487) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (493) heap_init: At 40097EB8 len 00008148 (32 KiB): IRAM
I (501) esp_core_dump_flash: Init core dump to flash
I (506) esp_core_dump_flash: Found partition 'coredump' @ 110000 65536 bytes
E (513) esp_core_dump_flash: Incorrect size of core dump image: 270737568
luepad32 (C) 2016-2023 Ricardo Quesada and contributors.
Version: v3.7.0-rc0
BTStack: Copyright (C) 2017 BlueKitchen GmbH.
Platform: unijoysticle2
Unijoysticle: Board ID values: 1,1,1
Hardware detected: Unijoysticle2
I (595) gpio: GPIO[5]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (605) gpio: GPIO[12]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (615) gpio: GPIO[13]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (625) gpio: GPIO[14]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (635) gpio: GPIO[16]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (645) gpio: GPIO[17]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (655) gpio: GPIO[18]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (665) gpio: GPIO[19]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (675) gpio: GPIO[23]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (685) gpio: GPIO[25]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (695) gpio: GPIO[26]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (705) gpio: GPIO[27]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (715) gpio: GPIO[32]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (715) gpio: GPIO[33]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (725) gpio: GPIO[10]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
Max connected gamepads: 4
BR/EDR support: enabled
BLE support: enabled
Device ID SDP service record size: 64
Gap security level: 2
Periodic Inquiry: max=5, min=4, len=3
I (755) BTDM_INIT: BT controller compile version [8020d24]
I (765) system_api: Base MAC address is not set
I (765) system_api: read default base MAC address from EFUSE
I (775) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07
I (1335) console: Command history disabled

Type 'help' to get the list of commands.
Use UP/DOWN arrows to navigate through command history.
Press TAB when typing command name to auto-complete.

Your terminal application does not support escape sequences.

Line editing and history features are disabled.

On Windows, try using Putty instead.
bp32> BTstack up and running at 8C:AA:B5:93:7C:CA
HCI not ready, cannot send packet, will again try later. Current state idx=1
BTstack up and running on 8C:AA:B5:93:7C:CA.
BR/EDR scan -> 1
BLE scan -> 1
Unijoysticle: Using Amiga mouse emulation
unijoysticle: Bluetooth discovery mode is enabled
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 173 dBm
Creating device: 00:90:E1:F0:DB:08 (idx=0)
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 1, incoming:0
uni_bt_process_fsm: requesting name
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 205 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 203 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 193 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 204 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 194 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 204 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 197 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 204 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 201 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
Device found: 00:90:E1:F0:DB:08 with COD: 0x002504, pageScan 1, clock offset 0x5c3f, rssi 192 dBm
Device already added, waiting (current state=0x03)...
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 3, incoming:0
--> HCI_EVENT_REMOTE_NAME_REQUEST_COMPLETE
Name: 'REMAX RY-01'
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 4, incoming:0
uni_bt_process_fsm: Starting L2CAP connection
--> HCI_EVENT_CONNECTION_COMPLETE
SM_EVENT_PAIRING_STARTED
Identity resolving failed for 00:90:E1:F0:DB:08

--> HCI_EVENT_LINK_KEY_REQUEST:
--> HCI_EVENT_AUTHENTICATION_COMPLETE_EVENT: status=0, handle=0x0081
L2CAP_EVENT_CHANNEL_OPENED (channel=0x0041)
PSM: 0x0011, local CID=0x0041, remote CID=0x0040, handle=0x0081, incoming=0, local MTU=1691, remote MTU=672, addr=00:90:E1:F0:DB:08
HID Control opened, cid 0x41
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 10, incoming:0
uni_bt_process_fsm: Create L2CAP interrupt connection
L2CAP_EVENT_CHANNEL_OPENED (channel=0x0042)
PSM: 0x0013, local CID=0x0042, remote CID=0x0041, handle=0x0081, incoming=0, local MTU=1691, remote MTU=672, addr=00:90:E1:F0:DB:08
HID Interrupt opened, cid 0x42
Device 00:90:E1:F0:DB:08 is connected
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 12, incoming:0
uni_bt_process_fsm: starting SDP query
-----------> sdp_query_start()
Starting SDP VID/PID query for 00:90:E1:F0:DB:08
Vendor ID: 0x1949 - Product ID: 0x0402
Device detected as Android: 0x25
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 6, incoming:0
uni_bt_process_fsm: querying HID descriptor
Starting SDP HID-descriptor query for 00:90:E1:F0:DB:08
SDP HID Descriptor (144):
05 0C 09 01 A1 01 85 02 15 00 25 01 75 01 95 0A 09 EA 09 CD 09 B6 09 B5 09 E9 09 B8 09 95 0A 23 02 0A 24 02 09 40 81 02 95 01 75 06 81 03 C0 05 01 09 05 A1 01 85 07 09 01 A1 00 09 30 09 31 09 32 09 35 15 00 26 FF 00 75 08 95 04 81 02 C0 09 39 15 00 25 07 35 00 46 3B 01 65 14 75 04 95 01 81 42 75 04 95 01 81 01 05 09 19 01 29 0F 15 00 25 01 75 01 95 10 81 02 05 02 15 00 26 FF 00 09 C4 09 C5 95 02 75 08 81 02 75 08 95 01 81 01 C0
<----------- sdp_query_end()
uni_bt_process_fsm, bd addr:00:90:E1:F0:DB:08, state: 8, incoming:0
uni_bt_process_fsm: Device is ready
Device setup (00:90:E1:F0:DB:08) is complete
unijoysticle: device 00:90:E1:F0:DB:08 has new gamepad seat: 2
mice timers enabled/disabled: port A=0, port B=0
unijoysticle: swap seat for 00:90:E1:F0:DB:08: 2 -> 1
unijoysticle: device 00:90:E1:F0:DB:08 has new gamepad seat: 1
mice timers enabled/disabled: port A=0, port B=0
unijoysticle: device 00:90:E1:F0:DB:08 has new gamepad seat: 3
unijoysticle: Gamepad mode = enhanced
mice timers enabled/disabled: port A=0, port B=0
Connected devices:
idx=0:
btaddr: 00:90:E1:F0:DB:08
bt: handle=129 (ACL), ctrl_cid=0x0041, intr_cid=0x0042, cod=0x00002504, flags=0x00003f00, incoming=0
model: vid=0x1949, pid=0x0402, model='Android', name='REMAX RY-01'
unijoysticle: type=gamepad, mode=enhanced, seat=0x03

--> Stop scanning for new gamepads
BR/EDR scan -> 0
BLE scan -> 0
unijoysticle: Bluetooth discovery mode is disabled
unijoysticle: device 00:90:E1:F0:DB:08 has new gamepad seat: 1
unijoysticle: Gamepad mode = normal
mice timers enabled/disabled: port A=0, port B=0
Connected devices:
idx=0:
btaddr: 00:90:E1:F0:DB:08
bt: handle=129 (ACL), ctrl_cid=0x0041, intr_cid=0x0042, cod=0x00002504, flags=0x00003f00, incoming=0
model: vid=0x1949, pid=0x0402, model='Android', name='REMAX RY-01'
unijoysticle: type=gamepad, mode=normal, seat=0x01

BR/EDR scan -> 1
BLE scan -> 1
unijoysticle: Bluetooth discovery mode is enabled

from bluepad32.

from bluepad32.

from bluepad32.

you are using the "unijoysticle" platform. that's meat to be used for Unijjoysticle boards:
https://retro.moe/unijoysticle2/
is that what you want?

my guess is that you need the arduino platform. See:
https://gitlab.com/ricardoquesada/bluepad32/-/blob/main/docs/architecture.md

If so, you have to use the Arduino builds. See:
https://gitlab.com/ricardoquesada/bluepad32/-/blob/main/docs/plat_arduino.md

And the Arduino example prints the pressed buttons

from bluepad32.

can i build the project

from bluepad32.

Copy the content of sketch.cpp to main.c then build

ohhhh... good to know. I'll fix it tonight.

from bluepad32.

just double-checking, which ESP-IDF version are you using?
You should be using v4.4.x (not v5.x, not v4.3...)

from bluepad32.

from bluepad32.

which OS are you using? Linux? mac?... which version?

from bluepad32.

it is github work flow , i just delete main.c then rename sketch.cpp to main.c

all default settings

win11 amd bluepad3.7.0

from bluepad32.

mmm... seems to be compiling ok for me. using Github actions as well:

https://github.com/ricardoquesada/esp-idf-arduino-bluepad32-template/actions/runs/4728529709/jobs/8390158992

compare my repo with yours, and see whether there are any differences

from bluepad32.

At first i thought if i want to compile hex for arduino

i need to fork your repo then delete main .c and rename sketch.cpp to main.c

actually just need to fork and compile . now it working well on my esp32 board.

from bluepad32.

https://github.com/bihailantian655/esp-idf-arduino-bluepad32-template/actions/runs/4750290071/jobs/8438332288 .

just a small question about github action ，How to change the command to run in the current directory

i want to merge the bin files , according to this instruction

https://docs.espressif.com/projects/esptool/en/latest/esp32/esptool/basic-commands.html

but Run cd build or cd ./build

Run pwd

still is

/home/runner/work/esp-idf-arduino-bluepad32-template/esp-idf-arduino-bluepad32-template

Does not change the directory

from bluepad32.

so, is it working oK? can close this bug?

for github actions, better ask in the github action forum, but I guess you can put multiple commands in one line like: cd my_folder && ./build or something like that

from bluepad32.

closing it.

from bluepad32.