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

[esp32 S2] Allow .bss segment placed in external memory (IDFGH-4320) #6162

Closed
chegewara opened this issue Nov 25, 2020 · 5 comments
Closed
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally

Comments

@chegewara
Copy link
Contributor

When i am trying to enable Allow .bss segment placed in external memory in menuconfig then code does not build with error:

/home/chegewara/esp/esp-idf/components/esp_system/port/cpu_start.c:395:13: error: '_ext_ram_bss_start' undeclared (first use in this function); did you mean '_rtc_bss_start'?
     memset(&_ext_ram_bss_start, 0, (&_ext_ram_bss_end - &_ext_ram_bss_start) * sizeof(_ext_ram_bss_start));
             ^~~~~~~~~~~~~~~~~~
             _rtc_bss_start
/home/chegewara/esp/esp-idf/components/esp_system/port/cpu_start.c:395:13: note: each undeclared identifier is reported only once for each function it appears in
/home/chegewara/esp/esp-idf/components/esp_system/port/cpu_start.c:395:38: error: '_ext_ram_bss_end' undeclared (first use in this function); did you mean '_rtc_bss_end'?
     memset(&_ext_ram_bss_start, 0, (&_ext_ram_bss_end - &_ext_ram_bss_start) * sizeof(_ext_ram_bss_start));
                                      ^~~~~~~~~~~~~~~~
                                      _rtc_bss_end

IDF: master commit 357a277
board: S2 wrover module
SPI RAM access method - all 3 options

@github-actions github-actions bot changed the title [esp32 S2] Allow .bss segment placed in external memory [esp32 S2] Allow .bss segment placed in external memory (IDFGH-4320) Nov 25, 2020
@projectgus
Copy link
Contributor

Hi @chegewara,

Sorry no one got back to you about this earlier. This config option shouldn't actually be visible for ESP32-S2 as this feature has only been implemented for ESP32. Because ESP32-S2 can map PSRAM in different ways, it's not straightforward to map the variable addresses at build time.

Will update this ticket again once we have an ETA for supporting this feature on ESP32-S2.

espressif-bot pushed a commit that referenced this issue Mar 12, 2021
…" for ESP32-S2 & ESP32-S3

Support for this feature is still pending.

As reported by #6162
@sgnes
Copy link

sgnes commented Jul 21, 2021

@projectgus Any update for this issue, do you have any plan to support esp32-s2?

@espressif-bot espressif-bot added the Status: In Progress Work is in progress label Jul 21, 2021
@igrr
Copy link
Member

igrr commented Jul 21, 2021

@sgnes this feature will be supported on S2, the code is in review now. Should be available in the next couple weeks. This issue will be updated when the feature is merged.

espressif-bot pushed a commit that referenced this issue Jul 28, 2021
…" for ESP32-S2 & ESP32-S3

Support for this feature is still pending.

As reported by #6162
@pratikpanchal4
Copy link

Any update on timeline for this feature support on esp32-s2. As timeline was mentioned around couple of weeks, Is it still the same?

espressif-bot pushed a commit that referenced this issue Aug 15, 2021
…" for ESP32-S2 & ESP32-S3

Support for this feature is still pending.

As reported by #6162
@espressif-bot espressif-bot added Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Resolution: Done Issue is done internally and removed Status: In Progress Work is in progress Resolution: NA Issue resolution is unavailable labels Aug 25, 2021
@Alvin1Zhang
Copy link
Collaborator

Thanks for reporting and sorry for slow turnaround, the fix is available b287e01, feel free to reopen.

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

No branches or pull requests

7 participants