Thread runs function but it is still sync

[sir-user]

Hello Everyone,

I made my custom ESP32 firmware and upload it to my custom ESP32 Board but Thread does not work right. I don't know why it does not work well. The problem is it creates threads but it does not work async, it is still sync.

That is how suppose to be thread:

Main App  Line   >   --------------------------Thread Request-------------------------------------------------------------->
                                                    |                                                              |
Thread       Line                                   --------------------------------------------------------- ThreadEnds

My thread behave is

Main App  Line   >   --------------------------Thread Request                                                     -------->
                                                   |                                                              | 
Thread       Line                                  ---------------------------------------------------------- ThreadEnds

So it works like just no threading. Just normal processing.

Also, I guess my bin file's size is allocated to CPU1 from CPU0. How could I fix it? Even I do not add any module, It still allocates to CPU1.

There is my code below, I wanted to test my thread function and code. So I play a wav file which is around 3 seconds but to test it I wait 500 ms then I turn it of by change it's status.

Thank you in advance for your help,
Volkan

My Code:

from libs import WavP
import _thread
from time import sleep_ms

Plyr = WavP.WavP()

_thread.start_new_thread(Plyr.play_wav,("wav_files/at.wav",))

sleep_ms(500)

Plyr.status = 0

There is console return when push the reset button:

ets Jun  8 2016 00:22:57

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:4728
load:0x40078000,len:14876
ho 0 tail 12 room 4
load:0x40080400,len:3368
entry 0x400805cc
I (678) cpu_start: Pro cpu up.
I (678) cpu_start: Starting app cpu, entry point is 0x40081400
I (0) cpu_start: App cpu up.
D (686) clk: RTC_SLOW_CLK calibration value: 3574938
I (697) cpu_start: Pro cpu start user code
I (697) cpu_start: cpu freq: 240000000 Hz
I (697) cpu_start: Application information:
I (702) cpu_start: Compile time:     Oct 23 2023 13:38:20
I (708) cpu_start: ELF file SHA256:  99794b96e9546fac...
I (714) cpu_start: ESP-IDF:          v5.0.2
I (719) cpu_start: Min chip rev:     v0.0
I (724) cpu_start: Max chip rev:     v3.99 
I (728) cpu_start: Chip rev:         v1.0
D (733) memory_layout: Checking 12 reserved memory ranges:
D (739) memory_layout: Reserved memory range 0x3ff81ff0 - 0x3ff82000
D (745) memory_layout: Reserved memory range 0x3ffae000 - 0x3ffae6e0
D (752) memory_layout: Reserved memory range 0x3ffae6e0 - 0x3ffaff10
D (758) memory_layout: Reserved memory range 0x3ffb0000 - 0x3ffb6388
D (764) memory_layout: Reserved memory range 0x3ffb8000 - 0x3ffb9a20
D (771) memory_layout: Reserved memory range 0x3ffbdb28 - 0x3ffbdb5c
D (777) memory_layout: Reserved memory range 0x3ffbdb60 - 0x3ffcac70
D (784) memory_layout: Reserved memory range 0x3ffe0000 - 0x3ffe0440
D (790) memory_layout: Reserved memory range 0x3ffe3f20 - 0x3ffe4350
D (797) memory_layout: Reserved memory range 0x40070000 - 0x40078000
D (803) memory_layout: Reserved memory range 0x40078000 - 0x40080000
D (809) memory_layout: Reserved memory range 0x40080000 - 0x4009f21c
D (816) memory_layout: Building list of available memory regions:
D (822) memory_layout: Available memory region 0x3ffaff10 - 0x3ffb0000
D (829) memory_layout: Available memory region 0x3ffb6388 - 0x3ffb8000�[0m
D (835) memory_layout: Available memory region 0x3ffb9a20 - 0x3ffbdb28
D (842) memory_layout: Available memory region 0x3ffcac70 - 0x3ffcc000
D (848) memory_layout: Available memory region 0x3ffcc000 - 0x3ffce000
D (855) memory_layout: Available memory region 0x3ffce000 - 0x3ffd0000
D (862) memory_layout: Available memory region 0x3ffd0000 - 0x3ffd2000
D (868) memory_layout: Available memory region 0x3ffd2000 - 0x3ffd4000
D (875) memory_layout: Available memory region 0x3ffd4000 - 0x3ffd6000
D (881) memory_layout: Available memory region 0x3ffd6000 - 0x3ffd8000
D (888) memory_layout: Available memory region 0x3ffd8000 - 0x3ffda000
D (895) memory_layout: Available memory region 0x3ffda000 - 0x3ffdc000
D (901) memory_layout: Available memory region 0x3ffdc000 - 0x3ffde000
D (908) memory_layout: Available memory region 0x3ffde000 - 0x3ffe0000
D (914) memory_layout: Available memory region 0x3ffe0440 - 0x3ffe3f20
D (921) memory_layout: Available memory region 0x3ffe4350 - 0x3ffe8000
D (928) memory_layout: Available memory region 0x3ffe8000 - 0x3fff0000
D (934) memory_layout: Available memory region 0x3fff0000 - 0x3fff8000�[0m
D (941) memory_layout: Available memory region 0x3fff8000 - 0x3fffc000
D (947) memory_layout: Available memory region 0x3fffc000 - 0x40000000
D (954) memory_layout: Available memory region 0x4009f21c - 0x400a0000
I (961) heap_init: Initializing. RAM available for dynamic allocation:
D (968) heap_init: New heap initialised at 0x3ffaff10
I (973) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
D (979) heap_init: New heap initialised at 0x3ffb6388
I (984) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
D (990) heap_init: New heap initialised at 0x3ffb9a20
I (995) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
D (1001) heap_init: New heap initialised at 0x3ffcac70
I (1007) heap_init: At 3FFCAC70 len 00015390 (84 KiB): DRAM
I (1013) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (1019) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
D (1026) heap_init: New heap initialised at 0x4009f21c
I (1031) heap_init: At 4009F21C len 00000DE4 (3 KiB): IRAM
D (1038) intr_alloc: Connected src 46 to int 2 (cpu 0)
D (1043) spi_flash: trying chip: issi
D (1046) spi_flash: trying chip: gd
D (1050) spi_flash: trying chip: mxic
D (1053) spi_flash: trying chip: winbond�[0m
D (1057) spi_flash: trying chip: generic
I (1061) spi_flash: detected chip: generic
I (1066) spi_flash: flash io: dio
D (1070) cpu_start: calling init function: 0x401d4150
D (1075) cpu_start: calling init function: 0x401d3c6c
D (1080) cpu_start: calling init function: 0x40157a4c
D (1086) cpu_start: calling init function: 0x40155c34
W (1091) i2s(legacy): legacy i2s driver is deprecated, please migrate to use driver/i2s_std.h, driver/i2s_pdm.h or driver/i2s_tdm.h
D (1103) cpu_start: calling init function: 0x4015263c
W (1108) rmt(legacy): legacy driver is deprecated, please migrate to `driver/rmt_tx.h` and/or `driver/rmt_rx.h`
D (1119) cpu_start: calling init function: 0x40151234
W (1124) ADC: legacy driver is deprecated, please migrate to `esp_adc/adc_oneshot.h`
D (1133) cpu_start: calling init function: 0x400d7c68
D (1138) cpu_start: calling init function: 0x400d2b18
D (1143) cpu_start: calling init function: 0x400d1f68
D (1148) cpu_start: calling init function: 0x400d5804 on core: 0
D (1154) intr_alloc: Connected src 17 to int 3 (cpu 0)
D (1159) cpu_start: calling init function: 0x400d28c4 on core: 0
D (1177) intr_alloc: Connected src 24 to int 9 (cpu 0)
�[0;32mI (1177) cpu_start: Starting scheduler on PRO CPU.
D (0) intr_alloc: Connected src 25 to int 2 (cpu 1)
I (0) cpu_start: Starting scheduler on APP CPU.
D (1198) heap_init: New heap initialised at 0x3ffe0440
D (1198) heap_init: New heap initialised at 0x3ffe4350
D (1208) intr_alloc: Connected src 16 to int 12 (cpu 0)
D (1228) intr_alloc: Connected src 34 to int 3 (cpu 1)
D (1228) event: created task for loop 0x3ffbcef0
D (1228) event: running task for loop 0x3ffbcef0
D (1228) event: created event loop 0x3ffbcef0
D (1238) intr_alloc: Connected src 22 to int 4 (cpu 1)
I (1408) pm: Frequency switching config: CPU_MAX: 240, APB_MAX: 240, APB_MIN: 240, Light sleep: DISABLED

[shydr15]

Hi Volkan,

Were you able to solve the issue, I am also facing same issue.

Thank you

[sir-user]

Hi Saddamheydarov

No, I could not find any answer. I think my micropython.bin firmware use CPU0 and CPU1 at the same time. So when I try to thread, thread just work in order. main app and thread do not work at the same time. Main app just wait until thread ends.

I will try to build another bin file, try to solve allocation problem(CPU0 and CPU1 using problem).

I will keep you informed if there are any changes.

[peterhinch]

Threading on ESP32 is not multiprocessing. MicroPython runs on one core on ESP32. There should still be concurrency via pre-emptive task switching.

[sir-user]

I do not understand it well. When I upload official firmware from micropython.org, thread works fine but for the firmware I made, thread does not work like supposed to be.

[shariltumin]

According to your test script, the official firmware gives you 500ms of sound, but your custom firmware gives you the full 3s?

Please try this simple script:

import _thread as th
from time import sleep_ms

cnt = 20

def fun1():
    global cnt
    while cnt > 10:
       print(f'fun1: {cnt}')
       sleep_ms(200)
       cnt -= 1
    print(f'fun1 terminating')

th.start_new_thread(fun1,())

sleep_ms(500)

cnt = 0

If thread is working, you will get something similar to this result when running in REPL Ctrl+E, Ctrl+D:

1073737620
fun1: 20
fun1: 19
fun1: 18
>>> fun1 terminating

The test was performed using the custom firmware MicroPython v1.22.0-preview.1.g523284777.dirty with ESP32-S2FN4R2.