dearsky/pico-fido
1
0
Fork 0
Code Issues 46 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

ESP32-S3 Build Issue: Missing driver/i2s_std.h in zorxx__neopixel #232

New Issue
Open
opened 2025-12-20 01:27:56 +08:00 by fbuirey · 2 comments
fbuirey commented 2025-12-20 01:27:56 +08:00 (Migrated from github.com)
Copy Link

I’m also encountering a compilation issue when building for ESP32-S3 related to the zorxx__neopixel component. The error is as follows:

fatal error: driver/i2s_std.h: No such file or directory
13 | #include "driver/i2s_std.h"

This file seems to be unavailable for ESP32-S3 in the current ESP-IDF version (v6.1)

Context:

ESP-IDF version: v6.1
Target: ESP32-S3
Component: zorxx__neopixel (managed component)
Workaround attempted: Created a dummy i2s_std.h header to bypass the error, but this is not a sustainable solution.

Questions:

  • Is there an official fix or alternative for zorxx__neopixel on ESP32-S3?
  • Should the component use RMT instead of I2S for ESP32-S3 compatibility?
  • Has anyone successfully built this project for ESP32-S3 without modifying the source code?
I’m also encountering a compilation issue when building for ESP32-S3 related to the zorxx__neopixel component. The error is as follows: fatal error: driver/i2s_std.h: No such file or directory 13 | #include "driver/i2s_std.h" This file seems to be unavailable for ESP32-S3 in the current ESP-IDF version (v6.1) **Context**: ESP-IDF version: v6.1 Target: ESP32-S3 Component: zorxx__neopixel (managed component) Workaround attempted: Created a dummy i2s_std.h header to bypass the error, but this is not a sustainable solution. **Questions**: - Is there an official fix or alternative for zorxx__neopixel on ESP32-S3? - Should the component use RMT instead of I2S for ESP32-S3 compatibility? - Has anyone successfully built this project for ESP32-S3 without modifying the source code?
Lab-8916100448256 commented 2025-12-20 22:52:09 +08:00 (Migrated from github.com)
Copy Link

I have successfully built it for ESP32-S3, but with ESP-IDF version 5.5, as it is done in https://github.com/polhenarejos/pico-fido/blob/main/workflows/autobuild.sh

I have successfully built it for ESP32-S3, but with ESP-IDF version 5.5, as it is done in https://github.com/polhenarejos/pico-fido/blob/main/workflows/autobuild.sh
fbuirey commented 2025-12-22 15:58:33 +08:00 (Migrated from github.com)
Copy Link

Thanks, With ESP-IDF version 5.5, I can compile the module. I will now look into adding a 'CUSTOM_BUTTON' to the esp32s3 platform.

Thanks, With ESP-IDF version 5.5, I can compile the module. I will now look into adding a 'CUSTOM_BUTTON' to the esp32s3 platform.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#232
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?