-
Notifications
You must be signed in to change notification settings - Fork 22
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
Feature: ESP32-S3 #112
Comments
Please try the branch fix_20ms_chunk_size_bug. Latest bug fixes and updates ar in there. They wilI be merged to master soon but there still has to be some testing. I don't know about S3 but there is a template sdkconfig for S2 which also doesn't have APLL. Maybe you can work your way from there |
Thanks for the feedback. This has already helped me, but it gets stuck in the I think it's somewhere along the line:
Do you have any advice? Thank you very much! |
Not sure if this could be a problem here, but in this branch there has been an upgrade to IDF v5.1.5 Also it dies at HAL init, which codec are you using? |
Thank you for your support. I have updated to version v5.1.5 and started fresh again. Unfortunately, nothing has changed. I have also increased the debug log, but after the HAL: INIT I see nothing. I assume that the codec means the audio board. I am using the TAS5805M here. (ESP32-S3 Louder) |
I'm sorry, I feel stupid. The GPIO ports have changed between the ESP32 version and the ESP32-S3. However, it now aborts after the following:
|
Is s3 a single core cpu? If so you might need to adjust the assigned core IDs in the task creation functions? |
The Espressif documentation specifies the following processor The TAS5805M power down pin 33 (should be 17) is also wrong, but can I find the configuration for it? |
Search for this line, Edit: Ok, saw your post about cpu architecture just now. So there is a second core indeed... |
You can change the pinout from menuconfig audio hal |
normal boot log should look like this, so you are good until it fails...
seems like it fails somewhere in player_setup_i2s |
Just tried it here:
|
@luar123 you are right. I'll change these Did you try increasing CONFIG_FREERTOS_IDLE_TASK_STACKSIZE ? |
It is working now, had to increase the idle stack size. Did not connect a dac, but logs look ok. @CarlosDerSeher: Might be a good idea to include sdkconfig.default files instead of full sdkconfigs. I created one based on my working esp32 setting with |
@luar123 oh didn't know about this. What exactly does this |
It creates a |
This sounds like something for the future commit list too. Thanks |
Seems we could even split it in multiple files, one for base configs (maybe target dependent) and one for the different audio board settings: https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/build-system.html#custom-sdkconfig-defaults |
This would have been my next question :) as the IDLE task stack size was never a problem on ESP32 |
So a file sdkconfig.defaults.esp32s3 should look like this
|
I have tried only the default size 1536. |
So I decreased this myself at some point while optimizing RAM usage? Totally forgot about this |
Thank you very much CarlosDerSeher and luar123 I have now tried a few things and was able to solve the first problem. After help from anabolyc I was able to get the board to run. The problem here was with the fix_20ms_chunk_size_bug and the CustomBoard TAS5805M. I used the TAS5805M component from features/s3-support. With this it starts and connects to the snapcast server. Now I can get the board to work with WiFi. However, when I start streaming, the following error occurs:
The ESP32S3 has a direct JTAG driver. I have tried to debug from here with VSCode and the ESP-IDF/OpenOCD. Unfortunately I can't get a working debug environment to run. |
Did you enable PSRAM (I think most/all S3 modules have PSRAM)? Otherwise 1000ms buffer length is too much. You would need to reduce it in the snapserver config to ~700ms (see readme). |
You probably have a wrong pin out configured then? I never tried this DAC myself, but others reported it works from customBoard.
What's the code at this line? |
Thanks for the hint, I have changed it. In your example, the PSRAM was not activated. I have activated the PSRAM in my current configuration (8MB - ESP32-S3-WROOM-N16R8).
In the current branch fix_20ms_chunk_size_bug it is line 1351 (old 1371)
I think that |
@Dotsch2005 what's your server config? mainly chunk size. Which codec do you use? PCM I see from your log? You could try enabling this line and maybe add chnk->fragment and fragment->payload pointers to this print just to see if they are NULL |
Yes, the codec is set to PCM in the Snapcast Config. Here is the config:
I have changed the code as follows:
Error on Line player.c:1352 is: Log:
The problem is that the chnk object is not filled. What does this function do after the |
Is it possible to run the snapclient on an ESP32-S3?
I have changed the sdkconfig target with
idf.py set-target esp32s3
and changed the confiuration viaidf.py menuconfig
.I am stuck at
error: ‘I2S_CLK_SRC_APLL’ undeclared
.I have read so that APLL is not available on the ESP32-S3.
Is there a way to get the ESP32-S3 up and running?
The text was updated successfully, but these errors were encountered: