topic Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects in LPCXpresso IDE

New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:09 GMT

Content originally posted in LPCWare by briching on Wed Oct 28 11:02:43 MST 2015
We have noticed this linker warning (in only the M0 build) after switching over to the 7.9.XX versions of the tool. Does anyone know how to troubleshoot it? There is very limited information through a google search on this warning, and it seems like no one else has documented it in the LPCXpresso toolchain. I've replaced the project file names with XXXX_m0.

Building target: XXXX_m0.axf
Invoking: MCU C++ Linker
arm-none-eabi-c++ -nostdlib -L<proprietary files here>
copy from `XXXX_m0.axf' [elf32-littlearm] to `XXXX_m0.axf.o' [elf32-littlearm]
BFD: XXXX_m0.axf: warning: Empty loadable segment detected, is this intentional ?

BFD: XXXX_m0.axf: warning: Empty loadable segment detected, is this intentional ?

Finished building target: XXXX_m0.axf

make --no-print-directory post-build
Performing post-build steps
arm-none-eabi-size "XXXX_m0.axf"; # arm-none-eabi-objcopy -v -O binary "XXXX_m0.axf" "XXXX_m0.bin" ; # checksum -p LPC4357_M0 -d "XXXX_m0.bin";
text data bss dec hexfilename
335928 4472 18208 358608 578d0XXXX_m0.axf

Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:10 GMT

Content originally posted in LPCWare by lpcxpresso-support on Fri Oct 30 03:38:30 MST 2015
I can't replicate your problem using a newly created C++ set of multicore projects.

Please can you post the whole of your link line. This will include the command that is being used to convert the M0 AXF file into an object file that can be linked into the main M4 image. It is this "arm-none-eabi-objcopy" conversion command carried out as part of the link step that is triggering the warning.

I suspect that we will also need to see your M0 axf file too. Can you ZIP and attach this?

If not, then please can you at least disassemble it, and post the first part of it (up to the "SYMBOL TABLE:" marker).

https://www.lpcware.com/content/faq/lpcxpresso/disassembling-objects-and-executables

Regards,
LPCXpresso Support

Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:11 GMT

Content originally posted in LPCWare by briching on Mon Nov 02 10:26:11 MST 2015
Here is the whole of our linker line as well as the section of our axf file, with proprietary names overwritten with XXXX. If you need to see them unmodified, I will need to work with you directly over email.

Link line:

Building target: XXXX_m0.axf
Invoking: MCU C++ Linker
arm-none-eabi-c++ -nostdlib -L"C:\git\Embedded\xLib\xThirdParty\xGraphics\emWin\emWin_library\LPCXpresso" -Xlinker -Map="XXXX_m0.map" -Xlinker --defsym=__user_stack_top=__top_RamLoc32 -Xlinker --gc-sections -mcpu=cortex-m0 -mthumb -T XXXX_m0_Debug.ld -o "XXXX_m0.axf"  ./XXXX/src/UiResources/Base64.o ./XXXX/src/UiResources/TBufferStream.o ./XXXX/src/UiResources/TEmWinFont.o ./XXXX/src/UiResources/TFileParser.o ./XXXX/src/UiResources/TLabelPreparer.o ./XXXX/src/UiResources/TUIResources.o ./XXXX/src/UiResources/cl_xUIStringFormatter.o ./XXXX/src/UiResources/yxml.o  ./XXXX/src/Timers/cl_tmrEvents.o ./XXXX/src/Timers/cl_tmrRIT.o ./XXXX/src/Timers/cl_tmrRequired.o ./XXXX/src/Timers/cl_tmrStandard.o ./XXXX/src/Timers/clbc_tmrTimer.o  ./XXXX/src/TenKhz/cl_tenKhzSctClock.o  ./XXXX/src/Screens/cl_scrnEventMgr.o ./XXXX/src/Screens/cl_scrnForm.o ./XXXX/src/Screens/cl_scrnScreen.o ./XXXX/src/Screens/cl_scrnScreenStack.o ./XXXX/src/Screens/cl_scrnWidgetsClient.o ./XXXX/src/Screens/cl_scrnWidgetsEmWin.o  ./XXXX/src/Parameters/cl_parBoolParam.o ./XXXX/src/Parameters/cl_parEnumParam.o ./XXXX/src/Parameters/cl_parFloatParam.o ./XXXX/src/Parameters/cl_parStrParam.o ./XXXX/src/Parameters/cl_parUintParam.o ./XXXX/src/Parameters/clbc_parParamGroup.o ./XXXX/src/Parameters/clbc_parParamTemplate.o  ./XXXX/src/Memory/cl_memIpcSharedMemory.o ./XXXX/src/Memory/cl_memMemoryTest.o  ./XXXX/src/Libs/cl_libFileSystem.o ./XXXX/src/Libs/cl_libRealTimeClock.o ./XXXX/src/Libs/cl_libScreen.o ./XXXX/src/Libs/cl_libSysConfig.o ./XXXX/src/Libs/cl_libUiResources.o ./XXXX/src/Libs/cl_libUiResourcesClient.o ./XXXX/src/Libs/clbc_libUiResources.o  ./XXXX/src/GPIO/cl_gpioPin.o ./XXXX/src/GPIO/cl_gpioPort.o  ./XXXX/src/FileSys/cl_fsIniFile.o ./XXXX/src/FileSys/cl_fsStdio.o  ./XXXX/src/DataStreams/cl_dsIPCStream.o ./XXXX/src/DataStreams/cl_dsUartIRQStream.o ./XXXX/src/DataStreams/cl_dsUartStream.o ./XXXX/src/DataStreams/clbc_dsHandShakeMgr.o ./XXXX/src/DataStreams/clbc_dsStream.o  ./XXXX/src/Configuration/cl_cfgApi.o ./XXXX/src/Configuration/cl_cfgGlobals.o ./XXXX/src/Configuration/cl_cfgScanner.o ./XXXX/src/Configuration/cl_cfgStream.o ./XXXX/src/Configuration/cl_cfgSystem.o  ./XXXX/src/Common/buffer.o ./XXXX/src/Common/cl_xAssert.o ./XXXX/src/Common/cl_XXXXBaseObj.o ./XXXX/src/Common/cl_xCrcCalc.o ./XXXX/src/Common/cl_xDebug.o ./XXXX/src/Common/cl_xExponentsAndUnits.o ./XXXX/src/Common/cl_xFatalErrorMgr.o ./XXXX/src/Common/cl_xNumUtils.o ./XXXX/src/Common/cl_xStringUtils.o ./XXXX/src/Common/cl_xValue.o ./XXXX/src/Common/cl_xValueToText.o ./XXXX/src/Common/cl_xZDotTextLog.o ./XXXX/src/Common/formatbuffer.o ./XXXX/src/Common/val2text.o  ./XXXX/src/Application/clbc_appApplication.o ./XXXX/src/Application/clbc_appSelfTest.o  ./XXXX/src/Api/XXXXApi/cl_capiFileSystem.o ./XXXX/src/Api/XXXXApi/cl_capiRequired.o ./XXXX/src/Api/XXXXApi/cl_capiScanner.o ./XXXX/src/Api/XXXXApi/cl_capiScreen.o ./XXXX/src/Api/XXXXApi/cl_capiUiResources.o  ./XXXX/src/Api/cl_apiClient.o ./XXXX/src/Api/cl_apiFramework.o ./XXXX/src/Api/cl_apiPacketBuffer.o ./XXXX/src/Api/cl_apiServer.o ./XXXX/src/Api/cl_apiStreamBuffer.o ./XXXX/src/Api/clbc_apiDataBuffer.o  ./xChip/src/adc_18xx_43xx.o ./xChip/src/aes_18xx_43xx.o ./xChip/src/atimer_18xx_43xx.o ./xChip/src/ccan_18xx_43xx.o ./xChip/src/chip_18xx_43xx.o ./xChip/src/clock_18xx_43xx.o ./xChip/src/dac_18xx_43xx.o ./xChip/src/eeprom_18xx_43xx.o ./xChip/src/emc_18xx_43xx.o ./xChip/src/enet_18xx_43xx.o ./xChip/src/evrt_18xx_43xx.o ./xChip/src/gpdma_18xx_43xx.o ./xChip/src/gpio_18xx_43xx.o ./xChip/src/gpiogroup_18xx_43xx.o ./xChip/src/hsadc_18xx_43xx.o ./xChip/src/i2c_18xx_43xx.o ./xChip/src/i2cm_18xx_43xx.o ./xChip/src/i2s_18xx_43xx.o ./xChip/src/iap_18xx_43xx.o ./xChip/src/lcd_18xx_43xx.o ./xChip/src/otp_18xx_43xx.o ./xChip/src/pinint_18xx_43xx.o ./xChip/src/pmc_18xx_43xx.o ./xChip/src/rgu_18xx_43xx.o ./xChip/src/ring_buffer.o ./xChip/src/ritimer_18xx_43xx.o ./xChip/src/rtc_18xx_43xx.o ./xChip/src/sct_18xx_43xx.o ./xChip/src/sct_pwm_18xx_43xx.o ./xChip/src/scu_18xx_43xx.o ./xChip/src/sdif_18xx_43xx.o ./xChip/src/sdmmc_18xx_43xx.o ./xChip/src/spi_18xx_43xx.o ./xChip/src/ssp_18xx_43xx.o ./xChip/src/stopwatch_18xx_43xx.o ./xChip/src/sysinit_18xx_43xx.o ./xChip/src/timer_18xx_43xx.o ./xChip/src/uart_18xx_43xx.o ./xChip/src/wwdt_18xx_43xx.o  ./xBoard/src/Timers/bd_tmrRIT.o ./xBoard/src/Timers/bd_tmrStandard.o ./xBoard/src/Timers/bd_tmrSysTickEvents.o  ./xBoard/src/TenKhz/SCT_LPC4357/bd_10khzSctDriver.o ./xBoard/src/TenKhz/SCT_LPC4357/sct_10khz_state_machine.o  ./xBoard/src/TenKhz/SCT_LPC1519/bd_pclkSctDriver.o ./xBoard/src/TenKhz/SCT_LPC1519/sct_pclk_state_machine.o  ./xBoard/src/Software/bd_swEmWin.o  ./xBoard/src/SelfTest/bd_selfMemTestDriver.o ./xBoard/src/SelfTest/bd_selfMemTests.o  ./xBoard/src/RTC/bd_rtcDriver.o  ./xBoard/src/IPC/bd_ipcCommDriver.o ./xBoard/src/IPC/bd_ipcSharedMemoryDriver.o  ./xBoard/src/Hardware/bd_hwADC.o ./xBoard/src/Hardware/bd_hwBoardCfg.o ./xBoard/src/Hardware/bd_hwComparator.o ./xBoard/src/Hardware/bd_hwDAC.o ./xBoard/src/Hardware/bd_hwLcd.o ./xBoard/src/Hardware/bd_hwSdmmc.o ./xBoard/src/Hardware/bd_hwSdram.o ./xBoard/src/Hardware/bd_hwSineGen.o ./xBoard/src/Hardware/bd_hwSpeakerLM48100Q.o ./xBoard/src/Hardware/bd_hwSpifi.o ./xBoard/src/Hardware/bd_hwTouchFT5x06.o ./xBoard/src/Hardware/bd_hwUsbDevice.o ./xBoard/src/Hardware/bd_hwUsbHostEvent.o ./xBoard/src/Hardware/bd_hwUsbHostMassStorage.o  ./xBoard/src/GPIO/bd_gpioPinDriver.o ./xBoard/src/GPIO/bd_gpioPortDriver.o  ./xBoard/src/FileSys/Drives/bd_fsRamDisk.o ./xBoard/src/FileSys/Drives/bd_fsSdmmcDisk.o ./xBoard/src/FileSys/Drives/bd_fsSpifiDisk.o ./xBoard/src/FileSys/Drives/bd_fsUsbDisk.o  ./xBoard/src/FileSys/bd_fsDiskIO.o ./xBoard/src/FileSys/bd_fsFileSys.o ./xBoard/src/FileSys/bd_fsTest.o  ./xBoard/src/Debug/bd_dbgRedirect.o  ./xBoard/src/DataStreams/bd_dsSpiDriver.o ./xBoard/src/DataStreams/bd_dsUartDriver.o  ./xBoard/src/Common/bd_xAssert.o ./xBoard/src/Common/bd_xInterrupts.o ./xBoard/src/Common/bd_xMcuPin.o ./xBoard/src/Common/bd_xRingBuffer.o  ./xApp/33xxUI_ui_screens.o ./xApp/33xxUI_ui_strings.o  ./src/main/cr_cpp_config.o ./src/main/cr_startup_lpc43xx-m0app.o ./src/main/main.o ./src/main/sysinit.o  ./src/emWin/GUIConf.o ./src/emWin/GUI_X.o ./src/emWin/LCDConf.o  ./Board/src/bd_17_39700_01A.o ./Board/src/bd_17_48100_01B.o ./Board/src/board_driver_init.o ./Board/src/board_system_init.o   -lemWin_M0 && arm-none-eabi-objcopy --target elf32-littlearm --verbose --strip-all --remove-section=.ARM.attributes --redefine-sym __vectors_start__=__vectors_start___core_m0app --keep-symbol __vectors_start___core_m0app --redefine-sym _data=__start_data_core_m0app --keep-symbol __start_data_core_m0app --redefine-sym _edata=__end_data_core_m0app --keep-symbol __end_data_core_m0app --remove-section=".bss*" --remove-section=".noinit*" --rename-section .ARM.exidx=".core_m0app.ARM.exidx" --rename-section .ARM.extab=".core_m0app.ARM.extab" --rename-section .text=".core_m0app" --rename-section .data=".core_m0app.data" --rename-section .data_RAM2=".core_m0app.data_RAM2" --rename-section .data_RAM3=".core_m0app.data_RAM3" --rename-section .data_RAM4=".core_m0app.data_RAM4" --rename-section .data_RAM5=".core_m0app.data_RAM5" --rename-section .data_RAM6=".core_m0app.data_RAM6" --rename-section .data_RAM7=".core_m0app.data_RAM7" "XXXX_m0.axf" "XXXX_m0.axf.o"
copy from `XXXX_m0.axf' [elf32-littlearm] to `XXXX_m0.axf.o' [elf32-littlearm]
BFD: XXXX_m0.axf: warning: Empty loadable segment detected, is this intentional ?

Finished building target: XXXX_m0.axf
 
make --no-print-directory post-build
Performing post-build steps
arm-none-eabi-size "XXXX_m0.axf"; # arm-none-eabi-objcopy -v -O binary "XXXX_m0.axf" "XXXX_m0.bin" ; # checksum -p LPC4357_M0 -d "XXXX_m0.bin";
   text   data    bss    dec    hexfilename
 329624   4472   5492 339588  52e84XXXX_m0.axf

AXF file up to SYMBOL TABLE:

C:\git\Embedded\XXXX_m0\Debug\XXXX_m0.axf:     file format elf32-littlearm
C:\git\Embedded\XXXX_m0\Debug\XXXX_m0.axf
architecture: arm, flags 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x1b012319

Program Header:
0x70000001 off    0x00058480 vaddr 0x1b050480 paddr 0x1b050480 align 2**2
         filesz 0x00000318 memsz 0x00000318 flags r--
    LOAD off    0x00008000 vaddr 0x1b000000 paddr 0x1b000000 align 2**15
         filesz 0x00050798 memsz 0x00050798 flags r-x
    LOAD off    0x00060000 vaddr 0x28000000 paddr 0x1b050798 align 2**15
         filesz 0x00001178 memsz 0x00001178 flags rw-
    LOAD off    0x00061178 vaddr 0x28001178 paddr 0x28001178 align 2**15
         filesz 0x00000000 memsz 0x00001574 flags rw-
private flags = 5000202: [Version5 EABI] [soft-float ABI] [has entry point]

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         00050228  1b000000  1b000000  00008000  2**3
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .data         00001178  28000000  1b050798  00060000  2**3
                  CONTENTS, ALLOC, LOAD, DATA
  2 .data_RAM2    00000000  28800000  28800000  00061178  2**2
                  CONTENTS
  3 .data_RAM3    00000000  10000000  10000000  00061178  2**2
                  CONTENTS
  4 .data_RAM4    00000000  10080000  10080000  00061178  2**2
                  CONTENTS
  5 .data_RAM5    00000000  20000000  20000000  00061178  2**2
                  CONTENTS
  6 .data_RAM6    00000000  20008000  20008000  00061178  2**2
                  CONTENTS
  7 .data_RAM7    00000000  2000c000  2000c000  00061178  2**2
                  CONTENTS
  8 .bss          00001574  28001178  28001178  00061178  2**3
                  ALLOC
  9 .ARM.extab    00000258  1b050228  1b050228  00058228  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
 10 .ARM.exidx    00000318  1b050480  1b050480  00058480  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
 11 .uninit_RESERVED 00000000  28000000  28000000  00061178  2**2
                  CONTENTS
 12 .noinit_RAM2  00000000  28800000  28800000  00061178  2**2
                  CONTENTS
 13 .noinit_RAM3  00000000  10000000  10000000  00061178  2**2
                  CONTENTS
 14 .noinit_RAM4  00000000  10080000  10080000  00061178  2**2
                  CONTENTS
 15 .noinit_RAM5  00000000  20000000  20000000  00061178  2**2
                  CONTENTS
 16 .noinit_RAM6  00000000  20008000  20008000  00061178  2**2
                  CONTENTS
 17 .noinit_RAM7  00000000  2000c000  2000c000  00061178  2**2
                  CONTENTS
 18 .noinit       00000000  280026ec  280026ec  00061178  2**2
                  CONTENTS
 19 .debug_info   000d1aa8  00000000  00000000  00061178  2**0
                  CONTENTS, READONLY, DEBUGGING
 20 .debug_abbrev 0001289a  00000000  00000000  00132c20  2**0
                  CONTENTS, READONLY, DEBUGGING
 21 .debug_aranges 00005890  00000000  00000000  001454ba  2**0
                  CONTENTS, READONLY, DEBUGGING
 22 .debug_ranges 000053c8  00000000  00000000  0014ad4a  2**0
                  CONTENTS, READONLY, DEBUGGING
 23 .debug_macro  000212ed  00000000  00000000  00150112  2**0
                  CONTENTS, READONLY, DEBUGGING
 24 .debug_line   0004190c  00000000  00000000  001713ff  2**0
                  CONTENTS, READONLY, DEBUGGING
 25 .debug_str    00068f9e  00000000  00000000  001b2d0b  2**0
                  CONTENTS, READONLY, DEBUGGING
 26 .comment      000000e0  00000000  00000000  0021bca9  2**0
                  CONTENTS, READONLY
 27 .ARM.attributes 0000002f  00000000  00000000  0021bd89  2**0
                  CONTENTS, READONLY
 28 .debug_frame  0001b1a8  00000000  00000000  0021bdb8  2**2
                  CONTENTS, READONLY, DEBUGGING
 29 .debug_loc    000000de  00000000  00000000  00236f60  2**0
                  CONTENTS, READONLY, DEBUGGING
SYMBOL TABLE:

Thank you very much for your reply.

Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:12 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Nov 04 11:20:11 MST 2015
Sorry, I forgot to ask previously - can you also post the contents of the disassembly of the *.axf.o" file generated (in addition to the *.axf).

Regards,
LPCXpresso Support

Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:12 GMT

Content originally posted in LPCWare by briching on Thu Nov 05 09:24:15 MST 2015
Hi, thanks again for helping me with this. I've been developing since then in the m4 core, so the m0 core may have rebuilt as a result of a few of my changes, so I'm resubmitting both of the dissassembled files. However, I don't think any changes in my link line would be significant enough to repost.

C:\git\Embedded\XXXX_m0\Debug\XXXX_m0.axf.o:     file format elf32-littlearm
C:\git\Embedded\XXXX_m0\Debug\XXXX_m0.axf.o
architecture: arm, flags 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x1b012685

Program Header:
0x70000001 off    0x00057178 vaddr 0x1b04f178 paddr 0x1b04f178 align 2**2
         filesz 0x00000318 memsz 0x00000318 flags r--
    LOAD off    0x00008000 vaddr 0x1b000000 paddr 0x1b000000 align 2**15
         filesz 0x0004f490 memsz 0x0004f490 flags r-x
    LOAD off    0x00058000 vaddr 0x28000000 paddr 0x1b04f490 align 2**15
         filesz 0x00000fc8 memsz 0x00000fc8 flags rw-
    LOAD off    0x00058fc8 vaddr 0x00000000 paddr 0x00000000 align 2**15
         filesz 0x00000000 memsz 0x00000000 flags rw-
private flags = 5000202: [Version5 EABI] [soft-float ABI] [has entry point]

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .core_m0app   0004ef20  1b000000  1b000000  00008000  2**3
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .core_m0app.data 00000fc8  28000000  1b04f490  00058000  2**3
                  CONTENTS, ALLOC, LOAD, DATA
  2 .core_m0app.data_RAM2 00000000  28800000  28800000  00058fc8  2**2
                  CONTENTS
  3 .core_m0app.data_RAM3 00000000  10000000  10000000  00058fc8  2**2
                  CONTENTS
  4 .core_m0app.data_RAM4 00000000  10080000  10080000  00058fc8  2**2
                  CONTENTS
  5 .core_m0app.data_RAM5 00000000  20000000  20000000  00058fc8  2**2
                  CONTENTS
  6 .core_m0app.data_RAM6 00000000  20008000  20008000  00058fc8  2**2
                  CONTENTS
  7 .core_m0app.data_RAM7 00000000  2000c000  2000c000  00058fc8  2**2
                  CONTENTS
  8 .core_m0app.ARM.extab 00000258  1b04ef20  1b04ef20  00056f20  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  9 .core_m0app.ARM.exidx 00000318  1b04f178  1b04f178  00057178  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
 10 .uninit_RESERVED 00000000  28000000  28000000  00058fc8  2**2
                  CONTENTS
 11 .comment      000000e0  00000000  00000000  00058fc8  2**0
                  CONTENTS, READONLY
SYMBOL TABLE:

C:\git\Embedded\XXXX_m0\Debug\XXXX_m0.axf:     file format elf32-littlearm
C:\git\Embedded\XXXX_m0\Debug\XXXX_m0.axf
architecture: arm, flags 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x1b012685

Program Header:
0x70000001 off    0x00057178 vaddr 0x1b04f178 paddr 0x1b04f178 align 2**2
         filesz 0x00000318 memsz 0x00000318 flags r--
    LOAD off    0x00008000 vaddr 0x1b000000 paddr 0x1b000000 align 2**15
         filesz 0x0004f490 memsz 0x0004f490 flags r-x
    LOAD off    0x00058000 vaddr 0x28000000 paddr 0x1b04f490 align 2**15
         filesz 0x00000fc8 memsz 0x00000fc8 flags rw-
    LOAD off    0x00058fc8 vaddr 0x28000fc8 paddr 0x28000fc8 align 2**15
         filesz 0x00000000 memsz 0x0000157c flags rw-
private flags = 5000202: [Version5 EABI] [soft-float ABI] [has entry point]

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         0004ef20  1b000000  1b000000  00008000  2**3
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .data         00000fc8  28000000  1b04f490  00058000  2**3
                  CONTENTS, ALLOC, LOAD, DATA
  2 .data_RAM2    00000000  28800000  28800000  00058fc8  2**2
                  CONTENTS
  3 .data_RAM3    00000000  10000000  10000000  00058fc8  2**2
                  CONTENTS
  4 .data_RAM4    00000000  10080000  10080000  00058fc8  2**2
                  CONTENTS
  5 .data_RAM5    00000000  20000000  20000000  00058fc8  2**2
                  CONTENTS
  6 .data_RAM6    00000000  20008000  20008000  00058fc8  2**2
                  CONTENTS
  7 .data_RAM7    00000000  2000c000  2000c000  00058fc8  2**2
                  CONTENTS
  8 .bss          0000157c  28000fc8  28000fc8  00058fc8  2**3
                  ALLOC
  9 .ARM.extab    00000258  1b04ef20  1b04ef20  00056f20  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
 10 .ARM.exidx    00000318  1b04f178  1b04f178  00057178  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
 11 .uninit_RESERVED 00000000  28000000  28000000  00058fc8  2**2
                  CONTENTS
 12 .noinit_RAM2  00000000  28800000  28800000  00058fc8  2**2
                  CONTENTS
 13 .noinit_RAM3  00000000  10000000  10000000  00058fc8  2**2
                  CONTENTS
 14 .noinit_RAM4  00000000  10080000  10080000  00058fc8  2**2
                  CONTENTS
 15 .noinit_RAM5  00000000  20000000  20000000  00058fc8  2**2
                  CONTENTS
 16 .noinit_RAM6  00000000  20008000  20008000  00058fc8  2**2
                  CONTENTS
 17 .noinit_RAM7  00000000  2000c000  2000c000  00058fc8  2**2
                  CONTENTS
 18 .noinit       00000000  28002544  28002544  00058fc8  2**2
                  CONTENTS
 19 .debug_info   000c51bb  00000000  00000000  00058fc8  2**0
                  CONTENTS, READONLY, DEBUGGING
 20 .debug_abbrev 00011c3c  00000000  00000000  0011e183  2**0
                  CONTENTS, READONLY, DEBUGGING
 21 .debug_aranges 00005860  00000000  00000000  0012fdbf  2**0
                  CONTENTS, READONLY, DEBUGGING
 22 .debug_ranges 000053d8  00000000  00000000  0013561f  2**0
                  CONTENTS, READONLY, DEBUGGING
 23 .debug_macro  00020aab  00000000  00000000  0013a9f7  2**0
                  CONTENTS, READONLY, DEBUGGING
 24 .debug_line   00040836  00000000  00000000  0015b4a2  2**0
                  CONTENTS, READONLY, DEBUGGING
 25 .debug_str    00069455  00000000  00000000  0019bcd8  2**0
                  CONTENTS, READONLY, DEBUGGING
 26 .comment      000000e0  00000000  00000000  0020512d  2**0
                  CONTENTS, READONLY
 27 .ARM.attributes 0000002f  00000000  00000000  0020520d  2**0
                  CONTENTS, READONLY
 28 .debug_frame  0001b130  00000000  00000000  0020523c  2**2
                  CONTENTS, READONLY, DEBUGGING
 29 .debug_loc    000000de  00000000  00000000  0022036c  2**0
                  CONTENTS, READONLY, DEBUGGING
SYMBOL TABLE:

Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:13 GMT

Content originally posted in LPCWare by lpcxpresso-support on Thu Nov 05 18:23:17 MST 2015
Ok, so this warning message seems to be being triggered in some circumstances by the removal of the .bss sections that LPCXpresso now carries out in creating the object file version of the M0 image. [As the M4 doesn't need these when creating the overall combined image - as the M0 image will dynamically create the bss area(s) as its startup code executes once the M4 releases it from reset.]

As far as I can tell the warning itself is completely benign and can be ignored. Can you confirm that your combined M4/M0 application functions as expected?

Regards,
LPCXpresso Support

Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:14 GMT

Content originally posted in LPCWare by lpcxpresso-support on Thu Nov 05 18:23:18 MST 2015
Ok, so this warning message seems to be being triggered in some circumstances by the removal of the .bss sections that LPCXpresso now carries out in creating the object file version of the M0 image. [As the M4 doesn't need these when creating the overall combined image - as the M0 image will dynamically create the bss area(s) as its startup code executes once the M4 releases it from reset.]

As far as I can tell the warning itself is completely benign and can be ignored. Can you confirm that your combined M4/M0 application functions as expected?

Regards,
LPCXpresso Support

Re: New linker warning (warning: Empty loadable segment detected, is this intentional?) in LPCXpresso on C++ multicore projects

lpcware — Thu, 16 Jun 2016 02:26:14 GMT

Content originally posted in LPCWare by briching on Fri Nov 06 21:37:02 MST 2015
We haven't found anything terribly wrong with the way our code runs (yet). I assumed it was a result of some change that had been made to the LPCXpresso toolchain, but wasn't sure how to confirm it since there was so little information online about it. One thing we did change on our side after upgrading to the new tools was to use Freemarker linker scripts. I wanted to be reasonably certain before our release that the changes we made with the linker scripts have nothing to do with that warning.

So, many thanks to your support in looking into this. Perhaps now you have enough information to pass along to prevent a future release from emitting the warning needlessly.

Thanks again.