Build err [Resolved] #12

Unclerojelio · 2021-10-04T03:20:37Z

Unclerojelio
Oct 4, 2021

Compiling .pio/build/demo/lib321/IRremoteESP8266/IRtext.cpp.o
src/main.cpp:223:21: error: gRingSizeTable causes a section type conflict with g_SocketServer
 DRAM_ATTR const int gRingSizeTable[MAX_RINGS] = 
                     ^
src/main.cpp:247:28: note: 'g_SocketServer' was declared here
     DRAM_ATTR SocketServer g_SocketServer(49152, STRAND_LEDS);  // $C000 is free RAM on the C64, fwiw!

Can I get a clue?

Answered by BeldrothTheGold

Oct 5, 2021

Maybe try and update your platform IO platforms?

View full answer

rbergen · 2021-10-04T09:08:39Z

rbergen
Oct 4, 2021
Maintainer

What exactly are you trying to build? In other words, what's the build command you're issuing?

3 replies

Unclerojelio Oct 4, 2021
Author

> Executing task: platformio run <

Processing demo (platform: espressif32; board: esp32dev; framework: arduino)

On src/main.cpp

rbergen Oct 4, 2021
Maintainer

I can't reproduce this locally, on the x86_64 system I'm using. It's an error related to the placement of variables in object file sections, which are not manipulated in the relevant source code, as far as I can tell.

What system/architecture and OS/distribution are you building on?

Unclerojelio Oct 4, 2021
Author

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.15.7
BuildVersion:	19H1323

rmd6502 · 2021-10-04T18:40:56Z

rmd6502
Oct 4, 2021

I'm getting the same error on a PopOS (ubuntu) 21.04, VSCode v1.60.2, latest PlatformIO, basically "git clone" and "platformio->build"

PLATFORM: Espressif 32 (1.12.4) > Espressif ESP32 Dev Module
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (esp-prog) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES: 
 - framework-arduinoespressif32 3.10004.200129 (1.0.4) 
 - tool-esptoolpy 1.20600.0 (2.6.0) 
 - toolchain-xtensa32 2.50200.80 (5.2.0)
LDF: Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 37 compatible libraries
Scanning dependencies...
Dependency Graph
|-- <IRremoteESP8266> 2.7.20
|-- <FastLED> 3.4.0
|   |-- <SPI> 1.0
|-- <Adafruit BusIO> 1.9.3
|   |-- <Wire> 1.0.1
|   |-- <SPI> 1.0
|-- <Adafruit GFX Library> 1.10.12
|   |-- <Adafruit BusIO> 1.9.3
|   |   |-- <Wire> 1.0.1
|   |   |-- <SPI> 1.0
|   |-- <Wire> 1.0.1
|   |-- <SPI> 1.0
|-- <ArduinoJson> 6.17.2
|-- <U8g2> 2.28.8
|   |-- <SPI> 1.0
|   |-- <Wire> 1.0.1
|-- <RemoteDebug> 3.0.5
|   |-- <SPI> 1.0
|   |-- <WiFi> 1.0
|   |-- <WiFiClientSecure> 1.0
|   |   |-- <WiFi> 1.0
|-- <arduinoFFT> 1.5.6
|-- <AsyncTCP> 1.1.1
|-- <Bounce2> 2.70.0
|-- <ESP Async WebServer> 1.2.3
|   |-- <AsyncTCP> 1.1.1
|   |-- <ArduinoJson> 6.17.2
|   |-- <FS> 1.0
|   |-- <WiFi> 1.0
|-- <ArduinoOTA> 1.0
|   |-- <Update> 1.0
|   |-- <WiFi> 1.0
|   |-- <ESPmDNS> 1.0
|   |   |-- <WiFi> 1.0
|-- <SD(esp32)> 1.0.5
|   |-- <FS> 1.0
|   |-- <SPI> 1.0
|-- <SPI> 1.0
|-- <WiFi> 1.0
|-- <FS> 1.0
|-- <SPIFFS> 1.0
|   |-- <FS> 1.0
Building in debug mode```
 
```$ uname -a
Linux rmd-linux 5.13.0-7614-generic #14~1631647151~21.04~930e87c-Ubuntu SMP Fri Sep 17 00:24:58 UTC  x86_64 x86_64 x86_64 GNU/Linux```

```src/main.cpp:223:22: error: gRingSizeTable causes a section type conflict with g_SocketServer
 DRAM_ATTR2 const int gRingSizeTable[MAX_RINGS] = 
                      ^
src/main.cpp:247:28: note: 'g_SocketServer' was declared here
     DRAM_ATTR SocketServer g_SocketServer(49152, STRAND_LEDS);  // $C000 is free RAM on the C64, fwiw!```

3 replies

rmd6502 Oct 4, 2021

I was able to get a successful build by going to esp_attr.h and duplicating DRAM_ATTR:
// Forces data into DRAM instead of flash
#define DRAM_ATTR attribute((section(".dram1")))
#define DRAM_ATTR2 attribute((section(".dram2")))

and then setting g_socketserver to have the DRAM_ATTR2, but that's a) modifying a platformio builtin header, and b) throwing a random guess at a wall based on stackoverflow answers that I didn't fully understand.

jmarevans Oct 4, 2021

I tried your solution but it just caused the error to move to a different declaration.

in esp_attr.h:

// Forces data into DRAM instead of flash
#define DRAM_ATTR __attribute__((section(".dram1")))
#define DRAM_ATTR2 __attribute__((section(".dram2")))

in main.cpp:

#if ENABLE_WEBSERVER
    DRAM_ATTR CSPIFFSWebServer g_WebServer;
#endif

#if INCOMING_WIFI_ENABLED
    DRAM_ATTR2 SocketServer g_SocketServer(49152, STRAND_LEDS);  // $C000 is free RAM on the C64, fwiw!
#endif

#if ENABLE_REMOTE
    DRAM_ATTR RemoteControl g_RemoteControl;
#endif

build output:

Compiling .pio\build\demo\lib753\IRremoteESP8266\IRtimer.cpp.o
src\main.cpp:225:21: error: gRingSizeTable causes a section type conflict with g_WebServer
 DRAM_ATTR const int gRingSizeTable[MAX_RINGS] = 
                     ^
src\main.cpp:245:32: note: 'g_WebServer' was declared here
     DRAM_ATTR CSPIFFSWebServer g_WebServer;
                                ^
*** [.pio\build\demo\src\main.cpp.o] Error 1

rmd6502 Oct 5, 2021

Yeah, like I said it was throwing a guess at the wall without much understanding of the underlying issue.

jmarevans · 2021-10-05T00:27:43Z

jmarevans
Oct 5, 2021

Interesting that your guess worked, though.

…

On Mon, Oct 4, 2021 at 5:22 PM Robert Diamond ***@***.***> wrote: Yeah, like I said it was throwing a guess at the wall without much understanding of the underlying issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3VGHESN5UTD75XAQ3IFYTUFJAMZANCNFSM5FILVYCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

1 reply

rmd6502 Oct 5, 2021

Here's the relevant SO link: https://stackoverflow.com/questions/30076949/gcc-error-variable-causes-a-section-type-conflict
and a bonus GCC forum link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091
Something about the compiler inferring different types of section variables in the same section, for (reasons). I think my "solution" sort of worked because the DRAM_ATTR2 didn't have a correspondence in the linker files for Platformio, so it worked out to be a totally different section type. Not sure why it didn't work for you, maybe I had an additional change in there that I forgot to write down? Or different compiler/linker/phase of moon environments?

jmarevans · 2021-10-05T01:56:04Z

jmarevans
Oct 5, 2021

:-)

…

On Mon, Oct 4, 2021 at 5:41 PM Robert Diamond ***@***.***> wrote: Here's the relevant SO link: https://stackoverflow.com/questions/30076949/gcc-error-variable-causes-a-section-type-conflict and a bonus GCC forum link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091 Something about the compiler inferring different types of section variables in the same section, for (reasons). I think my "solution" sort of worked because the DRAM_ATTR2 didn't have a correspondence in the linker files for Platformio, so it worked out to be a totally different section type. Not sure why it didn't work for you, maybe I had an additional change in there that I forgot to write down? Or different compiler/linker/phase of moon environments? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3VGHB4CXUET2BYNAI4VM3UFJCVFANCNFSM5FILVYCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

0 replies

BeldrothTheGold · 2021-10-05T14:38:35Z

BeldrothTheGold
Oct 5, 2021

Maybe try and update your platform IO platforms?

3 replies

jmarevans Oct 5, 2021

Thanks! That seems to have done the trick. There was one module listed as incompatible, but otherwise the update has allowed for a successful build.

Updating platformio/contrib-piohome           3.3.4 @ ~3.3.4                     [Up-to-date]
Updating platformio/contrib-pysite            2.37.191020 @ ~2.37.0              [Incompatible 2.39.201019]
Updating platformio/tool-unity                1.20500.200612 @ ~1.20500.0        [Up-to-date]
Updating platformio/tool-scons                4.40200.0 @ ~4.40200.0             [Up-to-date]

Platform Manager
================
Platform espressif32
--------
Updating platformio/espressif32               3.0.0                              [Updating to 3.3.2]
Platform Manager: Installing platformio/espressif32 @ 3.3.2
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Platform Manager: espressif32 @ 3.3.2 has been installed!
Tool Manager: toolchain-xtensa32 @ 2.50200.80 is already installed
Tool Manager: Installing platformio/tool-esptoolpy @ ~1.30100.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Tool Manager: tool-esptoolpy @ 1.30100.210531 has been installed!
Platform Manager: Removing espressif32 @ 3.0.0
Platform Manager: espressif32 @ 3.0.0 has been removed!
Updating platformio/toolchain-xtensa32        2.50200.80 @ ~2.50200.0            [Updating to 2.50200.97]
Tool Manager: Installing platformio/toolchain-xtensa32 @ 2.50200.97
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Tool Manager: toolchain-xtensa32 @ 2.50200.97 has been installed!
Tool Manager: Removing toolchain-xtensa32 @ 2.50200.80
Tool Manager: toolchain-xtensa32 @ 2.50200.80 has been removed!
Updating platformio/tool-esptoolpy            1.30100.210531 @ ~1.30100.0        [Up-to-date]
Updating platformio/tool-openocd-esp32        2.1000.20201202 @ ~2.1000.0        [Updating to 2.1000.20210721]
Tool Manager: Installing platformio/tool-openocd-esp32 @ 2.1000.20210721
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Tool Manager: tool-openocd-esp32 @ 2.1000.20210721 has been installed!
Tool Manager: Removing tool-openocd-esp32 @ 2.1000.20201202
Tool Manager: tool-openocd-esp32 @ 2.1000.20201202 has been removed!
Updating platformio/tool-mkspiffs             2.230.0 @ ~2.230.0                 [Up-to-date]
Tool Manager: Installing platformio/framework-arduinoespressif32 @ ~3.10006.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Tool Manager: framework-arduinoespressif32 @ 3.10006.210326 has been installed!

Platform espressif8266
--------
Updating platformio/espressif8266             2.6.3                              [Updating to 3.2.0]
Platform Manager: Installing platformio/espressif8266 @ 3.2.0
Platform Manager: espressif8266 @ 3.2.0 has been installed!
Tool Manager: Installing platformio/toolchain-xtensa @ ~2.100300.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Tool Manager: toolchain-xtensa @ 2.100300.210717 has been installed!
Tool Manager: tool-esptool @ 1.413.0 is already installed
Tool Manager: tool-esptoolpy @ 1.30000.201119 is already installed
Platform Manager: espressif8266 @ 2.6.3 has been removed!
Updating platformio/toolchain-xtensa          2.100300.210717 @ ~2.100300.0      [Up-to-date]
Updating platformio/tool-esptool              1.413.0 @ <2                       [Up-to-date]
Updating platformio/tool-esptoolpy            1.30000.201119 @ ~1.30000.0        [Up-to-date]
Updating platformio/tool-mkspiffs             1.200.0 @ ~1.200.0                 [Up-to-date]
Updating platformio/tool-mklittlefs           1.203.210203 @ ~1.203.0            [Updating to 1.203.210628]
Tool Manager: Installing platformio/tool-mklittlefs @ 1.203.210628
Downloading  [####################################]  100%
Tool Manager: tool-mklittlefs @ 1.203.210628 has been installed!
Tool Manager: Removing tool-mklittlefs @ 1.203.210203
Tool Manager: tool-mklittlefs @ 1.203.210203 has been removed!
Tool Manager: Installing platformio/framework-arduinoespressif8266 @ ~3.30002.0
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
Tool Manager: framework-arduinoespressif8266 @ 3.30002.0 has been installed!


Library Manager
===============
Library Storage: C:\Users\Jesse\.platformio\lib
PS C:\Users\Jesse\Documents\PlatformIO\Projects\nightdriver>

BeldrothTheGold Oct 5, 2021

nice

Unclerojelio Oct 6, 2021
Author

Worked for me too. Thanks!

davepl · 2021-10-06T00:57:57Z

davepl
Oct 6, 2021
Maintainer

Looks like it builds now!

0 replies

jmarevans · 2021-10-06T01:17:44Z

jmarevans
Oct 6, 2021

Yup! Played around with it a bit today; looking forward to more videos in this series. I watched your first LED strip series and really learned a lot. Actually, I’ve been enjoying all your videos. They’re very entertaining and informative. Thanks for doing what you do!

…

On Tue, Oct 5, 2021 at 5:58 PM David W Plummer ***@***.***> wrote: Looks like it builds now! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3VGHGEK3ZLT72GLIKQBRDUFONJ7ANCNFSM5FILVYCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

0 replies

Build err [Resolved] #12

Uh oh!

Uh oh!

Replies: 7 comments · 10 replies

Uh oh!

rbergen Oct 4, 2021 Maintainer

Uh oh!

Unclerojelio Oct 4, 2021 Author

Uh oh!

rbergen Oct 4, 2021 Maintainer

Uh oh!

Unclerojelio Oct 4, 2021 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Unclerojelio Oct 6, 2021 Author

Uh oh!

davepl Oct 6, 2021 Maintainer

Uh oh!

Replies: 7 comments 10 replies

rbergen
Oct 4, 2021
Maintainer

Unclerojelio Oct 4, 2021
Author

rbergen Oct 4, 2021
Maintainer

Unclerojelio Oct 4, 2021
Author

Unclerojelio Oct 6, 2021
Author

davepl
Oct 6, 2021
Maintainer