Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

in state connected by ble5.0, backlight of st7789 lcd is blink. (IDFGH-9076) #10479

Open
3 tasks done
hyu7000 opened this issue Jan 3, 2023 · 8 comments
Open
3 tasks done

in state connected by ble5.0, backlight of st7789 lcd is blink. (IDFGH-9076) #10479

hyu7000 opened this issue Jan 3, 2023 · 8 comments
Assignees
@xiewenxiang
Labels
Awaiting Response awaiting a response from the author Resolution: Cannot Reproduce Issue cannot be reproduced Status: Done Issue is done internally

Comments

@hyu7000
Copy link

hyu7000 commented Jan 3, 2023

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

v5.0 7f5ecbe

Operating System used.

Windows

How did you build your project?

VS Code IDE

If you are using Windows, please specify command line type.

None

Development Kit.

ESP32s3 wroom 1 devkit

Power Supply used.

USB

What is the expected behavior?

in state connected by ble5.0, st7789 lcd remains turned off.

What is the actual behavior?

in state connected by ble5.0, st7789 lcd repeat turn on and turn off.

if i change connection interval, repeat cycle of onoff was changed.

the below video show when connection interval is 500ms.
https://user-images.githubusercontent.com/82933946/210317688-ec8c64f7-82db-4036-a15f-87244e0df73a.mp4

the below video show when connection interval is 100ms.
https://user-images.githubusercontent.com/82933946/210318034-95402d35-cacc-4f5e-9063-18e3167a3ef5.mp4

if it not connected ble, lcd completly turn off.

Steps to reproduce.

  1. Step
    in ble50_security_server project, set bluetooth modem sleep
    and add this code at gatts_profile_event_handler()
case ESP_GATTS_CONNECT_EVT:
            ESP_LOGI(GATTS_TABLE_TAG, "ESP_GATTS_CONNECT_EVT");
            /* start security connect with peer device when receive the connect event sent by the master */
            esp_ble_set_encryption(param->connect.remote_bda, ESP_BLE_SEC_ENCRYPT_MITM);
            
            memcpy(conn_params.bda, param->connect.remote_bda, sizeof(esp_bd_addr_t));
            conn_params.latency = 0;
            conn_params.max_int = 0x50;   
            conn_params.min_int = 0x50;    
            conn_params.timeout = 400;    

            esp_ble_gap_update_conn_params(&conn_params);

            break;
  1. Step
    connect st7789 lcd by spi connection.
    and add this code at app_main()
#define LCD_PIN_NUM_BK_LIGHT    7
...
ESP_ERROR_CHECK(esp_lcd_panel_disp_on_off(panel_handle, false)); 
 gpio_set_level(LCD_PIN_NUM_BK_LIGHT, false);
  1. Step
    try to connect to a phone

Debug Logs.

No response

More Information.

gpio7 of esp32s3 was connected backlight pin(BLK) like below image

1

i can't find solution to solve this issue in the document and esp32 forum, git.

is there keyword to find solution?
@hyu7000 hyu7000 added the Type: Bug bugs in IDF label Jan 3, 2023
@espressif-bot espressif-bot added the Status: Opened Issue is new label Jan 3, 2023
@github-actions github-actions bot changed the title in state connected by ble5.0, backlight of st7789 lcd is blink. in state connected by ble5.0, backlight of st7789 lcd is blink. (IDFGH-9076) Jan 3, 2023
@suda-morris
Copy link
Collaborator

Maybe you need to attach an oscilloscope to the GPIO7 to see what happens on that GPIO. Is it possible that the power supply is not sufficient?

@hyu7000
Copy link
Author

hyu7000 commented Jan 3, 2023 •
edited
Loading

@suda-morris when i use oscilloscope, this image was shown

Interval is 100ms

20230103_172913

then if i disconnect ble, graph indicated 0V.

i don't know why it's 3.3v if it's connected ble.

I think power is sufficient. It shows the same symptoms when i use power supply or usb.

when i use esp32-arduino, though it connected, lcd did not blink.

@suda-morris
Copy link
Collaborator

what's the log output? is your program crashed somehow? are you sure GPIO7 is not used by other purpose in your program?

@suda-morris suda-morris removed the Type: Bug bugs in IDF label Jan 4, 2023
@hyu7000
Copy link
Author

hyu7000 commented Jan 4, 2023 •
edited
Loading

@suda-morris there is no shut down and crash ,disconnection, other config of GPIO7.

though it blink st7789 lcd, BLE work well .the issus is st7789 lcd

and if i except for code related to BLE and upload, display work well without blink.

this log is in vscode monitor.

I (43) boot: ESP-IDF v5.0-dirty 2nd stage bootloader
I (43) boot: compile time 14:30:45
I (43) boot: chip revision: v0.1
I (45) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (52) boot.esp32s3: Boot SPI Speed : 80MHz
I (57) boot.esp32s3: SPI Mode       : DIO
I (62) boot.esp32s3: SPI Flash Size : 8MB
I (67) boot: Enabling RNG early entropy source...
I (72) boot: Partition Table:
I (76) boot: ## Label            Usage          Type ST Offset   Length
I (83) boot:  0 nvs              WiFi data        01 02 00009000 00005000
I (90) boot:  1 otadata          OTA data         01 00 0000e000 00002000
I (98) boot:  2 app0             OTA app          00 10 00010000 00300000
I (105) boot:  3 spiffs           Unknown data     01 82 00310000 000f0000
I (113) boot: End of partition table
I (117) boot_comm: chip revision: 1, min. application chip revision: 0
I (124) esp_image: segment 0: paddr=00010020 vaddr=3c090020 size=24160h (147808) map
I (149) esp_image: segment 1: paddr=00034188 vaddr=3fc99800 size=03ff0h ( 16368) load
I (152) esp_image: segment 2: paddr=00038180 vaddr=40374000 size=07e98h ( 32408) load
I (160) esp_image: segment 3: paddr=00040020 vaddr=42000020 size=80f88h (528264) map
I (223) esp_image: segment 4: paddr=000c0fb0 vaddr=4037be98 size=0d8bch ( 55484) load
I (232) esp_image: segment 5: paddr=000ce874 vaddr=50000000 size=00010h (    16) load
I (232) esp_image: segment 6: paddr=000ce88c vaddr=600fe000 size=00034h (    52) load
I (246) boot: Loaded app from partition at offset 0x10000
I (246) boot: Disabling RNG early entropy source...
I (260) cpu_start: Pro cpu up.
I (260) cpu_start: Starting app cpu, entry point is 0x403755f4
0x403755f4: call_start_cpu1 at C:/Users/hk910/esp/esp-idf/components/esp_system/port/cpu_start.c:142

I (0) cpu_start: App cpu up.
I (325) cpu_start: Pro cpu start user code
I (325) cpu_start: cpu freq: 160000000 Hz
I (325) cpu_start: Application information:
I (328) cpu_start: Project name:     CremakerWatch
I (333) cpu_start: App version:      1
I (338) cpu_start: Compile time:     Jan  3 2023 14:31:09
I (344) cpu_start: ELF file SHA256:  d407910d28f4afa8...
I (350) cpu_start: ESP-IDF:          v5.0-dirty
I (355) heap_init: Initializing. RAM available for dynamic allocation:
I (362) heap_init: At 3FCA1B20 len 00047BF0 (286 KiB): D/IRAM
I (369) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DRAM
I (375) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (382) heap_init: At 600FE034 len 00001FCC (7 KiB): RTCRAM
I (389) spi_flash: detected chip: generic
I (393) spi_flash: flash io: dio
I (408) sleep: Configure to isolate all GPIO pins in sleep state
I (408) coexist: coexist rom version e7ae62f
I (409) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (437) pm: Frequency switching config: CPU_MAX: 80, APB_MAX: 80, APB_MIN: 40, Light sleep: ENABLED
I (437) sleep: Enable automatic switching of GPIO sleep configuration
I (447) sleep: Code start at 42000020, total 515.88 KiB, data start at 3c090020, total 144.34 KiB
W (457) BT_INIT: esp_bt_controller_mem_release not implemented, return OK
I (467) BT_INIT: BT controller compile version [76c24c9]
I (477) phy_init: phy_version 503,13653eb,Jun  1 2022,17:47:08
I (517) system_api: Base MAC address is not set
I (517) system_api: read default base MAC address from EFUSE
I (517) BT_INIT: Bluetooth MAC: 68:b6:b3:29:af:ca

I (527) BLE: ble_init init bluetooth
I (587) BLE: ESP_GATTS_REG_EVT
I (597) BLE: The number handle = 8
I (597) BLE: ESP_GAP_BLE_SET_LOCAL_PRIVACY_COMPLETE_EVT, tatus = 0
I (607) BLE: ESP_GAP_BLE_EXT_ADV_SET_PARAMS_COMPLETE_EVT status 0
I (607) BLE: ESP_GAP_BLE_EXT_ADV_DATA_SET_COMPLETE_EVT status 0
I (617) BLE: ESP_GAP_BLE_EXT_ADV_START_COMPLETE_EVT, status = 0
I (617) gpio: GPIO[7]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (627) gpio: GPIO[9]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (637) gpio: GPIO[6]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (45217) BLE: ESP_GAP_BLE_ADV_TERMINATED_EVT, status = 0
I (45217) BLE: ADV successfully ended with a connection being created
I (45357) BLE: ESP_GATTS_CONNECT_EVT
I (45897) BLE: update connection params status = 0, min_int = 80, max_int = 80,conn_int = 6,latency = 0, timeout = 500
W (45987) BT_SMP: FOR LE SC LTK IS USED INSTEAD OF STK
I (46017) BLE: key type = ESP_LE_KEY_LENC
I (46017) BLE: key type = ESP_LE_KEY_PENC
I (46017) BLE: key type = ESP_LE_KEY_LID
I (46037) BLE: key type = ESP_LE_KEY_PID
I (46107) BLE: remote BD_ADDR: 51d5b688d65d
I (46107) BLE: address type = 1
I (46107) BLE: pair status = success
I (46117) BLE: auth mode = ESP_LE_AUTH_REQ_SC_BOND
I (46117) BLE: Bonded devices number : 1
I (46117) BLE: 51 d5 b6 88 d6 5d 
I (46357) BLE: update connection params status = 0, min_int = 0, max_int = 0,conn_int = 80,latency = 0, timeout = 400

this log is in nRFConnect app

nRF Connect, 2023-01-04
ESP_BLE50_SERVER (68:B6:B3:29:AF:CA)
D	22:05:30.086	gatt.close()
D	22:05:30.090	wait(200)
V	22:05:30.291	Connecting to 68:B6:B3:29:AF:CA...
D	22:05:30.291	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	22:05:30.766	[Server callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I	22:05:30.766	[Server] Device with address 68:B6:B3:29:AF:CA connected
D	22:05:30.828	[Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I	22:05:30.828	Connected to 68:B6:B3:29:AF:CA
V	22:05:30.843	Discovering services...
D	22:05:30.843	gatt.discoverServices()
D	22:05:30.887	[Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
D	22:05:30.926	[Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDING (11)
I	22:05:31.356	Connection parameters updated (interval: 7.5ms, latency: 0, timeout: 5000ms)
D	22:05:31.736	[Callback] Services discovered with status: 0
I	22:05:31.736	Services discovered
V	22:05:31.742	Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
- Central Address Resolution [R] (0x2AA6)
Unknown Service (000000ff-0000-1000-8000-00805f9b34fb)
- Unknown Characteristic [N R W] (0000ff01-0000-1000-8000-00805f9b34fb)
   Client Characteristic Configuration (0x2902)
- Unknown Characteristic [R] (0000ff02-0000-1000-8000-00805f9b34fb)
- Unknown Characteristic [W] (0000ff03-0000-1000-8000-00805f9b34fb)
D	22:05:31.743	gatt.setCharacteristicNotification(00002a05-0000-1000-8000-00805f9b34fb, true)
D	22:05:31.745	gatt.setCharacteristicNotification(0000ff01-0000-1000-8000-00805f9b34fb, true)
I	22:05:31.823	Connection parameters updated (interval: 100.0ms, latency: 0, timeout: 4000ms)
D	22:05:32.172	[Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDED (12)
I	22:05:32.172	Device bonded

when i add this code, st7789 LCD no longer blink.

gpio_sleep_sel_dis(LCD_PIN_NUM_BK_LIGHT);

but i don't know what role SLP_SEL play.

I'm not sure if it's okay to use this function.

@hyu7000
Copy link
Author

hyu7000 commented Jan 5, 2023 •
edited
Loading

when i add gpio_sleep_sel_dis(LCD_PIN_NUM_BK_LIGHT); and gpio_sleep_sel_en(LCD_PIN_NUM_BK_LIGHT);, it work well.

but, current cumsumption is increasing. ( about 10mA -> about 30mA )

@suda-morris
Copy link
Collaborator

Okay, now I see it's expected behavior because you enabled the CONFIG_PM_SLP_DISABLE_GPIO option, which will isolate your LCD backlight GPIO in the esp_sleep_config_gpio_isolate function. If you call gpio_sleep_sel_dis for that GPIO, esp_sleep_config_gpio_isolate will have no effect on that GPIO.

@hyu7000
Copy link
Author

hyu7000 commented Jan 7, 2023

if gpio_sleep_sel_dis(); is enable, power comsumption is higher than i expect.

so i tested to reduce current consumption without gpio_sleep_sel_dis();

i found that when connection interval is in 10~35ms, it is work well without gpio_sleep_sel_dis();

at this time, there is no blink.

but when connection interval is over than 40ms, it blink again.

and i want to increase interval to reduce power consumption.

@esp-cjh
Copy link
Contributor

esp-cjh commented Feb 26, 2024

@hyu7000 Does this issue still exist in the latest IDF version?

@espressif-bot espressif-bot added the Awaiting Response awaiting a response from the author label Feb 28, 2024
@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: Cannot Reproduce Issue cannot be reproduced and removed Status: Opened Issue is new labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xiewenxiang xiewenxiang

Labels
Awaiting Response awaiting a response from the author Resolution: Cannot Reproduce Issue cannot be reproduced Status: Done Issue is done internally
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@suda-morris @xiewenxiang @espressif-bot @hyu7000 @esp-cjh