TMDS64GPEVM: ethernet-sbl project linker.cmd error:program will not fit into available memory !!

Hi Ahmet Baser,

Thanks for your query.

Which example you are working on ?

Any specific reason to work with old SDK?

If not, can you please try with our latest release 

https://www.ti.com/tool/download/INDUSTRIAL-COMMUNICATIONS-SDK-AM64X

https://www.ti.com/tool/download/MCU-PLUS-SDK-AM64X

Best Regards

Ashwani

Hi Ashwani Goel

Thanks for your reply.

Ashwani Goel said:

Which example you are working on ?

I am working on sbl_ospi_linux project in {mcu_plus_sdk_path}/examples/drivers/boot/sbl_ospi_linux and also I integrate enet_cpsw_rawhttpserver example into sbl_ospi_linux.

Ashwani Goel said:

Any specific reason to work with old SDK?

This project has grown too much to change versions.

When I remove unnecessary codes and strings from my code,  "GROUP 1" size is reduced to 0xa07. But I can't recude it anymore. It may be due to the contents of the libraries.  

What solution do you suggest?

Thanks...

Thanks Ahmet for update.

Ahmet Baser said:

When I build my project in Debug mode

Any specific reason for using debug mode ?

Can you please provide memory map file for debug and release mode both ?

Best Regards

Ashwani

Hi Ashwani Goel

Ashwani Goel said:

Any specific reason for using debug mode ?

For more effective debugging.

Ashwani Goel said:

Can you please provide memory map file for debug and release mode both ?

memory_maps.zip

Thanks..

Thanks Ahmet,

We will analyze the logs and get back to you.

Best Regards

Ashwani

Hi Ashwani Goel

Is there any update?

Thanks

Hi Ahmet,

Looks like MSRAM0 does not have enough memory to fit debug image file

1. Why customer allocating such a less space for MSRAM0 ?
2. 
3. Can we suggest to run with default settings in SDK example 
4. 

Best Regards

Ashwani

Hi Ashwani Goel

Thanks for your reply.

I think there was a mistake when I shared the linker.cmd file.

Actually, my project's msram settings are as follows.

    MSRAM0	: ORIGIN = 0x70000100 , LENGTH = 0x80000-0x100
    MSRAM1  : ORIGIN = 0x70080000 , LENGTH = 0x40000

Thanks..

Thanks Ahmet for update.

Can you share updated linker.cmd file ?  

Best Regards

Hi Ashwani Goel

This is updated linker.cmd file

#include "ti_enet_config.h"

--stack_size=16384
--heap_size=32768
-e_vectors_sbl  /* for SBL make sure to set entry point to _vectors_sbl */

__IRQ_STACK_SIZE = 4096;
__FIQ_STACK_SIZE = 256;
__SVC_STACK_SIZE = 256;
__ABORT_STACK_SIZE = 256;
__UNDEFINED_STACK_SIZE = 256;

SECTIONS
{
    .vectors:{} palign(8) > MSRAM_VECS
    GROUP {
        .text:   {} palign(8)
        .text.hwi: palign(8)
        .text.cache: palign(8)
        .text.mpu: palign(8)
        .text.boot: palign(8)
        .data:   {} palign(8)
        .rodata: {} palign(8)
    } > MSRAM0
    GROUP {
		.sysmem: {} palign(8)
    	.stack:  {} palign(8)
    } > MSRAM1

    GROUP {
	    .bss:    {} palign(8)
    	RUN_START(__BSS_START)
    	RUN_END(__BSS_END)
    } > MSRAM1


    GROUP {
        .irqstack: {. = . + __IRQ_STACK_SIZE;} align(8)
        RUN_START(__IRQ_STACK_START)
        RUN_END(__IRQ_STACK_END)
        .fiqstack: {. = . + __FIQ_STACK_SIZE;} align(8)
        RUN_START(__FIQ_STACK_START)
        RUN_END(__FIQ_STACK_END)
        .svcstack: {. = . + __SVC_STACK_SIZE;} align(8)
        RUN_START(__SVC_STACK_START)
        RUN_END(__SVC_STACK_END)
        .abortstack: {. = . + __ABORT_STACK_SIZE;} align(8)
        RUN_START(__ABORT_STACK_START)
        RUN_END(__ABORT_STACK_END)
        .undefinedstack: {. = . + __UNDEFINED_STACK_SIZE;} align(8)
        RUN_START(__UNDEFINED_STACK_START)
        RUN_END(__UNDEFINED_STACK_END)
    } > MSRAM1


        /* General purpose user shared memory, used in some examples */
    .bss.user_shared_mem (NOLOAD) : {} > USER_SHM_MEM
    /* this is used when Debug log's to shared memory are enabled, else this is not used */
    .bss.log_shared_mem  (NOLOAD) : {} > LOG_SHM_MEM
    /* this is used only when IPC RPMessage is enabled, else this is not used */
    .bss.ipc_vring_mem   (NOLOAD) : {} > RTOS_NORTOS_IPC_SHM_MEM


    .enet_dma_mem {
        *(*ENET_DMA_DESC_MEMPOOL)
        *(*ENET_DMA_RING_MEMPOOL)
#if (ENET_SYSCFG_PKT_POOL_ENABLE == 1)
        *(*ENET_DMA_PKT_MEMPOOL)
#endif
    } (NOLOAD) {} ALIGN (128) > DDR

    .bss:ENET_DMA_OBJ_MEM (NOLOAD) {} ALIGN (128) > MSRAM1
    .bss:ENET_DMA_PKT_INFO_MEMPOOL (NOLOAD) {} ALIGN (128) > MSRAM1
    .bss:ENET_ICSSG_OCMC_MEM (NOLOAD) {} ALIGN (128) > MSRAM1
}

/*
NOTE: Below memory is reserved for DMSC usage
 - During Boot till security handoff is complete
   0x701E0000 - 0x701FFFFF (128KB)
 - After "Security Handoff" is complete (i.e at run time)
   0x701FC000 - 0x701FFFFF (16KB)

 Security handoff is complete when this message is sent to the DMSC,
   TISCI_MSG_SEC_HANDOVER

 This should be sent once all cores are loaded and all application
 specific firewall calls are setup.
*/

MEMORY
{
	R5F_VECS  : ORIGIN = 0x00000000 , LENGTH = 0x00000040
    R5F_TCMA  : ORIGIN = 0x00000040 , LENGTH = 0x00007FC0
    R5F_TCMB0 : ORIGIN = 0x41010000 , LENGTH = 0x00008000
    MSRAM_VECS: ORIGIN = 0x70000000 , LENGTH = 0x100
    /* when using multi-core application's i.e more than one R5F/M4F active, make sure
     * this memory does not overlap with other R5F's
     */
    MSRAM0	: ORIGIN = 0x70000100 , LENGTH = 0x80000-0x100
    MSRAM1  : ORIGIN = 0x70080000 , LENGTH = 0x40000

    /* This section can be used to put XIP section of the application in flash, make sure this does not overlap with
     * other CPUs. Also make sure to add a MPU entry for this section and mark it as cached and code executable
     */
    FLASH     : ORIGIN = 0x60200000 , LENGTH = 0x100000

    /* when using multi-core application's i.e more than one R5F/M4F active, make sure
     * this memory does not overlap with other R5F's
     */
    DDR       : ORIGIN = 0x80000000 , LENGTH = 0x1F0000

    /* shared memory segments */
    /* On R5F,
     * - make sure there is a MPU entry which maps below regions as non-cache
     */
    USER_SHM_MEM            : ORIGIN = 0x701D0000, LENGTH = 0x00004000
    LOG_SHM_MEM             : ORIGIN = 0x701D4000, LENGTH = 0x00004000
    RTOS_NORTOS_IPC_SHM_MEM : ORIGIN = 0x701D8000, LENGTH = 0x00008000
}

Thanks..

Hi Ahmet,

To reproduce the issue on my setup.

1. I opened "C:\ti\mcu_plus_sdk_am64x_08_05_00_24\examples\drivers\boot\sbl_ospi_linux\am64x-evm\r5fss0-0_nortos" in ccs
2. By default build mode was debug only.
3. Right click on project and build.
4. It is passing.

• Can you try same thing on your setup?
• If yes, what next step I need to follow ?
• May I know your goal, what you want to achieve (end goal) ?

One quick thing you can try is change in linker.cmd file as below:

MSRAM0 : ORIGIN = 0x70000100 , LENGTH = 0xC0000-0x100
MSRAM1 : ORIGIN = 0x700C0000 , LENGTH = 0x40000

Best Regards

Ashwani

Hi Ashwani Goel

Ashwani Goel said:

what next step I need to follow ?

You should integrate enet_cpsw_rawhttpserver example into "C:\ti\mcu_plus_sdk_am64x_08_05_00_24\examples\drivers\boot\sbl_ospi_linux\am64x-evm\r5fss0-0_nortos" project. You must make syscfg settings for the enet module and add the necessary source and header files. As a result, you should be able to run Ethernet properly. I can say that this is my main purpose.

Ashwani Goel said:

MSRAM0 : ORIGIN = 0x70000100 , LENGTH = 0xC0000-0x100
MSRAM1 : ORIGIN = 0x700C0000 , LENGTH = 0x40000

Ok, I will try this but If I do it this way, won't I be occupying the msram region of the r5-0-0 core?

I know that addresses 0x70000000 and 0x70080000 are allocated for SBL.

Thanks...

Hi Ahmet,

Ahmet Baser said:

won't I be occupying the msram region of the r5-0-0 core?

you can move R5F_0_0 region forward. Assuming you are not using any other R5F core ?

Best Regards

Ashwani

Hi Ashwani Goel

Ashwani Goel said:

you can move R5F_0_0 region forward. Assuming you are not using any other R5F core ?

I don't use it for now, but I am planning to use it in the future. So it will be better if I don't move it to r5f0-0 region of MSRAM.

Thanks...

Ahmet Baser said:

I don't use it for now, but I am planning to use it in the future. So it will be better if I don't move it to r5f0-0 region of MSRAM.

Are you planning to use all R5F cores ?

Still, I am suggesting as a permanent changes.

Just trying get build successful and get memory map in debug mode.

So, please,

1. Expand MSRAM0 length
2. Shift MSRAM1
3. Move R5_0_0 to R5F_0_1 MSRAM
4. and let me know, if you get build successfully.

Best Regards

Ashwani