Skip to content
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

CONFIG_SPIRAM_IGNORE_NOTFOUND does not work on ESP32-PICO-V3 (but works on ESP32-PICO-D4) (IDFGH-14168) #14970

Closed
3 tasks done
mmrein opened this issue Dec 2, 2024 · 2 comments
Assignees
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Type: Bug bugs in IDF

Comments

@mmrein
Copy link

mmrein commented Dec 2, 2024

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

v4.4.6, v5.4.0-beta1

Espressif SoC revision.

ESP32-PICO-V3

Operating System used.

Linux

How did you build your project?

Command line with idf.py

If you are using Windows, please specify command line type.

None

Development Kit.

ESP-PICO-KIT-1

Power Supply used.

USB

What is the expected behavior?

When using CONFIG_SPIRAM_IGNORE_NOTFOUND=y the app should be able to boot without PSRAM. This works correctly on ESP32-PICO-D4 (no PSRAM) for example:

I (5643) boot: Loaded app from partition at offset 0x20000 
I (5643) boot: Disabling RNG early entropy source... 
I (5653) quad_psram: This chip is ESP32-PICO 
E (5654) quad_psram: PSRAM ID read error: 0xffffffff, PSRAM chip not found or not supported 
E (5658) esp_psram: PSRAM enabled but initialization failed. Bailing out. 
I (5665) cpu_start: Failed to init external RAM; continuing without it. 
... app boot continues normally

What is the actual behavior?

When this option is enabled on ESP32-PICO-V3 (no PSRAM) the app boot fails and ESP reboots:

I (607) boot: Loaded app from partition at offset 0x20000 
I (623) boot: Set actual ota_seq=1 in otadata[0] 
I (623) boot: Disabling RNG early entropy source... 
E (632) quad_psram: This chip is ESP32-PICO-V3. It does not support PSRAM (disable it in Kconfig) 
abort() was called at PC 0x40086a9c on core 0 
Backtrace: ....
...
Rebooting... 

Steps to reproduce.

Using following options in sdkconfig file:

CONFIG_SPIRAM=y
CONFIG_SPIRAM_BOOT_INIT=y
CONFIG_SPIRAM_IGNORE_NOTFOUND=y

Debug Logs.

No response

More Information.

ESP32-PICO-V3-02 works correctly as it does have PSRAM.

@mmrein mmrein added the Type: Bug bugs in IDF label Dec 2, 2024
@github-actions github-actions bot changed the title CONFIG_SPIRAM_IGNORE_NOTFOUND does not work on ESP32-PICO-V3 (but works on ESP32-PICO-D4) CONFIG_SPIRAM_IGNORE_NOTFOUND does not work on ESP32-PICO-V3 (but works on ESP32-PICO-D4) (IDFGH-14168) Dec 2, 2024
@espressif-bot espressif-bot added the Status: Opened Issue is new label Dec 2, 2024
@espressif-bot espressif-bot added Status: Selected for Development Issue is selected for development Status: Reviewing Issue is being reviewed and removed Status: Opened Issue is new Status: Selected for Development Issue is selected for development labels Dec 3, 2024
@Icarus113
Copy link
Collaborator

@mmrein have reproduced your issue, the fix will be updated here soon~

@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: NA Issue resolution is unavailable and removed Status: Reviewing Issue is being reviewed labels Dec 4, 2024
@mmrein
Copy link
Author

mmrein commented Dec 6, 2024

Thank you for quick solve!

I've successfully tested the fix on v4.4.6 too, just the line and file in question is this one, in case someone else needs it:

Change to return ESP_FAIL;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Type: Bug bugs in IDF
Projects
None yet
Development

No branches or pull requests

3 participants