Examples broken at runtime. #23
Comments
|
I cannot reproduce that exception on my side on ESP32-S3 I do see some TLS errors sometimes - but sometimes it just works |
|
I'm on toolchain Here's the steps to reproduce on my side. It's weird because it used to work at some point.
git clone https://github.com/esp-rs/esp-mbedtls
SSID=<SSID> PASSWORD=<SSID> cargo +esp run --example sync_server --target xtensa-esp32s3-none-elf -F esp32s3,esp-wifi/wifi-logs
|
|
Mhhh seems like in our 1.74 build the c-variadics are broken, again. e.g. for the first string it tries to get it e.g. reads the address Works fine with 1.73.0.1 cc @MabezDev |
|
I'm so sorry that's completely my bad. I forgot to add the commit to 1.74, because I was looking at the patch set from 1.73.0.0, instead of 1.73.0.1 🤦. I'll fix that and get a release out soon. |
|
Alright, I'm using Examples run without any issue on the Now, I'm only facing runtime issues during a connection. When I run the SSID=<SSID> PASSWORD=<PASS> cargo +esp run --release --example sync_server --target xtensa-esp32s3-none-elf -F esp32s3I get the following error during a connection: INFO - esp-wifi configuration Config { rx_queue_size: 10, tx_queue_size: 10, static_rx_buf_num: 10, dynamic_rx_buf_num: 32, static_tx_buf_num: 0, dynamic_tx_buf_num: 32, ampdu_rx_enable: 0, ampdu_tx_enable: 0, amsdu_tx_enable: 0, rx_ba_win: 6, max_burst_size: 1, country_code: "CN", country_code_operating_class: 0, mtu: 1492, heap_size: 112640, tick_rate_hz: 100, listen_interval: 3, beacon_timeout: 6, ap_beacon_timeout: 300, failure_retry_cnt: 1, scan_method: 0 }
Call wifi_connect
Wait to get connected
Wait to get an ip address
Got ip Ok(IpInfo { ip: 192.168.69.165, subnet: Subnet { gateway: 192.168.69.1, mask: Mask(24) }, dns: Some(192.168.69.16), secondary_dns: None })
We are connected!
Point your browser to https://192.168.69.165/
New connection
!! A panic occured in 'examples/sync_server.rs', at line 198, column 21
PanicInfo {
payload: Any { .. },
message: Some(
MbedTlsError(-17280),
),
location: Location {
file: "examples/sync_server.rs",
line: 198,
col: 21,
},
can_unwind: true,
}The error code is for |
|
I can reproduce it. I also tried different versions of the toolchain and very few different (recent) commits of esp-mbedtls Oh wait ... seems like Aaaaand I can also get the current main to work when copying the pre-compiled libs from If it's reproducible on your side then there is something wrong with how mbedtls is built for Xtensa while it's fine for RISC-V |
|
I've tested with the pre-compiled libraries from before we refactored the build scripts to use xtasks and it works. The issue effectively seems to be from the way we build mbedtls for Xtensa, introduced in #15 |
|
I'm going to close this because it has been fixed in #24 after recompiling using clang |
I've tried to run the following examples after a clean git clone and they all fail due to various issues:
EDIT: After further testing, the problem seems to occur on Xtensa targets. It had issues on
esp32s3but withesp32c3everything is running without any failure.Here's the output from running async_client:
Waiting to get IP address... Got IP: 192.168.69.165/24 connecting... Start tls connect Exception occured 'InstrProhibited' Context PC=0x00000000 PS=0x00060a10 0x00000000 - XT_STK_PC at ??:?? 0x00060a10 - PS_WOE at ??:?? A0=0x8037b2eb A1=0x3fc9b900 A2=0x00000001 A3=0x00000000 A4=0x3fcbbfe0 0x8037b2eb - _rtc_fast_data_end at ??:?? 0x3fc9b900 - _ZN8esp_wifi7preempt10TASK_STACK17hc849bc2d8dfdc35eE.llvm.8558853931319064652 at ??:?? 0x00000001 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x3fcbbfe0 - g_pm at ??:?? A5=0x3fcbbfe0 A6=0x3fcef940 A7=0x1d800160 A8=0x820a44aa A9=0x00000000 0x3fcbbfe0 - g_pm at ??:?? 0x3fcef940 - g_osi_funcs_p at ??:?? 0x1d800160 - PS_WOE at ??:?? 0x820a44aa - _rtc_fast_data_end at ??:?? 0x00000000 - XT_STK_PC at ??:?? A10=0x00019000 A11=0x00000001 A12=0x3fc9b900 A13=0xeeeeeeef A14=0x00000000 0x00019000 - RESERVE_ICACHE at ??:?? 0x00000001 - XT_STK_PC at ??:?? 0x3fc9b900 - _ZN8esp_wifi7preempt10TASK_STACK17hc849bc2d8dfdc35eE.llvm.8558853931319064652 at ??:?? 0xeeeeeeef - _rtc_fast_data_end at ??:?? 0x00000000 - XT_STK_PC at ??:?? A15=0x00000006 0x00000006 - XT_STK_PS at ??:?? SAR=00000004 EXCCAUSE=0x00000014 EXCVADDR=0x00000000 0x00000014 - XT_STK_A3 at ??:?? 0x00000000 - XT_STK_PC at ??:?? LBEG=0x00000000 LEND=0x00000000 LCOUNT=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? THREADPTR=0x00000000 0x00000000 - XT_STK_PC at ??:?? SCOMPARE1=0x00000001 0x00000001 - XT_STK_PC at ??:?? BR=0x00000000 0x00000000 - XT_STK_PC at ??:?? ACCLO=0x00000000 ACCHI=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? M0=0x00000000 M1=0x00000000 M2=0x00000000 M3=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? F64R_LO=0x00000000 F64R_HI=0x00000000 F64S=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? FCR=0x00000000 FSR=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? F0=0x00000000 F1=0x00000000 F2=0x00000000 F3=0x00000000 F4=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? F5=0x00000000 F6=0x00000000 F7=0x00000000 F8=0x00000000 F9=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? F10=0x00000000 F11=0x00000000 F12=0x00000000 F13=0x00000000 F14=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? 0x00000000 - XT_STK_PC at ??:?? F15=0x00000000 0x00000000 - XT_STK_PC at ??:?? 0x4003d024 0x4003d024 - rom_rx_gain_force at ??:?? 0x4037a49c 0x4037a49c - ppTask at ??:?? 0x42021f84 0x42021f84 - core::sync::atomic::atomic_load at /home/anthony/.rustup/toolchains/esp/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:3184 0x40000000 0x40000000 - ets_rom_layout_p at ??:??The text was updated successfully, but these errors were encountered: