-
Notifications
You must be signed in to change notification settings - Fork 115
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.
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
ESP32-S3 - CORRUPT HEAP: Bad tail after wifi connection. #398
Comments
Wondering why you changed the RTOS config? |
Because I got:
In deeper mening, no, I don't know why. |
ok. This port was done by @philippe44 so he can possibly help. |
To be more specific the board is ESP32-S3-DevKitC-1-N16R8V also I build image again and I saw in logs:
Any clue? |
Yes, you must change rtos config on all platforms per message. Why doesn't it work on the s3, I don't know. I had the same issue the first time with my s3 and I did something in the build to fix it but I can't remember why, sorry. |
I have a custom build in my fork that I build in Visual Studio Code. |
@wizmo2 thanks! I managed to successful flash esp32-s3 with current branch and set wifi creds but I have another error with DAC i2c:
and for Airplay:
|
Looks like a NVS configuration issue. Check you i2c settings for the DAC and the auxiliaries. If you are using my build, it could also be the ADC configuration (plus airplay is disabled). |
I used the master-v4.3 branch, sdkconfig from 4.4-s3 and some parameters from your cfg.
My gole is to run on S3 with PCM5012 and Airplay. |
Hey,
I have problem with ESP32-S3, device just crash after wifi connection in AP Mode with log CORRUPT HEAP: Bad tail at 0x3d81cbef. Expected 0xbaad5678 got 0xbaad5600
I build image for ESP32-S3-DEVKIT using:
python3 -m esptool -p /dev/cu.usbmodem14201 -b 460800 --before default_reset --after hard_reset --chip esp32-s3 write_flash --flash_mode dio --flash_size detect --flash_freq 80m 0x0 bootloader.bin 0x8000 partition-table.bin 0xd000 ota_data_initial.bin 0x10000 recovery.bin 0x150000 squeezelite.bin
Logs from usb:
Any ideas?
Thanks!
The text was updated successfully, but these errors were encountered: