ESP8266 iram1_0_seg too Large

Sysprogs forums Forums VisualGDB ESP8266 iram1_0_seg too Large

Viewing 2 posts - 16 through 17 (of 17 total)
  • Author
    Posts
  • #9223
    freeck
    Participant

    This is part of the error log:
    C:\SysGCC\esp8266/bin/xtensa-lx106-elf-gcc.exe -ggdb -ffunction-sections -O0 -nostdlib -mlongcalls -mtext-section-literals -nostdlib -mlongcalls -mtext-section-literals -I. -IC:\SysGCC\esp8266\esp8266-bsp/sysprogs/include -IC:\SysGCC\esp8266\esp8266-bsp/IoT-SDK/include -IC:\SysGCC\esp8266\esp8266-bsp/RTOS-SDK/extra_include -IC:\SysGCC\esp8266\esp8266-bsp/GDBStub -DDEBUG=1 -DICACHE_FLASH -DESP8266_GDBSTUB -DGDBSTUB_BREAK_ON_INIT=1 -DGDBSTUB_FREERTOS=0 -c C:\SysGCC\esp8266\esp8266-bsp/sysprogs/stubs.c -o Debug/stubs.o -MD -MF Debug/stubs.dep
    1> C:\SysGCC\esp8266/bin/xtensa-lx106-elf-g++.exe -ggdb -ffunction-sections -fno-exceptions -fno-rtti -O0 -nostdlib -mlongcalls -mtext-section-literals -nostdlib -mlongcalls -mtext-section-literals -I. -IC:\SysGCC\esp8266\esp8266-bsp/sysprogs/include -IC:\SysGCC\esp8266\esp8266-bsp/IoT-SDK/include -IC:\SysGCC\esp8266\esp8266-bsp/RTOS-SDK/extra_include -IC:\SysGCC\esp8266\esp8266-bsp/GDBStub -DDEBUG=1 -DICACHE_FLASH -DESP8266_GDBSTUB -DGDBSTUB_BREAK_ON_INIT=1 -DGDBSTUB_FREERTOS=0 -c LEDBlink.cpp -o Debug/LEDBlink.o -MD -MF Debug/LEDBlink.dep
    1> C:\SysGCC\esp8266/bin/xtensa-lx106-elf-gcc.exe -ggdb -ffunction-sections -O0 -nostdlib -mlongcalls -mtext-section-literals -nostdlib -mlongcalls -mtext-section-literals -I. -IC:\SysGCC\esp8266\esp8266-bsp/sysprogs/include -IC:\SysGCC\esp8266\esp8266-bsp/IoT-SDK/include -IC:\SysGCC\esp8266\esp8266-bsp/RTOS-SDK/extra_include -IC:\SysGCC\esp8266\esp8266-bsp/GDBStub -DDEBUG=1 -DICACHE_FLASH -DESP8266_GDBSTUB -DGDBSTUB_BREAK_ON_INIT=1 -DGDBSTUB_FREERTOS=0 -nostdlib -mlongcalls -mtext-section-literals -nostdlib -mlongcalls -mtext-section-literals -DDEBUG=1 -DICACHE_FLASH -DESP8266_GDBSTUB -DGDBSTUB_BREAK_ON_INIT=1 -DGDBSTUB_FREERTOS=0 -c C:\SysGCC\esp8266\esp8266-bsp/GDBStub/gdbstub-entry.S -o Debug/gdbstub-entry.o -MD -MF Debug/gdbstub-entry.dep
    1> C:\SysGCC\esp8266/bin/xtensa-lx106-elf-g++.exe -o Debug/GpioTesten.elf -Wl,-gc-sections -Wl,-Map=fred.map -TC:\SysGCC\esp8266\esp8266-bsp/IoT-SDK/ld/eagle.app.v6.ld -nostdlib -mlongcalls -mtext-section-literals -nostdlib -mlongcalls -mtext-section-literals -LC:\SysGCC\esp8266/hal -LC:\SysGCC\esp8266\esp8266-bsp/IoT-SDK/lib -LC:\SysGCC\esp8266\esp8266-bsp/IoT-SDK/ld -Wl,–start-group Debug/gdbstub.o Debug/stubs.o Debug/LEDBlink.o Debug/gdbstub-entry.o -lc -lgcc -lphy -lpp -lnet80211 -llwip -lwpa -lmain -ljson -lupgrade -lssl -lpwm -lsmartconfig -lcrypto -Wl,–end-group
    1> c:/sysgcc/esp8266/bin/../lib/gcc/xtensa-lx106-elf/5.2.0\libgcc.a(_divdi3.o): In function `__udivmoddi4′:
    1> /q/gnu/auto/gcc-bu-2.24+gcc-5.2.0+gmp-5.1.3+mpfr-3.1.2+mpc-1.0.2+newlib-2.0.0-xtensa-lx106-elf/xtensa-lx106-elf/libgcc/../../../gcc-5.2.0/libgcc/libgcc2.c:1078:(.irom0.text+0x8a): dangerous relocation: l32r: literal target out of range (try using text-section-literals): .literal
    1> /q/gnu/auto/gcc-bu-2.24+gcc-5.2.0+gmp-5.1.3+mpfr-3.1.2+mpc-1.0.2+newlib-2.0.0-xtensa-lx106-elf/xtensa-lx106-elf/libgcc/../../../gcc-5.2.0/libgcc/libgcc2.c:1078:(.irom0.text+0x9a): dangerous relocation: l32r: literal target out of range (try using text-section-literals): (.literal+0x4)
    1> /q/gnu/auto/gcc-bu-2.24+gcc-5.2.0+gmp-5.1.3+mpfr-3.1.2+mpc-1.0.2+newlib-2.0.0-xtensa-lx106-elf/xtensa-lx106-elf/libgcc/../../../gcc-5.2.0/libgcc/libgcc2.c:1078:(.irom0.text+0xd4): dangerous relocation: l32r: literal target out of range (try using text-section-literals): (.literal+0x8)
    1> /

    But strangely enough, when I deleted all 4 functions from libgcc.a the linker did no protest for these missing functions, so why were these functions included in the first place? After deleting all functions of libgcc2.c as displayed in the memory explorer I save ca 2K of IRAM, and the application is running OK…
    I dont get this….

    • This reply was modified 7 years, 5 months ago by freeck.
    #9233
    support
    Keymaster

    Hi,

    Perhaps the linker just reports the wrong function? Please try relocating ALL the functions from _divdi3.o in libgcc.a

Viewing 2 posts - 16 through 17 (of 17 total)
  • You must be logged in to reply to this topic.