• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 102 subscribers
  • Views 181 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VH-Q1: SBL:segment overflow when linking

zhisong zheng
Intellectual 431 points
Part Number: TDA4VH-Q1

Tool/software:

Hi,experts:

I am developing on the SDK version 08_06_01_03.

When we were developing SBL, we encountered the problem of segment overflow when linking, log as follows:

In order to solve this problem, looking through the compiler manual, we found a way to solve this problem

As shown below, we have changed the link options, The specific file is Ti-processor-SDK-RTOs-J784S4-EVM-08_06_01_03 \pdk_j784s4_08_06_01_03\packages\ti\build\makerules\rules_ti_cgt_arm.mk

However, after this change, the program does not work properly, we use the debugger to locate the location of the code jam

We still need to make some additional changes ? Or is there any way to solve our problems?

  • 0
    TI__Expert 5490 points

    Hi,

    zhisong zheng said:

    When we were developing SBL, we encountered the problem of segment overflow when linking, log as follows:

    Are you referring this https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1395618/tda4vh-q1-when-sbl-is-compiled-the-cinit-segment-is-placed-in-msmc same issue here also ? if so please share your linker.cmd file.

    Regards,

    Karthik

  • 0 in reply to Karthikeyan S
    Intellectual 431 points

    It's not the same problem. Here we did not change the link file of SBL, but changed the link option, and the link option was changed from -c to -cr

  • 0 in reply to zhisong zheng
    TI__Expert 5490 points

    Hi,

    zhisong zheng said:
    It's not the same problem. Here we did not change the link file of SBL, but changed the link option, and the link option was changed from -c to -c

    I'll look into this and get back to you.

    Regards,

    Karthik

  • 0 in reply to Karthikeyan S
    Intellectual 431 points

    Any new information syncing?

  • 0 in reply to zhisong zheng
    TI__Expert 5490 points

    Hi,

    zhisong zheng said:

    When we were developing SBL, we encountered the problem of segment overflow when linking, log as follows:

    I am not receiving any errors when building. Have you made any changes to SBL? If yes, could you please share those changes?

    karthikeyansaravanan@LAP678U:~/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/build$ make BOARD=j784s4_evm CORE=mcu1_0 sbl_ospi_img  DISABLE_RECURSE_DEPS=no -sj6
# Compiling j784s4_evm:j784s4:mcu1_0:release:sbl_ospi_img:sbl_main.c
# Linking into /home/karthikeyansaravanan/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/binary/j784s4_evm/ospi/bin/sbl_ospi_img_mcu1_0_release.xer5f...
#
#
# /home/karthikeyansaravanan/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/binary/j784s4_evm/ospi/bin/sbl_ospi_img_mcu1_0_release.xer5f created.
#
# Generating stripped image into /home/karthikeyansaravanan/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/binary/j784s4_evm/ospi/bin/sbl_ospi_img_mcu1_0_release_strip.xer5f...
#
~/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/board/k3 ~/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/board/k3

Debug Extension is Enabled :
SoC UID not specified for Debug Extension. Using UID 0
	UID = 0000000000000000000000000000000000000000000000000000000000000000
	DBG_TYPE = 4
R5 Certificate being generated :
	X509_CFG = ./x509-temp.cfg
	KEY = /home/karthikeyansaravanan/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/build/makerules/rom_degenerateKey.pem
	BIN = /home/karthikeyansaravanan/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/binary/j784s4_evm/ospi/bin/sbl_ospi_img_mcu1_0_release.bin
	CERT TYPE = R5, 1
	CORE ID = 16
	LOADADDR = 0x41c00100
	IMAGE_SIZE = 385872
	BOOT_OPTIONS = 2
SUCCESS: Image /home/karthikeyansaravanan/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/binary/j784s4_evm/ospi/bin/sbl_ospi_img_mcu1_0_release.tiimage generated. Good to boot
# SBL image /home/karthikeyansaravanan/ti/ti-processor-sdk-rtos-j784s4-evm-08_06_01_03/pdk_j784s4_08_06_01_03/packages/ti/boot/sbl/binary/j784s4_evm/ospi/bin/sbl_ospi_img_mcu1_0_release.bin created.
#


    Regards,

    Karthik

  • 0 in reply to Karthikeyan S
    Intellectual 431 points

    The compilation is normal, but it cannot run properly. For details, please see my problem description

  • 0 in reply to zhisong zheng
    TI__Expert 5490 points

    Hi,

    zhisong zheng said:
    we encountered the problem of segment overflow when linking, log as follows:

    I'm hoping that you got the segment overflow issue before changing from -c to -cr,  with fresh SDK I am not receiving any errors when building. Have you made any changes to SBL? If yes, could you please share those changes?

    zhisong zheng said:

    However, after this change, the program does not work properly, we use the debugger to locate the location of the code jam

    I'll replicate the problem on my end and get back to you.


    Regards,

    Karthik