• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 215 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.

TDA4AH-Q1: sbl boot mcu1_1 entry point

li quan
Intellectual 945 points
Part Number: TDA4AH-Q1

Hi  TI expert,

We tried to boot mcu1_1 through sbl, but found that mcu1_1 could not be started successfully if the entry point was set to ATCM, BTCM or DDR. Only if the entry point was set in MSMC (such as 0x70012000), it could be started successfully. Is this a normal phenomenon?

Best regards !

QuanLi

  • 0
    TI__Mastermind 42135 points

    Hi Quan,

    No, you should be able to boot with entry point in ATCM without any issues.

    Can you please share more details? Which SDK version are you using? What example are you trying to load?

    Also, did you try running IPC echo test on MCU1_1?  I believe that places entry point in TCMs.

    Regards,
    Parth

  • 0 in reply to Parth Nagpal
    Intellectual 945 points

    Hi Parth,

    SDK:8.6

    The test firmware is compiled with make sbl_boot_test BOARD=j784s4_evm CORE=mcu1_1.

    The code change point is:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    --- boot/sbl/example/k3MulticoreApp/j784s4/mcuAmplinker.lds (revision 438697)
    +++ boot/sbl/example/k3MulticoreApp/j784s4/mcuAmplinker.lds (working copy)
    @@ -12,7 +12,7 @@
    MEMORY
    {
    MSMC3_MCU1_CPU0 : origin=0x70010000 length=0x2000 /* 8KB */
    - MSMC3_MCU1_CPU1 : origin=0x70012000 length=0x2000 /* 8KB */
    + MSMC3_MCU1_CPU1 : origin=0x41410000 length=0x2000 /* 8KB */
    MSMC3_MCU2_CPU0 : origin=0x70014000 length=0x2000 /* 8KB */
    MSMC3_MCU2_CPU1 : origin=0x70016000 length=0x2000 /* 8KB */
    MSMC3_MCU3_CPU0 : origin=0x70018000 length=0x2000 /* 8KB */
    --- boot/sbl/sbl_component.mk (revision 438697)
    +++ boot/sbl/sbl_component.mk (working copy)
    @@ -1219,7 +1219,7 @@
    # SBL log level
    # no logs = 0, only errors =1, normal logs = 2, all logs = 3
    -SBL_CFLAGS += -DSBL_LOG_LEVEL=2
    +SBL_CFLAGS += -DSBL_LOG_LEVEL=3
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


    Entry point 0x70012000(MSMC), the SBL logs are as follows:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    SBL Revision: 01.00.10.01 (Aug 23 2023 - 15:11:55)
    TIFS ver: 8.6.3--v08.06.03 (Chill Capybar
    SCISERVER Board Configuration header population... PASSED
    Sciclient_setBoardConfigHeader... PASSED
    Initlialzing PLLs ...done.
    InitlialzingClocks ...done.
    Initlialzing DDR ...done.
    Initializing GTC ...Board_control failed to configure MUX2 A <-> B2
    Begin parsing user application
    Calling Sciclient_procBootRequestProcessor, ProcId 0x20...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x21...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x22...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x23...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x24...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x25...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x26...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x27...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x1...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x2...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x6...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x7...
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Entry point 0x41400000(ATCM), the SBL logs are as follows:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    SBL Revision: 01.00.10.01 (Aug 23 2023 - 15:11:55)
    TIFS ver: 8.6.3--v08.06.03 (Chill Capybar
    SCISERVER Board Configuration header population... PASSED
    Sciclient_setBoardConfigHeader... PASSED
    Initlialzing PLLs ...done.
    InitlialzingClocks ...done.
    Initlialzing DDR ...done.
    Initializing GTC ...Board_control failed to configure MUX2 A <-> B2
    Begin parsing user application
    Calling Sciclient_procBootRequestProcessor, ProcId 0x20...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x21...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x22...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x23...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x24...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x25...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x26...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x27...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x1...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x2...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x6...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x7...
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    MCU1_1 running print is missing ，compared to entry point 0x70012000.

    Entry point 0x41410000(BTCM), the SBL logs are as follows:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    SBL Revision: 01.00.10.01 (Aug 23 2023 - 15:11:55)
    TIFS ver: 8.6.3--v08.06.03 (Chill Capybar
    SCISERVER Board Configuration header population... PASSED
    Sciclient_setBoardConfigHeader... PASSED
    Initlialzing PLLs ...done.
    InitlialzingClocks ...done.
    Initlialzing DDR ...done.
    Initializing GTC ...Board_control failed to configure MUX2 A <-> B2
    Begin parsing user application
    Calling Sciclient_procBootRequestProcessor, ProcId 0x20...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x21...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x22...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x23...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x24...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x25...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x26...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x27...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x1...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x2...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x6...
    Calling Sciclient_procBootRequestProcessor, ProcId 0x7...
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    MCU1_1 running print is missing ，compared to entry point 0x70012000.

    Regards,

    QuanLi

  • 0 in reply to li quan
    TI__Mastermind 42135 points

    Hi Quan,

    Apologies for delay on this.

    Is the support still required on this topic? Can you please share the current state of the issue?

    Regards,
    Parth