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.

TDA4VM: PBIST/LBIST execute error

Part Number: TDA4VM

We want to execute PBIST and LBIST in MCU, so change the file below.
psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/makefile
BISTFUNC ?= enabled

And turn on the debug macro .
But something wrong .
Log:
For HW POST LBIST core 0, Expected MISR= 0xe851b017, Calculated MISR = 0xe851b017
HW POST core: HWPOST - DMSC: result = 0
For HW POST LBIST core 1, Expected MISR= 0x296b47db, Calculated MISR = 0x296b47db
HW POST core: HWPOST - MCU: result = 0
Ran PBIST for Stage 0

HwiP_Params_init complete
Primary core: Main R5F0-0: Requesting processor
Secondary core: Main R5F1-0: Requesting processor
Primary core: Putting in module and local reset the core Main R5F0-0
Secondary core: Putting in module and local reset the core Main R5F1-0
Primary core: Putting into Retention Main R5F0-0
Secondary core: Putting into Retention Main R5F1-0

Starting CSL_LBIST_enableIsolation

Starting CSL_LBIST_reset

Starting CSL_LBIST_enabledRunBISTMode

Starting CSL_LBIST_start

Starting CSL_LBIST_isRunning
LBIST not running

Starting CSL_LBIST_getMISR

Starting CSL_LBIST_getExpectedMISR

Starting CSL_LBIST_clearRunBISTMode

Starting CSL_LBIST_stop

Starting CSL_LBIST_reset
Secondary core: Powering off Main R5F1-0
Primary core: Powering off Main R5F0-0
Disabling isolation
Primary core: Putting into Retention Main R5F0-0
Secondary core: Putting into Retention Main R5F1-0
Checking that LBIST is not running
Secondary core: Powering off Main R5F1-0
Primary core: Powering off Main R5F0-0
Primary core: Taking out of local reset the core Main R5F0-0
Secondary core: Taking out of local reset the core Main R5F1-0
Primary core: Releasing Main R5F0-0
Secondary core: Releasing Main R5F1-0

LBIST failed with MISR mismatch: Expected 0xad7f4501 got 0x31669786
LBIST functional test failed for 2
Ran LBIST for Stage 0

ESM Call back function called : instType 0x3, intType 0x1, grpChannel 0x8, index 0x6, intSrc 0x106

ESM Call back function called : instType 0x3, intType 0x1, grpChannel 0x8, index 0x6, intSrc 0x106
Ra
ESM Call back function called : instType 0x3, intType 0x1, grpChannel 0x8, index 0x6, intSrc 0x106
n PBIST for Stage 1

HwiP_Params_init complete
Primary core: Main R5F1-0: Requesting processor
Secondary core: Main R5F1-1: Requesting processor
Primary core: Putting in module and local reset the core Main R5F1-0
Secondary core: Putting in module and local reset the core Main R5F1-1
Primary core: Putting into Retention Main R5F1-0
Secondary core: Putting into Retention Main R5F1-1

Starting CSL_LBIST_enableIsolation

Starting CSL_LBIST_reset

Starting CSL_LBIST_enabledRunBISTMode

Starting CSL_LBIST_start

Starting CSL_LBIST_isRunning
LBIST not running

Starting CSL_LBIST_getMISR

Starting CSL_LBIST_getExpectedMISR

Starting CSL_LBIST_clearRunBISTMode

Starting CSL_LBIST_stop

Starting CSL_LBIST_reset
Secondary core: Powering off Main R5F1-1
Primary core: Powering off Main R5F1-0
Disabling isolation
Primary core: Putting into Retention Main R5F1-0
Secondary core: Putting into Retention Main R5F1-1
Checking that LBIST is not running
Secondary core: Powering off Main R5F1-1
Primary core: Powering off Main R5F1-0
Primary core: Taking out of local reset the core Main R5F1-0
Secondary core: Taking out of local reset the core Main R5F1-1
Primary core: Releasing Main R5F1-0
Secondary core: Releasing Main R5F1-1

LBIST failed with MISR mismatch: Expected 0xad7f4501 got 0x31669786
LBIST functional test failed for 3
Ran LBIST for Stage 1
Ran PBIST for Stage 2

HwiP_Params_init complete
Primary core: A72 core 0: Requesting processor
Secondary core: A72 core 1: Requesting processor
Putting into module reset Device number 0 Device Id 4
Primary core: Putting in module and local reset the core A72 core 0
Secondary core: Putting in module and local reset the core A72 core 1
Putting into Retention Device number 0 Device Id 4
Primary core: Putting into Retention A72 core 0
Secondary core: Putting into Retention A72 core 1

Starting CSL_LBIST_enableIsolation

Starting CSL_LBIST_reset

Starting CSL_LBIST_enabledRunBISTMode

Starting CSL_LBIST_start

Starting CSL_LBIST_isRunning
LBIST not running

Starting CSL_LBIST_getMISR

Starting CSL_LBIST_getExpectedMISR

Starting CSL_LBIST_clearRunBISTMode

Starting CSL_LBIST_stop

Starting CSL_LBIST_reset
Secondary core: Powering off A72 core 1
Primary core: Powering off A72 core 0
Powering off Device number 0 Device Id 4
Disabling isolation
Putting into Retention Device number 0 Device Id 4
Primary core: Putting into Retention A72 core 0
Secondary core: Putting into Retention A72 core 1
Checking that LBIST is not running
Secondary core: Powering off A72 core 1
Primary core: Powering off A72 core 0
Powering off Device number 0 Device Id 4
Primary core: Taking out of local reset the core A72 core 0
Secondary core: Taking out of local reset the core A72 core 1
Putting into module reset Device number 0 Device Id 4
Primary core: Releasing A72 core 0
Secondary core: Releasing A72 core 1

LBIST failed with MISR mismatch: Expected 0xdd5cd3b3 got 0x3358dd14
LBIST functional test failed for 7
Ran LBIST for Stage 2

  • We are using SDK version 8.4.

  • As to the differnt partnumber stage , such as ES1_1 , PG1.1 , PG2.0  the Test vector is different ,  casue the diffect expect output.  when we get the MISR mismatch. Could you please check part number fistly. 

  • TKS meng

        we use the configuration parameters of ES1_1 to test BIST? The BIST has passed and the log is as follows. However, MCU2_0/MCU2_1/MCU3_0/MCU3_1 failed to start up.

    Starting Sciserver..... PASSED
    start I2C_Init !
    start Pmic_I2C_InstanceInit !
    setConfigI2C baseAddr=1108475904 !
    IIC : I2C_open i2cHandle =1104010532!
    end Pmic_I2C_InstanceInit i2c_instance=0 i2cHandle =1104010532!
    Main I2c BUS PMIC_INTF_SINGLE_I2C with status
    Main I2c BUS PMIC_INTF_SINGLE_I2C with status
    pmicb_ldo12_vmon_disable
    get 0x1D ldo1_ctrl: 0x31
    set 0x1D ldo1_ctrl: 0x21
    get 0x1E ldo2_ctrl: 0x31
    set 0x1E ldo2_ctrl: 0x21
    SPI cbMode
    SPI Interrupt NO DMA mode!
    The interrupt path has been set with interrupt number 21
    SPI Slave Mode
    ADC_APP: Variant - Post Build being used !!!
    ADC_Func: ADC Setup - DONE !!!
    FS_PMICA FS_PMIC_glHisErrData = 0x10000 FS_PMIC_glRunErrData
    ESM Call back function called : instType 0x3, intType 0x1, grpChannel 0x8, index 0x6, intSrc 0x106
    0 = 0x0 FS_PMIC_
    ESM Call back function called : instType 0x3, intType 0x1, grpChannel 0x8, index 0x6, intSrc 0x106
    glRunErrData1 = 0x0
    FS_PMICB FS_PMICB_glHisErrData = 0x4000 FS_PMICB_glRunErrData0 = 0x0 FS_PMICB_glRunErrData1 = 0x0
    ADC_APP: Sample Application - STARTS !!!
    Adc_Ipc_Init called
    BIST: Pre-boot stage - Started at 88711 usec
    BIST: Pre-boot Stage - Ran PBIST ID - PBIST_INSTANCE_MAIN_INFRA, Result = PASS
    BIST: Pre-boot Stage - Ran PBIST ID - PBIST_INSTANCE_MSMC, Result = PASS
    Pre-boot stage - Ran 2 PBIST total sections
    BIST: Pre-boot Stage - Ran LBIST ID - LBIST_HWPOST_DMSC_INDEX, Result = LBIST_POST_COMPLETED_SUCCESS
    BIST: Pre-boot Stage - Ran LBIST ID - LBIST_HWPOST_MCU_INDEX, Result = LBIST_POST_COMPLETED_SUCCESS
    Pre-boot stage - Ran 2 LBIST total sections
    BIST: Stage 0 - Started running PBIST sections at 119014 usec
    BIST: Stage 0 - Ran PBIST ID - PBIST_INSTANCE_MAIN_PULSAR_0, Result = PASS
    BIST: Stage 0 - Ran 1 PBIST total sections
    BIST: Stage 0 - Started running LBIST sections at 119839 usec
    BIST: Stage 0 - Ran LBIST ID - LBIST_MAIN_MCU0_INDEX, Result = PASS
    BIST: Stage 0 - Ran 1 LBIST sections
    BIST: Stage 0 - Completed stage at 137703 usec
    BIST: Stage 1 - Started running PBIST sections at 137703 usec
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_MAIN_PULSAR_1, Result = PASS
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_C7X, Result = PASS
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_C66X_0, Result = PASS
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_C66X_1, Result = PASS
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_VPAC, Result = PASS
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_DMPAC, Result = PASS
    BIST: Stage 1 - Ran 6 PBIST total sections
    BIST: Stage 1 - Started running LBIST sections at 185128 usec
    BIST: Stage 1 - Ran LBIST ID - LBIST_MAIN_MCU1_INDEX, Result = PASS
    BIST: Stage 1 - Ran LBIST ID - LBIST_C7X_CORE_INDEX, Result = PASS
    BIST: Stage 1 - Ran LBIST ID - LBIST_VPAC_INDEX, Result = PASS
    BIST: Stage 1 - Ran LBIST ID - LBIST_DMPAC_INDEX, Result = PASS
    BIST: Stage 1 - Ran 4 LBIST sections
    BIST: Stage 1 - Completed stage at 221105 usec
    BIST: Stage 2 - Started running PBIST sections at 221105 usec
    BIST: Stage 2 - Ran PBIST ID - PBIST_INSTANCE_A72, Result = PASS
    BIST: Stage 2 - Ran PBIST ID - PBIST_INSTANCE_HC, Result = PASS
    BIST: Stage 2 - Ran PBIST ID - PBIST_INSTANCE_ENCODER, Result = PASS
    BIST: Stage 2 - Ran 3 PBIST total sections
    BIST: Stage 2 - Started running LBIST sections at 230273 usec
    BIST: Stage 2 - Ran LBIST ID - LBIST_A72_CORE_INDEX, Result = PASS
    BIST: Stage 2 - Ran 1 LBIST sections
    BIST: Stage 2 - Completed stage at 248047 usec
    OSPI flash left configured in Legacy SPI mode.

    OSPI NOR device ID: 0x5b1a, manufacturer ID: 0x2c
    Boot App: Started at 88527 usec
    Boot App: Total Num booted cores = 8
    Boot App: Booted Core ID #10 at 415684 usecs
    Boot App: Booted Core ID #11 at 415906 usecs
    Boot App: Booted Core ID #12 at 1226209 usecs
    Boot App: Booted Core ID #13 at 1226426 usecs
    Boot App: Booted Core ID #16 at 1226621 usecs
    Boot App: Booted Core ID #17 at 1226814 usecs
    Boot App: Booted Core ID #18 at 1227527 usecs
    Boot App: Booted Core ID #0 at 3094427 usecs

    MCU Boot Task started at 88527 usecs and finished at 9160859 usecs


    root@c801soc1:~# cd /opt/vision_apps/
    root@c801soc1:/opt/vision_apps# source ./vision_apps_init.sh
    root@c801soc1:/opt/vision_apps# [MCU2_0] 0.619619 s: CIO: Init ... Done !!!
    [MCU2_0] 0.619687 s: ### CPU Frequency = 1000000000 Hz
    [MCU2_0] 0.619732 s: APP: Init ... !!!
    [MCU2_0] 0.619758 s: SCICLIENT: Init ... !!!
    [MCU2_0] 0.619976 s: SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [MCU2_0] 0.620025 s: SCICLIENT: DMSC FW revision 0x8
    [MCU2_0] 0.620060 s: SCICLIENT: DMSC FW ABI revision 3.1
    [MCU2_0] 0.620097 s: SCICLIENT: Init ... Done !!!
    [MCU2_0] 0.620124 s: UDMA: Init ... !!!
    [MCU2_0] 0.621230 s: UDMA: Init ... Done !!!
    [MCU2_0] 0.621291 s: MEM: Init ... !!!
    [MCU2_0] 0.621335 s: MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ d9000000 of size 16777216 bytes !!!
    [MCU2_0] 0.621414 s: MEM: Created heap (L3_MEM, id=1, flags=0x00000000) @ 3600000 of size 262144 bytes !!!
    [MCU2_0] 0.621482 s: MEM: Init ... Done !!!
    [MCU2_0] 0.621507 s: IPC: Init ... !!!
    [MCU2_0] 0.621581 s: IPC: 8 CPUs participating in IPC !!!
    [MCU2_0] 0.621634 s: IPC: Waiting for HLOS to be ready ... !!!
    [MCU2_0] 9.945193 s: IPC: HLOS is ready !!!
    [MCU2_0] 9.965884 s: IPC: Init ... Done !!!
    [MCU2_0] 9.965950 s: APP: Syncing with 7 CPUs ... !!!
    [MCU2_0] 20.589584 s: ERROR: core init timeout !! stop feed rti 8 thread to report esm!!
    [MCU2_1] 0.506711 s: CIO: Init ... Done !!!
    [MCU2_1] 0.506779 s: ### CPU Frequency = 1000000000 Hz
    [MCU2_1] 0.506826 s: APP: Init ... !!!
    [MCU2_1] 0.506853 s: SCICLIENT: Init ... !!!
    [MCU2_1] 0.507068 s: SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [MCU2_1] 0.507118 s: SCICLIENT: DMSC FW revision 0x8
    [MCU2_1] 0.507155 s: SCICLIENT: DMSC FW ABI revision 3.1
    [MCU2_1] 0.507193 s: SCICLIENT: Init ... Done !!!
    [MCU2_1] 0.507220 s: UDMA: Init ... !!!
    [MCU2_1] 0.508447 s: UDMA: Init ... Done !!!
    [MCU2_1] 0.508505 s: MEM: Init ... !!!
    [MCU2_1] 0.508550 s: MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ da000000 of size 16777216 bytes !!!
    [MCU2_1] 0.508623 s: MEM: Created heap (L3_MEM, id=1, flags=0x00000001) @ 3640000 of size 262144 bytes !!!
    [MCU2_1] 0.508683 s: MEM: Init ... Done !!!
    [MCU2_1] 0.508709 s: IPC: Init ... !!!
    [MCU2_1] 0.508770 s: IPC: 8 CPUs participating in IPC !!!
    [MCU2_1] 0.508824 s: IPC: Waiting for HLOS to be ready ... !!!
    [MCU2_1] 10.318548 s: IPC: HLOS is ready !!!
    [MCU2_1] 10.339322 s: IPC: Init ... Done !!!
    [MCU2_1] 10.339392 s: APP: Syncing with 7 CPUs ... !!!
    [MCU2_1] 20.506273 s: ERROR: core init timeout !! stop feed rti 9 thread to report esm!!
    [MCU3_0] 1.316355 s: CIO: Init ... Done !!!
    [MCU3_0] 1.316426 s: ### CPU Frequency = 1000000000 Hz
    [MCU3_0] 1.316471 s: APP: Init ... !!!
    [MCU3_0] 1.316498 s: SCICLIENT: Init ... !!!
    [MCU3_0] 1.316811 s: SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [MCU3_0] 1.316871 s: SCICLIENT: DMSC FW revision 0x8
    [MCU3_0] 1.316908 s: SCICLIENT: DMSC FW ABI revision 3.1
    [MCU3_0] 1.316945 s: SCICLIENT: Init ... Done !!!
    [MCU3_0] 1.316973 s: MEM: Init ... !!!
    [MCU3_0] 1.317010 s: MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ db000000 of size 8388608 bytes !!!
    [MCU3_0] 1.317078 s: MEM: Init ... Done !!!
    [MCU3_0] 1.317105 s: IPC: Init ... !!!
    [MCU3_0] 1.317166 s: IPC: 8 CPUs participating in IPC !!!
    [MCU3_0] 1.317219 s: IPC: Waiting for HLOS to be ready ... !!!
    [MCU3_0] 10.466907 s: IPC: HLOS is ready !!!
    [MCU3_0] 10.487923 s: IPC: Init ... Done !!!
    [MCU3_0] 10.487994 s: APP: Syncing with 7 CPUs ... !!!
    [MCU3_0] 21.315903 s: ERROR: core init timeout !! stop feed rti 10 thread to report esm!!
    [MCU3_1] 1.316329 s: CIO: Init ... Done !!!
    [MCU3_1] 1.316401 s: ### CPU Frequency = 1000000000 Hz
    [MCU3_1] 1.316443 s: APP: Init ... !!!
    [MCU3_1] 1.316469 s: SCICLIENT: Init ... !!!
    [MCU3_1] 1.316743 s: SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [MCU3_1] 1.316796 s: SCICLIENT: DMSC FW revision 0x8
    [MCU3_1] 1.316848 s: SCICLIENT: DMSC FW ABI revision 3.1
    [MCU3_1] 1.316890 s: SCICLIENT: Init ... Done !!!
    [MCU3_1] 1.316922 s: MEM: Init ... !!!
    [MCU3_1] 1.316960 s: MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ db800000 of size 8388608 bytes !!!
    [MCU3_1] 1.317031 s: MEM: Init ... Done !!!
    [MCU3_1] 1.317060 s: IPC: Init ... !!!
    [MCU3_1] 1.317127 s: IPC: 8 CPUs participating in IPC !!!
    [MCU3_1] 1.317181 s: IPC: Waiting for HLOS to be ready ... !!!
    [MCU3_1] 10.588061 s: IPC: HLOS is ready !!!
    [MCU3_1] 10.608947 s: IPC: Init ... Done !!!
    [MCU3_1] 10.609015 s: APP: Syncing with 7 CPUs ... !!!
    [MCU3_1] 21.315870 s: ERROR: core init timeout !! stop feed rti 11 thread to report esm!!
    [C6x_1 ] 1.274618 s: CIO: Init ... Done !!!
    [C6x_1 ] 1.274645 s: ### CPU Frequency = 1350000000 Hz
    [C6x_1 ] 1.274656 s: APP: Init ... !!!
    [C6x_1 ] 1.274664 s: SCICLIENT: Init ... !!!
    [C6x_1 ] 1.274847 s: SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [C6x_1 ] 1.274860 s: SCICLIENT: DMSC FW revision 0x8
    [C6x_1 ] 1.274870 s: SCICLIENT: DMSC FW ABI revision 3.1
    [C6x_1 ] 1.274880 s: SCICLIENT: Init ... Done !!!
    [C6x_1 ] 1.274889 s: UDMA: Init ... !!!
    [C6x_1 ] 1.276319 s: UDMA: Init ... Done !!!
    [C6x_1 ] 1.276338 s: MEM: Init ... !!!
    [C6x_1 ] 1.276351 s: MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ dc000000 of size 16777216 bytes !!!
    [C6x_1 ] 1.276368 s: MEM: Created heap (L2_MEM, id=2, flags=0x00000001) @ 800000 of size 229376 bytes !!!
    [C6x_1 ] 1.276391 s: MEM: Created heap (DDR_SCRATCH_MEM, id=4, flags=0x00000001) @ dd000000 of size 50331648 bytes !!!
    [C6x_1 ] 1.276408 s: MEM: Init ... Done !!!
    [C6x_1 ] 1.276416 s: IPC: Init ... !!!
    [C6x_1 ] 1.276438 s: IPC: 8 CPUs participating in IPC !!!
    [C6x_1 ] 1.276451 s: IPC: Waiting for HLOS to be ready ... !!!
    [C6x_1 ] 9.137555 s: IPC: HLOS is ready !!!
    [C6x_1 ] 9.141201 s: IPC: Init ... Done !!!
    [C6x_1 ] 9.141227 s: APP: Syncing with 7 CPUs ... !!!
    [C6x_1 ] 21.274405 s: ERROR: core init timeout !! stop feed rti 6 thread to report esm!!
    [C6x_2 ] 1.274908 s: CIO: Init ... Done !!!
    [C6x_2 ] 1.274935 s: ### CPU Frequency = 1350000000 Hz
    [C6x_2 ] 1.274947 s: APP: Init ... !!!
    [C6x_2 ] 1.274955 s: SCICLIENT: Init ... !!!
    [C6x_2 ] 1.275128 s: SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [C6x_2 ] 1.275142 s: SCICLIENT: DMSC FW revision 0x8
    [C6x_2 ] 1.275152 s: SCICLIENT: DMSC FW ABI revision 3.1
    [C6x_2 ] 1.275162 s: SCICLIENT: Init ... Done !!!
    [C6x_2 ] 1.275171 s: UDMA: Init ... !!!
    [C6x_2 ] 1.276757 s: UDMA: Init ... Done !!!
    [C6x_2 ] 1.276777 s: MEM: Init ... !!!
    [C6x_2 ] 1.276789 s: MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ e0000000 of size 16777216 bytes !!!
    [C6x_2 ] 1.276808 s: MEM: Created heap (L2_MEM, id=2, flags=0x00000001) @ 800000 of size 229376 bytes !!!
    [C6x_2 ] 1.276823 s: MEM: Created heap (DDR_SCRATCH_MEM, id=4, flags=0x00000001) @ e1000000 of size 50331648 bytes !!!
    [C6x_2 ] 1.276840 s: MEM: Init ... Done !!!
    [C6x_2 ] 1.276848 s: IPC: Init ... !!!
    [C6x_2 ] 1.276871 s: IPC: 8 CPUs participating in IPC !!!
    [C6x_2 ] 1.276884 s: IPC: Waiting for HLOS to be ready ... !!!
    [C6x_2 ] 9.751149 s: IPC: HLOS is ready !!!
    [C6x_2 ] 9.754752 s: IPC: Init ... Done !!!
    [C6x_2 ] 9.754779 s: APP: Syncing with 7 CPUs ... !!!
    [C6x_2 ] 21.274670 s: ERROR: core init timeout !! stop feed rti 7 thread to report esm!!

  • According to the above log, the startup code for the core C7x_1 is missing. It has been tested that with enabling BIST, this core fails to start. However, when BIST is disabled, it can start normally. 

  • Hi,

    Apologies for delayed response on this topic.   

    TI has a safety assessed SDL package (Software Diagnostic Library).  TI recommendation is to use this package for BIST testing, vs the CSL version which is referenced above.

    The SDL package is available as part of the PSDK RTOS release, the public documentation for which on SDK 8.4 is available at: 3. SDK Components — Processor SDK RTOS J721E (ti.com).   The setup of the SDL is similar to SDL, and migration from CSL implementation to SDL is possible.

    Is your project tied to the SDK 8.4 release, or are there plans to move to a more recent SDK?

    Thanks,

    kb

  • Hi KB

    I am experiencing a freeze issue when testing the Pbist&Lbist functionality using the SDL library's API. Specifically, when I open the PBIST_INSTANCE_MSMC, the MCU2_0/MCU2_1/MCU3_0/MCU3_1 instances freeze during startup, similar to the log provided above. Can you please suggest a solution to this problem?

    int pbist_pre_boot_stage[] =
    {
    PBIST_HWPOST_MCU_INDEX, /* Read results of HW POST MCU PBIST */
    PBIST_INSTANCE_MAIN_INFRA, /* Main Infra - Must be in pre-boot stage */
    // PBIST_INSTANCE_MSMC /* MSMC RAM - Must be in pre-boot stage */
    };

  • Hi,

    Could you please provide more details regarding your boot flow? Have you tried testing the standalone SDL example BIST application?

    Specifically, when I open the PBIST_INSTANCE_MSMC, the MCU2_0/MCU2_1/MCU3_0/MCU3_1 instances freeze during startup

    If you do not run MSMC, do the cores come up properly?

    Regards,

    Josiitaa

  • HI 

    I had tested the  SDL example BIST application,all the test can be passed.

    Even if I enable the PBIST_INSTANCE_MSMC test option and all the test options pass, there are some cores that get stuck.102.diff

    The attachment contains all my modification codes.

  • Hi,

    I will try to reproduce the issue with your code modifications and get back to you in a couple of days.

    Regards,

    Josiitaa

  • Hi 

    In the code which i provide ,the PBIST_INSTANCE_MSMC  has been closed.

    You should reopen the option .

  • Yes understood. I will do that.

  • Hi,

    What are the additional binaries that you are using to test that the cores are running after BIST?

    Regards,

    Josiitaa

  • Just execute PBIST&LBIST&ECC test.

  • Hi,

    I do not see any ECC related modifications in the file that you had shared with me earlier. Could you send a patch of all the changes made to the baseline 8.4 SDK?

    Regards,

    Josiitaa

  • Sorry for the late answer.

    We had change the sdk8.4 to sdk 8.6.

    And ti seems like more problems with bist test.

    1) /psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/makefile -->enabled the BISTFUNC.

       But this leads to compilation failure.

       so i changed the code like this

    diff --git a/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.c b/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.c
    index e7bd1f296..95770a37a 100755
    --- a/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.c
    +++ b/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.c
    @@ -135,7 +135,7 @@ static const char *testStatusPrint(int32_t status)
     }
     
     
    -void bist_TaskFxn(SemaphoreP_Handle bistSemHandle)
    +void bist_TaskFxn(void* a0, void* a1)
     {
         int32_t testResult = 0;
         int     i, j;
    @@ -153,7 +153,7 @@ void bist_TaskFxn(SemaphoreP_Handle bistSemHandle)
         uint64  time_lbist_start[NUM_BOOT_STAGES];
         uint64  time_pbist_start[NUM_BOOT_STAGES];
     #endif
    -
    +    SemaphoreP_Handle bistSemHandle = a0;
         /* Initialize boot stage status bitmaps to "not run/fail" */
         for (i = 0; i < NUM_BOOT_STAGES; i++)
         {
    diff --git a/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.h b/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.h
    index 6cc72080a..83e26d325 100755
    --- a/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.h
    +++ b/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.h
    @@ -73,6 +73,6 @@
     /*                           Macros & Typedefs                                */
     /* ========================================================================== */
     /* Function prototypes */
    -void bist_TaskFxn(void);
    +void bist_TaskFxn(void* a0, void* a1);
     
     #endif /* __BIST__ */
    

     but the bist still can not pass.

    2) I test the sdl bsit example img. 

         --->

    It can not pass too.

  • Hi,

    There were a few bugs in the SDK 8.6 with regards to the BIST example, which was fixed in the SDK 9.0. Could you try that?

    I will meanwhile try and reproduce this issue on 8.6 SDK as well.

    Regards,

    Josiitaa

  • Wow ~ bad news.

    Anyway, thank you very much。

    By the way, could you please provide a patch for bist(What are the changes in the code from SDK8.6 to 9.0 about BIST)?

  • Hi,

    I tried to reproduce the issue on SDK 8.6 and I see the code crash at test for A72. Main R5F 1 seems to pass.

    This is the patch with the changes in BIST between SDK 8.6 and 9.0 -

    0001-Changes-made-in-SDK-9.0.patch

    Using these changes, I am able to execute BIST example completely.

    Regards,

    Josiitaa

  • hello 

        Thank you Bro.

        You did me a big favor.

  • hello 

       I had git applay the patch .

       And excute the cmd :make bist_example PROFILE=release to get bist_example_app_r5f_baremetal_release.appimage.

       Then test the img on board.

       The log below,there seems something wrong in it.

    mcuClkFreq 1000000000
    
    BIST Example Application
    
     Starting PBIST failure insertion test on PBIST HWPOST MCU, index 0...
      Sciclient_pmSetModuleState 0xe59ff018 ...FAILED
    PBIST negative test failed for 0
    
     Starting PBIST test on PBIST HWPOST MCU, index 0...
      Sciclient_pmSetModuleState 0xe59ff018 ...FAILED
    PBIST functional test failed for 0
        HW POST MCU Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST DMSC Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST MCU Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST DMSC Status : SDL_LBIST_POST_COMPLETED_SUCCESS
    
     Starting PBIST failure insertion test on , index 2...
    customPrepareForPowerUpSequence - Invalid ProcId 53
      Custom core power restore sequence, ProcId 0x20304635 ...FAILED
    PBIST negative test failed for 2
    
     Starting PBIST test on , index 2...
    customPrepareForPowerUpSequence - Invalid ProcId 53
      Custom core power restore sequence, ProcId 0x20304635 ...FAILED
    PBIST functional test failed for 2
    
     *** Boot stage 0 is complete, cores for this stage may now be loaded ***
    
    
     Starting PBIST failure insertion test on , index 3...
       Primary core: Sciclient_procBootRequestProcessor, ProcId 0x52206e69...FAILED
    PBIST negative test failed for 3
    
     Starting PBIST test on , index 3...
       Primary core: Sciclient_procBootRequestProcessor, ProcId 0x52206e69...FAILED
    PBIST functional test failed for 3
    
     *** Boot stage 1 is complete, cores for this stage may now be loaded ***
    
    
     Starting PBIST failure insertion test on , index 5...
       Secondary core: Sciclient_procBootRequestProcessor, ProcId 0x37410000...FAILED
    PBIST negative test failed for 5
    
     Starting PBIST test on , index 5...
       Secondary core: Sciclient_procBootRequestProcessor, ProcId 0x37410000...FAILED
    PBIST functional test failed for 5
    
     *** Boot stage 2 is complete, cores for this stage may now be loaded ***
    
    ==========================
    BIST: Example App Summary:
    ==========================
    BIST: Pre-boot Stage - Ran negative PBIST ID - PBIST_HWPOST_MCU_INDEX, Result = FAIL or NOT RUN
    BIST: Pre-boot Stage - Ran negative PBIST ID - PBIST_INSTANCE_MAIN_INFRA, Result = FAIL or NOT RUN
    BIST: Pre-boot Stage - Ran negative PBIST ID - PBIST_INSTANCE_MSMC, Result = FAIL or NOT RUN
    Pre-boot stage - Ran 3 negative PBIST total sections
    BIST: Pre-boot Stage - Ran PBIST ID - PBIST_HWPOST_MCU_INDEX, Result = FAIL or NOT RUN
    BIST: Pre-boot Stage - Ran PBIST ID - PBIST_INSTANCE_MAIN_INFRA, Result = FAIL or NOT RUN
    BIST: Pre-boot Stage - Ran PBIST ID - PBIST_INSTANCE_MSMC, Result = FAIL or NOT RUN
    Pre-boot stage - Ran 3 PBIST total sections
    BIST: Pre-boot Stage - Ran LBIST ID - LBIST_HWPOST_DMSC_INDEX, Result = LBIST_POST_COMPLETED_SUCCESS
    BIST: Pre-boot Stage - Ran LBIST ID - LBIST_HWPOST_MCU_INDEX, Result = LBIST_POST_COMPLETED_SUCCESS
    Pre-boot stage - Ran 2 LBIST total sections
    BIST: Stage 0 - Ran negative PBIST ID - PBIST_INSTANCE_MAIN_PULSAR_0, Result = FAIL or NOT RUN
    BIST: Stage 0 - Ran 1 negative PBIST total sections
    BIST: Stage 0 - Ran PBIST ID - PBIST_INSTANCE_MAIN_PULSAR_0, Result = FAIL or NOT RUN
    BIST: Stage 0 - Ran 1 PBIST total sections
    BIST: Stage 0 - Ran LBIST ID - LBIST_MAIN_MCU0_INDEX, Result = PASS
    BIST: Stage 0 - Ran 1 LBIST sections
    BIST: Stage 1 - Ran negative PBIST ID - PBIST_INSTANCE_MAIN_PULSAR_1, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran negative PBIST ID - PBIST_INSTANCE_C7X, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran negative PBIST ID - PBIST_INSTANCE_C66X_0, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran negative PBIST ID - PBIST_INSTANCE_C66X_1, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran negative PBIST ID - PBIST_INSTANCE_VPAC, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran negative PBIST ID - PBIST_INSTANCE_DMPAC, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran 6 negative PBIST total sections
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_MAIN_PULSAR_1, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_C7X, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_C66X_0, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_C66X_1, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_VPAC, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran PBIST ID - PBIST_INSTANCE_DMPAC, Result = FAIL or NOT RUN
    BIST: Stage 1 - Ran 6 PBIST total sections
    BIST: Stage 1 - Ran LBIST ID - LBIST_MAIN_MCU1_INDEX, Result = PASS
    BIST: Stage 1 - Ran LBIST ID - LBIST_C7X_CORE_INDEX, Result = PASS
    BIST: Stage 1 - Ran LBIST ID - LBIST_VPAC_INDEX, Result = PASS
    BIST: Stage 1 - Ran LBIST ID - LBIST_DMPAC_INDEX, Result = PASS
    BIST: Stage 1 - Ran 4 LBIST sections
    BIST: Stage 2 - Ran negative PBIST ID - PBIST_INSTANCE_A72, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran negative PBIST ID - PBIST_INSTANCE_HC, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran negative PBIST ID - PBIST_INSTANCE_ENCODER, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran negative PBIST ID - PBIST_INSTANCE_DECODER, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran 4 negative PBIST total sections
    BIST: Stage 2 - Ran PBIST ID - PBIST_INSTANCE_A72, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran PBIST ID - PBIST_INSTANCE_HC, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran PBIST ID - PBIST_INSTANCE_ENCODER, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran PBIST ID - PBIST_INSTANCE_DECODER, Result = FAIL or NOT RUN
    BIST: Stage 2 - Ran 4 PBIST total sections
    BIST: Stage 2 - Ran LBIST ID - LBIST_A72_CORE_INDEX, Result = PASS
    BIST: Stage 2 - Ran 1 LBIST sections
    main.c:200:bist_example_app:PASS
    
    -----------------------
    1 Tests 0 Failures 0 Ignored
    OK

  • Hi,

    The BIST example requires multicore app image to be loaded on SDK 8.6. This image is genarated in the same folder as the binary is generated. The multi core app image binary file is named as bist_example_app_r5f_baremetal_multicore_image.appimage The reason for using the multicore app image (R5F and C7X binary) is to make sure MCU R5F is able to do CLEC configuration, as starting with SDK 8.6, MCU R5F boots in non-secure mode.

    Regards,

    Josiitaa

  • bad new ~

    The same results,.

    Hey bro do you have other idea

  • Hi, 

    It is working on my setup. Could you maybe share a patch with the changes you have made to the SDL base code and your binaries so I can test them on my setup?

    Regards,

    Josiitaa

  • 2728.file.zip

    Hi bro 

    In the additional file,there are bist.patch & bist_example_app_r5f_baremetal_multicore_image.appimage(program by make bist_example PROFILE=release)

    You can use the image to test bist on you board.

    Grinning

    Thank you very much.Sunglasses

  • I will test these on my setup and get back to you next week.

    Regards,

    Josiitaa 

  • Thank you.

    Next week is our National Day holiday,I will be on vacation tomorrow.

    So the response will not be very timely.Grinning

    Best Regards

    liupt

  • Yes understood. I will get back to you in a few days.

    Regards,

    Josiitaa 

  • Hi,

    I just went through your patch. You have not applied the changes in the pbist_utils.c and bist_core_defs.c files from that patch that I shared. Please apply all the changes from my patch. This should fix the issue.

    0001-Changes-made-in-SDK-9.0.patch

    Regards,

    Josiitaa

  • Hi bro

         You are right , I use git apply to the patch .

    There are two files not change is so weird.

    Then i use git am to patch,and test the image.

    All cases can passed.

        But the Bist test in he mcu1_0( psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.c ), I should change like the patch?

    You can also provide the patch?

  • Hi bro

    I change some code in the path( psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/) to test bist.

    But something wrong in the test.

    If i enable PBIST_INSTANCE_MSMC the log blow.

    Starting PBIST failure insertion test on PBIST HWPOST MCU, index 0...
    
     Starting PBIST test on PBIST HWPOST MCU, index 0...
      HW POST: Running test on HW POST, 1 Instances
        HW POST MCU Status : SDL_PBIST_POST_COMPLETED_SUCCESS
        HW POST MCU Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST DMSC Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST MCU Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST DMSC Status : SDL_LBIST_POST_COMPLETED_SUCCESS
    
     Starting PBIST failure insertion test on Main R5F 0 PBIST, index 2...
      Primary core: Main R5F0 core0: Requesting processor
      Secondary core: Main R5F0 core1: Requesting processor
      Main R5F0 core0: Primary core: Set module reset
      Main R5F0 core1: Secondary core: Set Module reset
      Primary core: Powering on Main R5F0 core0
      Secondary core: Powering on Main R5F0 core1
      Primary core: Double checking Powering on Main R5F0 core0
      Secondary core: Double checking Powering on Main R5F0 core0
      Powering on PBIST 317
      Powering off PBIST 317
      Secondary core: Powering off Main R5F0 core1
      Primary core: Powering off Main R5F0 core0
      Primary core: Taking out of local reset the core Main R5F0 core0
      Secondary core: Taking out of local reset the core Main R5F0 core1
      Main R5F0 core0: Primary core: Put in Software Reset Disable
      Main R5F0 core1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing Main R5F0 core0
      Secondary core: Releasing Main R5F0 core1
    
     Starting PBIST test on Main R5F 0 PBIST, index 2...
      Primary core: Main R5F0 core0: Requesting processor
      Secondary core: Main R5F0 core1: Requesting processor
      Main R5F0 core0: Primary core: Set module reset
      Main R5F0 core1: Secondary core: Set Module reset
      Primary core: Powering on Main R5F0 core0
      Secondary core: Powering on Main R5F0 core1
      Primary core: Double checking Powering on Main R5F0 core0
      Secondary core: Double checking Powering on Main R5F0 core0
      Powering on PBIST 317
      Powering off PBIST 317
      Secondary core: Powering off Main R5F0 core1
      Primary core: Powering off Main R5F0 core0
      Primary core: Taking out of local reset the core Main R5F0 core0
      Secondary core: Taking out of local reset the core Main R5F0 core1
      Main R5F0 core0: Primary core: Put in Software Reset Disable
      Main R5F0 core1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing Main R5F0 core0
      Secondary core: Releasing Main R5F0 core1
    Ran PBIST for Stage 0
    Ran LBIST for Stage 0
    
     Starting PBIST failure insertion test on Main R5F 1 PBIST, index 3...
      Primary core: Main R5F1 core0: Requesting processor
      Secondary core: Main R5F1 core1: Requesting processor
      Main R5F1 core0: Primary core: Set module reset
      Main R5F1 core1: Secondary core: Set Module reset
      Primary core: Powering on Main R5F1 core0
      Secondary core: Powering on Main R5F1 core1
      Primary core: Double checking Powering on Main R5F1 core0
      Secondary core: Double checking Powering on Main R5F1 core0
      Powering on PBIST 318
      Powering off PBIST 318
      Secondary core: Powering off Main R5F1 core1
      Primary core: Powering off Main R5F1 core0
      Primary core: Taking out of local reset the core Main R5F1 core0
      Secondary core: Taking out of local reset the core Main R5F1 core1
      Main R5F1 core0: Primary core: Put in Software Reset Disable
      Main R5F1 core1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing Main R5F1 core0
      Secondary core: Releasing Main R5F1 core1
    
     Data Abort exception falut_type:1 falut_addr:0x780c1000
    CSL_initGTC, freq is 200000000
    Starting Sciserver..... PASSED
      start I2C_Init !
      start Pmic_I2C_InstanceInit !
      setConfigI2C baseAddr=1108475904  !
    IIC : I2C_open    i2cHandle =1103942772!
      end Pmic_I2C_InstanceInit  i2c_instance=0   i2cHandle =1103942772!
    Main I2c BUS PMIC_INTF_SINGLE_I2C  with status
    Main I2c BUS PMIC_INTF_SINGLE_I2C  with status
     pmicb_ldo12_vmon_disable
    get 0x1D ldo1_ctrl: 0x31
    set 0x1D ldo1_ctrl: 0x21
    get 0x1E ldo2_ctrl: 0x31
    set 0x1E ldo2_ctrl: 0x21
    SPI cbMode
    SPI Interrupt NO DMA mode!
    The interrupt path has been set with interrupt number 21
    SPI Slave Mode
    clk0Seed: 22857, clk1Seed: 40, clk0ValidSeed: 2406
    : Init: inst 13, clk0Freq 19200000, clk1Freq 32000, clk0Src 0, clk1Src 6
    : DCC selftest OK!
    clk0Seed: 22857, clk1Seed: 40, clk0ValidSeed: 2406
    : Init: inst 13, clk0Freq 19200000, clk1Freq 32000, clk0Src 0, clk1Src 6
    clk0Seed: 95, clk1Seed: 868, clk0ValidSeed: 10
    : Init: inst 14, clk0Freq 19200000, clk1Freq 166666666, clk0Src 0, clk1Src 4
    clk0Seed: 115, clk1Seed: 79, clk0ValidSeed: 12
    : Init: inst 15, clk0Freq 19200000, clk1Freq 12500000, clk0Src 0, clk1Src 7
    clk0Seed: 95, clk1Seed: 153, clk0ValidSeed: 10
    : Init: inst 0, clk0Freq 12500000, clk1Freq 19200000, clk0Src 5, clk1Src 5
    clk0Seed: 95, clk1Seed: 2000, clk0ValidSeed: 10
    : Init: inst 1, clk0Freq 12500000, clk1Freq 250000000, clk0Src 5, clk1Src 2
    clk0Seed: 95, clk1Seed: 1800, clk0ValidSeed: 10
    : Init: inst 2, clk0Freq 12500000, clk1Freq 225000000, clk0Src 5, clk1Src 3
    clk0Seed: 95, clk1Seed: 1500, clk0ValidSeed: 10
    : Init: inst 3, clk0Freq 12500000, clk1Freq 187500000, clk0Src 5, clk1Src 6
    clk0Seed: 95, clk1Seed: 2133, clk0ValidSeed: 10
    : Init: inst 4, clk0Freq 12500000, clk1Freq 266625000, clk0Src 5, clk1Src 3
    clk0Seed: 95, clk1Seed: 4160, clk0ValidSeed: 10
    : Init: inst 5, clk0Freq 12500000, clk1Freq 520000000, clk0Src 5, clk1Src 4
    clk0Seed: 95, clk1Seed: 1600, clk0ValidSeed: 10
    : Init: inst 8, clk0Freq 12500000, clk1Freq 200000000, clk0Src 5, clk1Src 8
    clk0Seed: 95, clk1Seed: 800, clk0ValidSeed: 10
    : Init: inst 9, clk0Freq 12500000, clk1Freq 100000000, clk0Src 5, clk1Src 2
    clk0Seed: 95, clk1Seed: 1536, clk0ValidSeed: 10
    : Init: inst 10, clk0Freq 12500000, clk1Freq 192000000, clk0Src 5, clk1Src 6
    FS Adc SelfTest OK
    : FS_GtcSelftest OK!
    
     FS_RAMTst_Init memTypeIndex[12] NG
    
     FS_RAMTst_Init memTypeIndex[13] NG
    
     FS_RAMTst_Init memTypeIndex[14] NG
    ADC_APP: Variant - Post Build being used !!!
    ADC_Func: ADC Setup - DONE !!!
    s2m FLAG[0x10000000] m2s FLAG[0x00000000].
    
    
     SDL_ECC_injectError memTypeIndex[12] error!
    
     SDL_ECC_injectError memTypeIndex[12] error!
    
     SDL_ECC_injectError memTypeIndex[13] error!
    
     SDL_ECC_injectError memTypeIndex[13] error!
    
     SDL_ECC_injectError memTypeIndex[14] error!
    
     SDL_ECC_injectError memTypeIndex[14] error!
    after s2m FLAG[0x10000000] m2s FLAG[0x00000000].
    
    [MCU2SOC W] CRC[0x0C1E5C14] 0xBC  0xBD  0xBE  0xBF  0xC0  0xC1  0xC2  0xC3 ...
    
    ADC_APP: Sample Application - STARTS !!!
    
     Starting PBIST failure insertion test on PBIST HWPOST MCU, index 0...
    
     Starting PBIST failure insertion test on Main Infra PBIST, index 12...
      Powering on Device number 0 Device Id 130
      Powering on Device number 1 Device Id 9c
      Powering on Device number 2 Device Id 9e
      Powering on Device number 3 Device Id a0
      Powering on Device number 4 Device Id a1
      Powering on Device number 5 Device Id a2
      Powering on Device number 6 Device Id a3
      Powering on Device number 7 Device Id a4
      Powering on Device number 8 Device Id a5
      Powering on Device number 9 Device Id a6
      Powering on Device number 10 Device Id a7
      Powering on Device number 11 Device Id a8
      Powering on Device number 12 Device Id a9
      Powering on Device number 13 Device Id aa
      Powering on Device number 14 Device Id ab
      Powering on Device number 15 Device Id 74
      Powering on Device number 16 Device Id 108
      Powering on Device number 17 Device Id 13
      Double checking Powering on Device number 0 Device Id 130
      Double checking Powering on Device number 1 Device Id 9c
      Double checking Powering on Device number 2 Device Id 9e
      Double checking Powering on Device number 3 Device Id a0
      Double checking Powering on Device number 4 Device Id a1
      Double checking Powering on Device number 5 Device Id a2
      Double checking Powering on Device number 6 Device Id a3
      Double checking Powering on Device number 7 Device Id a4
      Double checking Powering on Device number 8 Device Id a5
      Double checking Powering on Device number 9 Device Id a6
      Double checking Powering on Device number 10 Device Id a7
      Double checking Powering on Device number 11 Device Id a8
      Double checking Powering on Device number 12 Device Id a9
      Double checking Powering on Device number 13 Device Id aa
      Double checking Powering on Device number 14 Device Id ab
      Double checking Powering on Device number 15 Device Id 74
      Double checking Powering on Device number 16 Device Id 108
      Double checking Powering on Device number 17 Device Id 13
      Powering on PBIST 315
      Powering off PBIST 315
      Powering off Device number 0 Device Id 130
      Powering off Device number 1 Device Id 9c
      Powering off Device number 2 Device Id 9e
      Powering off Device number 3 Device Id a0
      Powering off Device number 4 Device Id a1
      Powering off Device number 5 Device Id a2
      Powering off Device number 6 Device Id a3
      Powering off Device number 7 Device Id a4
      Powering off Device number 8 Device Id a5
      Powering off Device number 9 Device Id a6
      Powering off Device number 10 Device Id a7
      Powering off Device number 11 Device Id a8
      Powering off Device number 12 Device Id a9
      Powering off Device number 13 Device Id aa
      Powering off Device number 14 Device Id ab
      Powering off Device number 15 Device Id 74
      Powering off Device number 16 Device Id 108
      Powering off Device number 17 Device Id 13
    
     Starting PBIST failure insertion test on MSMC PBIST, index 13...
      Primary core: A72 core 0: Requesting processor
      Secondary core: A72 core 1: Requesting processor
      A72 core 0: Primary core: Set module reset
      A72 core 1: Secondary core: Set Module reset
      Powering on Device number 0 Device Id d
      Powering on Device number 1 Device Id c7
      Powering on Device number 2 Device Id 4
      Primary core: Powering on A72 core 0
      Secondary core: Powering on A72 core 1
      Double checking Powering on Device number 0 Device Id d
      Double checking Powering on Device number 1 Device Id c7
      Double checking Powering on Device number 2 Device Id 4
      Primary core: Double checking Powering on A72 core 0
      Secondary core: Double checking Powering on A72 core 0
      Powering on PBIST 17
      Powering off PBIST 17
      Secondary core: Powering off A72 core 1
      Primary core: Powering off A72 core 0
      Powering off Device number 0 Device Id d
      Powering off Device number 1 Device Id c7
      Powering off Device number 2 Device Id 4
      Primary core: Taking out of local reset the core A72 core 0
      Secondary core: Taking out of local reset the core A72 core 1
      A72 core 0: Primary core: Put in Software Reset Disable
      A72 core 1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing A72 core 0
      Secondary core: Releasing A72 core 1
    
     Starting PBIST test on PBIST HWPOST MCU, index 0...
      HW POST: Running test on HW POST, 1 Instances
        HW POST MCU Status : SDL_PBIST_POST_COMPLETED_SUCCESS
    
     Starting PBIST test on Main Infra PBIST, index 12...
    ipc_shm_task_app running... shm_s2m->flag [0x10000000] shm_m2s->flag [0x00000002]
    
      Powering on Device number 0 Device Id 130
      Powering on Device number 1 Device Id 9c
      Powering on Device number 2 Device Id 9e
      Powering on Device number 3 Device Id a0
      Powering on Device number 4 Device Id a1
      Powering on Device number 5 Device Id a2
      Powering on Device number 6 Device Id a3
      Powering on Device number 7 Device Id a4
      Powering on Device number 8 Device Id a5
      Powering on Device number 9 Device Id a6
      Powering on Device number 10 Device Id a7
      Powering on Device number 11 Device Id a8
      Powering on Device number 12 Device Id a9
      Powering on Device number 13 Device Id aa
      Powering on Device number 14 Device Id ab
      Powering on Device number 15 Device Id 74
      Powering on Device number 16 Device Id 108
      Powering on Device number 17 Device Id 13
      Double checking Powering on Device number 0 Device Id 130
      Double checking Powering on Device number 1 Device Id 9c
      Double checking Powering on Device number 2 Device Id 9e
      Double checking Powering on Device number 3 Device Id a0
      Double checking Powering on Device number 4 Device Id a1
      Double checking Powering on Device number 5 Device Id a2
      Double checking Powering on Device number 6 Device Id a3
      Double checking Powering on Device number 7 Device Id a4
      Double checking Powering on Device number 8 Device Id a5
      Double checking Powering on Device number 9 Device Id a6
      Double checking Powering on Device number 10 Device Id a7
      Double checking Powering on Device number 11 Device Id a8
      Double checking Powering on Device number 12 Device Id a9
      Double checking Powering on Device number 13 Device Id aa
      Double checking Powering on Device number 14 Device Id ab
      Double checking Powering on Device number 15 Device Id 74
      Double checking Powering on Device number 16 Device Id 108
      Double checking Powering on Device number 17 Device Id 13
      Powering on PBIST 315
      Powering off PBIST 315
      Powering off Device number 0 Device Id 130
      Powering off Device number 1 Device Id 9c
      Powering off Device number 2 Device Id 9e
      Powering off Device number 3 Device Id a0
      Powering off Device number 4 Device Id a1
      Powering off Device number 5 Device Id a2
      Powering off Device number 6 Device Id a3
      Powering off Device number 7 Device Id a4
      Powering off Device number 8 Device Id a5
      Powering off Device number 9 Device Id a6
      Powering off Device number 10 Device Id a7
      Powering off Device number 11 Device Id a8
      Powering off Device number 12 Device Id a9
      Powering off Device number 13 Device Id aa
      Powering off Device number 14 Device Id ab
      Powering off Device number 15 Device Id 74
      Powering off Device number 16 Device Id 108
      Powering off Device number 17 Device Id 13
    
     Starting PBIST test on MSMC PBIST, index 13...
      Primary core: A72 core 0: Requesting processor
      Secondary core: A72 core 1: Requesting processor
      A72 core 0: Primary core: Set module reset
      A72 core 1: Secondary core: Set Module reset
      Powering on Device number 0 Device Id d
      Powering on Device number 1 Device Id c7
      Powering on Device number 2 Device Id 4
      Primary core: Powering on A72 core 0
      Secondary core: Powering on A72 core 1
      Double checking Powering on Device number 0 Device Id d
      Double checking Powering on Device number 1 Device Id c7
      Double checking Powering on Device number 2 Device Id 4
      Primary core: Double checking Powering on A72 core 0
      Secondary core: Double checking Powering on A72 core 0
      Powering on PBIST 17
    
    
    

    If I disable PBIST_INSTANCE_MSMC  the log blow.

     Starting PBIST failure insertion test on PBIST HWPOST MCU, index 0...
    
     Starting PBIST failure insertion test on Main Infra PBIST, index 12...
      Powering on Device number 0 Device Id 130
      Powering on Device number 1 Device Id 9c
      Powering on Device number 2 Device Id 9e
      Powering on Device number 3 Device Id a0
      Powering on Device number 4 Device Id a1
      Powering on Device number 5 Device Id a2
      Powering on Device number 6 Device Id a3
      Powering on Device number 7 Device Id a4
      Powering on Device number 8 Device Id a5
      Powering on Device number 9 Device Id a6
      Powering on Device number 10 Device Id a7
      Powering on Device number 11 Device Id a8
      Powering on Device number 12 Device Id a9
      Powering on Device number 13 Device Id aa
      Powering on Device number 14 Device Id ab
      Powering on Device number 15 Device Id 74
      Powering on Device number 16 Device Id 108
      Powering on Device number 17 Device Id 13
      Double checking Powering on Device number 0 Device Id 130
      Double checking Powering on Device number 1 Device Id 9c
      Double checking Powering on Device number 2 Device Id 9e
      Double checking Powering on Device number 3 Device Id a0
      Double checking Powering on Device number 4 Device Id a1
      Double checking Powering on Device number 5 Device Id a2
      Double checking Powering on Device number 6 Device Id a3
      Double checking Powering on Device number 7 Device Id a4
      Double checking Powering on Device number 8 Device Id a5
      Double checking Powering on Device number 9 Device Id a6
      Double checking Powering on Device number 10 Device Id a7
      Double checking Powering on Device number 11 Device Id a8
      Double checking Powering on Device number 12 Device Id a9
      Double checking Powering on Device number 13 Device Id aa
      Double checking Powering on Device number 14 Device Id ab
      Double checking Powering on Device number 15 Device Id 74
      Double checking Powering on Device number 16 Device Id 108
      Double checking Powering on Device number 17 Device Id 13
      Powering on PBIST 315
      Powering off PBIST 315
      Powering off Device number 0 Device Id 130
      Powering off Device number 1 Device Id 9c
      Powering off Device number 2 Device Id 9e
      Powering off Device number 3 Device Id a0
      Powering off Device number 4 Device Id a1
      Powering off Device number 5 Device Id a2
      Powering off Device number 6 Device Id a3
      Powering off Device number 7 Device Id a4
      Powering off Device number 8 Device Id a5
      Powering off Device number 9 Device Id a6
      Powering off Device number 10 Device Id a7
      Powering off Device number 11 Device Id a8
      Powering off Device number 12 Device Id a9
      Powering off Device number 13 Device Id aa
      Powering off Device number 14 Device Id ab
      Powering off Device number 15 Device Id 74
      Powering off Device number 16 Device Id 108
      Powering off Device number 17 Device Id 13
    
     Starting PBIST failure insertion test on MSMC PBIST, index 13...
      Primary core: A72 core 0: Requesting processor
      Secondary core: A72 core 1: Requesting processor
      A72 core 0: Primary core: Set module reset
      A72 core 1: Secondary core: Set Module reset
      Powering on Device number 0 Device Id d
      Powering on Device number 1 Device Id c7
      Powering on Device number 2 Device Id 4
      Primary core: Powering on A72 core 0
      Secondary core: Powering on A72 core 1
      Double checking Powering on Device number 0 Device Id d
      Double checking Powering on Device number 1 Device Id c7
      Double checking Powering on Device number 2 Device Id 4
      Primary core: Double checking Powering on A72 core 0
      Secondary core: Double checking Powering on A72 core 0
      Powering on PBIST 17
      Powering off PBIST 17
      Secondary core: Powering off A72 core 1
      Primary core: Powering off A72 core 0
      Powering off Device number 0 Device Id d
      Powering off Device number 1 Device Id c7
      Powering off Device number 2 Device Id 4
      Primary core: Taking out of local reset the core A72 core 0
      Secondary core: Taking out of local reset the core A72 core 1
      A72 core 0: Primary core: Put in Software Reset Disable
      A72 core 1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing A72 core 0
      Secondary core: Releasing A72 core 1
    
     Starting PBIST test on PBIST HWPOST MCU, index 0...
      HW POST: Running test on HW POST, 1 Instances
        HW POST MCU Status : SDL_PBIST_POST_COMPLETED_SUCCESS
    
     Starting PBIST test on Main Infra PBIST, index 12...
    ipc_shm_task_app running... shm_s2m->flag [0x10000000] shm_m2s->flag [0x00000002]
    
      Powering on Device number 0 Device Id 130
      Powering on Device number 1 Device Id 9c
      Powering on Device number 2 Device Id 9e
      Powering on Device number 3 Device Id a0
      Powering on Device number 4 Device Id a1
      Powering on Device number 5 Device Id a2
      Powering on Device number 6 Device Id a3
      Powering on Device number 7 Device Id a4
      Powering on Device number 8 Device Id a5
      Powering on Device number 9 Device Id a6
      Powering on Device number 10 Device Id a7
      Powering on Device number 11 Device Id a8
      Powering on Device number 12 Device Id a9
      Powering on Device number 13 Device Id aa
      Powering on Device number 14 Device Id ab
      Powering on Device number 15 Device Id 74
      Powering on Device number 16 Device Id 108
      Powering on Device number 17 Device Id 13
      Double checking Powering on Device number 0 Device Id 130
      Double checking Powering on Device number 1 Device Id 9c
      Double checking Powering on Device number 2 Device Id 9e
      Double checking Powering on Device number 3 Device Id a0
      Double checking Powering on Device number 4 Device Id a1
      Double checking Powering on Device number 5 Device Id a2
      Double checking Powering on Device number 6 Device Id a3
      Double checking Powering on Device number 7 Device Id a4
      Double checking Powering on Device number 8 Device Id a5
      Double checking Powering on Device number 9 Device Id a6
      Double checking Powering on Device number 10 Device Id a7
      Double checking Powering on Device number 11 Device Id a8
      Double checking Powering on Device number 12 Device Id a9
      Double checking Powering on Device number 13 Device Id aa
      Double checking Powering on Device number 14 Device Id ab
      Double checking Powering on Device number 15 Device Id 74
      Double checking Powering on Device number 16 Device Id 108
      Double checking Powering on Device number 17 Device Id 13
      Powering on PBIST 315
      Powering off PBIST 315
      Powering off Device number 0 Device Id 130
      Powering off Device number 1 Device Id 9c
      Powering off Device number 2 Device Id 9e
      Powering off Device number 3 Device Id a0
      Powering off Device number 4 Device Id a1
      Powering off Device number 5 Device Id a2
      Powering off Device number 6 Device Id a3
      Powering off Device number 7 Device Id a4
      Powering off Device number 8 Device Id a5
      Powering off Device number 9 Device Id a6
      Powering off Device number 10 Device Id a7
      Powering off Device number 11 Device Id a8
      Powering off Device number 12 Device Id a9
      Powering off Device number 13 Device Id aa
      Powering off Device number 14 Device Id ab
      Powering off Device number 15 Device Id 74
      Powering off Device number 16 Device Id 108
      Powering off Device number 17 Device Id 13
    
     Starting PBIST test on MSMC PBIST, index 13...
      Primary core: A72 core 0: Requesting processor
      Secondary core: A72 core 1: Requesting processor
      A72 core 0: Primary core: Set module reset
      A72 core 1: Secondary core: Set Module reset
      Powering on Device number 0 Device Id d
      Powering on Device number 1 Device Id c7
      Powering on Device number 2 Device Id 4
      Primary core: Powering on A72 core 0
      Secondary core: Powering on A72 core 1
      Double checking Powering on Device number 0 Device Id d
      Double checking Powering on Device number 1 Device Id c7
      Double checking Powering on Device number 2 Device Id 4
      Primary core: Double checking Powering on A72 core 0
      Secondary core: Double checking Powering on A72 core 0
      Powering on PBIST 17
    Starting Sciserver..... PASSED
      start I2C_Init !
      start Pmic_I2C_InstanceInit !
      setConfigI2C baseAddr=1108475904  !
    IIC : I2C_open    i2cHandle =1103942772!
      end Pmic_I2C_InstanceInit  i2c_instance=0   i2cHandle =1103942772!
    Main I2c BUS PMIC_INTF_SINGLE_I2C  with status
    Main I2c BUS PMIC_INTF_SINGLE_I2C  with status
     pmicb_ldo12_vmon_disable
    get 0x1D ldo1_ctrl: 0x31
    set 0x1D ldo1_ctrl: 0x21
    get 0x1E ldo2_ctrl: 0x31
    set 0x1E ldo2_ctrl: 0x21
    SPI cbMode
    SPI Interrupt NO DMA mode!
    The interrupt path has been set with interrupt number 21
    SPI Slave Mode
    clk0Seed: 22857, clk1Seed: 40, clk0ValidSeed: 2406
    : Init: inst 13, clk0Freq 19200000, clk1Freq 32000, clk0Src 0, clk1Src 6
    : DCC selftest OK!
    clk0Seed: 22857, clk1Seed: 40, clk0ValidSeed: 2406
    : Init: inst 13, clk0Freq 19200000, clk1Freq 32000, clk0Src 0, clk1Src 6
    clk0Seed: 95, clk1Seed: 868, clk0ValidSeed: 10
    : Init: inst 14, clk0Freq 19200000, clk1Freq 166666666, clk0Src 0, clk1Src 4
    clk0Seed: 115, clk1Seed: 79, clk0ValidSeed: 12
    : Init: inst 15, clk0Freq 19200000, clk1Freq 12500000, clk0Src 0, clk1Src 7
    clk0Seed: 95, clk1Seed: 153, clk0ValidSeed: 10
    : Init: inst 0, clk0Freq 12500000, clk1Freq 19200000, clk0Src 5, clk1Src 5
    clk0Seed: 95, clk1Seed: 2000, clk0ValidSeed: 10
    : Init: inst 1, clk0Freq 12500000, clk1Freq 250000000, clk0Src 5, clk1Src 2
    clk0Seed: 95, clk1Seed: 1800, clk0ValidSeed: 10
    : Init: inst 2, clk0Freq 12500000, clk1Freq 225000000, clk0Src 5, clk1Src 3
    clk0Seed: 95, clk1Seed: 1500, clk0ValidSeed: 10
    : Init: inst 3, clk0Freq 12500000, clk1Freq 187500000, clk0Src 5, clk1Src 6
    clk0Seed: 95, clk1Seed: 2133, clk0ValidSeed: 10
    : Init: inst 4, clk0Freq 12500000, clk1Freq 266625000, clk0Src 5, clk1Src 3
    clk0Seed: 95, clk1Seed: 4160, clk0ValidSeed: 10
    : Init: inst 5, clk0Freq 12500000, clk1Freq 520000000, clk0Src 5, clk1Src 4
    clk0Seed: 95, clk1Seed: 1600, clk0ValidSeed: 10
    : Init: inst 8, clk0Freq 12500000, clk1Freq 200000000, clk0Src 5, clk1Src 8
    clk0Seed: 95, clk1Seed: 800, clk0ValidSeed: 10
    : Init: inst 9, clk0Freq 12500000, clk1Freq 100000000, clk0Src 5, clk1Src 2
    clk0Seed: 95, clk1Seed: 1536, clk0ValidSeed: 10
    : Init: inst 10, clk0Freq 12500000, clk1Freq 192000000, clk0Src 5, clk1Src 6
    FS Adc SelfTest OK
    : FS_GtcSelftest OK!
    
     FS_RAMTst_Init memTypeIndex[12] NG
    
     FS_RAMTst_Init memTypeIndex[13] NG
    
     FS_RAMTst_Init memTypeIndex[14] NG
    ADC_APP: Variant - Post Build being used !!!
    ADC_Func: ADC Setup - DONE !!!
    s2m FLAG[0x10000000] m2s FLAG[0x00000000].
    
    
     SDL_ECC_injectError memTypeIndex[12] error!
    
     SDL_ECC_injectError memTypeIndex[12] error!
    
     SDL_ECC_injectError memTypeIndex[13] error!
    
     SDL_ECC_injectError memTypeIndex[13] error!
    
     SDL_ECC_injectError memTypeIndex[14] error!
    
     SDL_ECC_injectError memTypeIndex[14] error!
    after s2m FLAG[0x10000000] m2s FLAG[0x00000000].
    
    [MCU2SOC W] CRC[0x68427225] 0xCA  0xCB  0xCC  0xCD  0xCE  0xCF  0xD0  0xD1 ...
    
    ADC_APP: Sample Application - STARTS !!!
    
     Starting PBIST failure insertion test on PBIST HWPOST MCU, index 0...
    
     Starting PBIST failure insertion test on Main Infra PBIST, index 12...
      Powering on Device number 0 Device Id 130
      Powering on Device number 1 Device Id 9c
      Powering on Device number 2 Device Id 9e
      Powering on Device number 3 Device Id a0
      Powering on Device number 4 Device Id a1
      Powering on Device number 5 Device Id a2
      Powering on Device number 6 Device Id a3
      Powering on Device number 7 Device Id a4
      Powering on Device number 8 Device Id a5
      Powering on Device number 9 Device Id a6
      Powering on Device number 10 Device Id a7
      Powering on Device number 11 Device Id a8
      Powering on Device number 12 Device Id a9
      Powering on Device number 13 Device Id aa
      Powering on Device number 14 Device Id ab
      Powering on Device number 15 Device Id 74
      Powering on Device number 16 Device Id 108
      Powering on Device number 17 Device Id 13
      Double checking Powering on Device number 0 Device Id 130
      Double checking Powering on Device number 1 Device Id 9c
      Double checking Powering on Device number 2 Device Id 9e
      Double checking Powering on Device number 3 Device Id a0
      Double checking Powering on Device number 4 Device Id a1
      Double checking Powering on Device number 5 Device Id a2
      Double checking Powering on Device number 6 Device Id a3
      Double checking Powering on Device number 7 Device Id a4
      Double checking Powering on Device number 8 Device Id a5
      Double checking Powering on Device number 9 Device Id a6
      Double checking Powering on Device number 10 Device Id a7
      Double checking Powering on Device number 11 Device Id a8
      Double checking Powering on Device number 12 Device Id a9
      Double checking Powering on Device number 13 Device Id aa
      Double checking Powering on Device number 14 Device Id ab
      Double checking Powering on Device number 15 Device Id 74
      Double checking Powering on Device number 16 Device Id 108
      Double checking Powering on Device number 17 Device Id 13
      Powering on PBIST 315
      Powering off PBIST 315
      Powering off Device number 0 Device Id 130
      Powering off Device number 1 Device Id 9c
      Powering off Device number 2 Device Id 9e
      Powering off Device number 3 Device Id a0
      Powering off Device number 4 Device Id a1
      Powering off Device number 5 Device Id a2
      Powering off Device number 6 Device Id a3
      Powering off Device number 7 Device Id a4
      Powering off Device number 8 Device Id a5
      Powering off Device number 9 Device Id a6
      Powering off Device number 10 Device Id a7
      Powering off Device number 11 Device Id a8
      Powering off Device number 12 Device Id a9
      Powering off Device number 13 Device Id aa
      Powering off Device number 14 Device Id ab
      Powering off Device number 15 Device Id 74
      Powering off Device number 16 Device Id 108
      Powering off Device number 17 Device Id 13
    
     Starting PBIST test on PBIST HWPOST MCU, index 0...
      HW POST: Running test on HW POST, 1 Instances
        HW POST MCU Status : SDL_PBIST_POST_COMPLETED_SUCCESS
    
     Starting PBIST test on Main Infra PBIST, index 12...
      Powering on Device number 0 Device Id 130
      Powering on Device number 1 Device Id 9c
      Powering on Device number 2 Device Id 9e
      Powering on Device number 3 Device Id a0
      Powering on Device number 4 Device Id a1
      Powering on Device number 5 Device Id a2
      Powering on Device number 6 Device Id a3
      Powering on Device number 7 Device Id a4
      Powering on Device number 8 Device Id a5
      Powering on Device number 9 Device Id a6
      Powering on Device number 10 Device Id a7
      Powering on Device number 11 Device Id a8
      Powering on Device number 12 Device Id a9
      Powering on Device number 13 Device Id aa
      Powering on Device number 14 Device Id ab
      Powering on Device number 15 Device Id 74
      Powering on Device number 16 Device Id 108
      Powering on Device number 17 Device Id 13
      Double checking Powering on Device number 0 Device Id 130
      Double checking Powering on Device number 1 Device Id 9c
      Double checking Powering on Device number 2 Device Id 9e
      Double checking Powering on Device number 3 Device Id a0
      Double checking Powering on Device number 4 Device Id a1
      Double checking Powering on Device number 5 Device Id a2
      Double checking Powering on Device number 6 Device Id a3
      Double checking Powering on Device number 7 Device Id a4
      Double checking Powering on Device number 8 Device Id a5
    ipc_shm_task_app running... shm_s2m->flag [0x10000000] shm_m2s->flag [0x00000002]
    
      Double checking Powering on Device number 9 Device Id a6
      Double checking Powering on Device number 10 Device Id a7
      Double checking Powering on Device number 11 Device Id a8
      Double checking Powering on Device number 12 Device Id a9
      Double checking Powering on Device number 13 Device Id aa
      Double checking Powering on Device number 14 Device Id ab
      Double checking Powering on Device number 15 Device Id 74
      Double checking Powering on Device number 16 Device Id 108
      Double checking Powering on Device number 17 Device Id 13
      Powering on PBIST 315
      Powering off PBIST 315
      Powering off Device number 0 Device Id 130
      Powering off Device number 1 Device Id 9c
      Powering off Device number 2 Device Id 9e
      Powering off Device number 3 Device Id a0
      Powering off Device number 4 Device Id a1
      Powering off Device number 5 Device Id a2
      Powering off Device number 6 Device Id a3
      Powering off Device number 7 Device Id a4
      Powering off Device number 8 Device Id a5
      Powering off Device number 9 Device Id a6
      Powering off Device number 10 Device Id a7
      Powering off Device number 11 Device Id a8
      Powering off Device number 12 Device Id a9
      Powering off Device number 13 Device Id aa
      Powering off Device number 14 Device Id ab
      Powering off Device number 15 Device Id 74
      Powering off Device number 16 Device Id 108
      Powering off Device number 17 Device Id 13
        HW POST MCU Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST DMSC Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST MCU Status : SDL_LBIST_POST_COMPLETED_SUCCESS
        HW POST DMSC Status : SDL_LBIST_POST_COMPLETED_SUCCESS
    
     Starting PBIST failure insertion test on Main R5F 0 PBIST, index 2...
      Primary core: Main R5F0 core0: Requesting processor
      Secondary core: Main R5F0 core1: Requesting processor
      Main R5F0 core0: Primary core: Set module reset
      Main R5F0 core1: Secondary core: Set Module reset
      Primary core: Powering on Main R5F0 core0
      Secondary core: Powering on Main R5F0 core1
      Primary core: Double checking Powering on Main R5F0 core0
      Secondary core: Double checking Powering on Main R5F0 core0
      Powering on PBIST 317
      Powering off PBIST 317
      Secondary core: Powering off Main R5F0 core1
      Primary core: Powering off Main R5F0 core0
      Primary core: Taking out of local reset the core Main R5F0 core0
      Secondary core: Taking out of local reset the core Main R5F0 core1
      Main R5F0 core0: Primary core: Put in Software Reset Disable
      Main R5F0 core1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing Main R5F0 core0
      Secondary core: Releasing Main R5F0 core1
    
     Starting PBIST test on Main R5F 0 PBIST, index 2...
      Primary core: Main R5F0 core0: Requesting processor
      Secondary core: Main R5F0 core1: Requesting processor
      Main R5F0 core0: Primary core: Set module reset
      Main R5F0 core1: Secondary core: Set Module reset
      Primary core: Powering on Main R5F0 core0
      Secondary core: Powering on Main R5F0 core1
      Primary core: Double checking Powering on Main R5F0 core0
      Secondary core: Double checking Powering on Main R5F0 core0
      Powering on PBIST 317
      Powering off PBIST 317
      Secondary core: Powering off Main R5F0 core1
      Primary core: Powering off Main R5F0 core0
      Primary core: Taking out of local reset the core Main R5F0 core0
      Secondary core: Taking out of local reset the core Main R5F0 core1
      Main R5F0 core0: Primary core: Put in Software Reset Disable
      Main R5F0 core1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing Main R5F0 core0
      Secondary core: Releasing Main R5F0 core1
    Ran PBIST for Stage 0
    Ran LBIST for Stage 0
    
     Starting PBIST failure insertion test on Main R5F 1 PBIST, index 3...
      Primary core: Main R5F1 core0: Requesting processor
      Secondary core: Main R5F1 core1: Requesting processor
      Main R5F1 core0: Primary core: Set module reset
      Main R5F1 core1: Secondary core: Set Module reset
      Primary core: Powering on Main R5F1 core0
      Secondary core: Powering on Main R5F1 core1
      Primary core: Double checking Powering on Main R5F1 core0
      Secondary core: Double checking Powering on Main R5F1 core0
      Powering on PBIST 318
      Powering off PBIST 318
      Secondary core: Powering off Main R5F1 core1
      Primary core: Powering off Main R5F1 core0
      Primary core: Taking out of local reset the core Main R5F1 core0
      Secondary core: Taking out of local reset the core Main R5F1 core1
      Main R5F1 core0: Primary core: Put in Software Reset Disable
      Main R5F1 core1: Secondary Core Put in Software Reset Disable
      Primary core: Releasing Main R5F1 core0
      Secondary core: Releasing Main R5F1 core1
    
     Data Abort exception falut_type:1 falut_addr:0x780c1000
    
    boot_app_mcu_rtos.zip

    The attachment contains all relevant code files.

  • Hi,

    What is the error that you are seeing when you enable MSMC exactly? Is it with respect to the SDL APIs or is it part of the boot app?

    Regards,

    Josiitaa

  • Hi,

    You provided me with a BIST modification solution for SDL, so I made changes to the code of the boot app (using SDL API). If I enable the MSMC BIST test, the boot app will stop running and will not continue.

    The last log:

    Starting PBIST test on MSMC PBIST, index 13...
    Primary core: A72 core 0: Requesting processor
    Secondary core: A72 core 1: Requesting processor
    A72 core 0: Primary core: Set module reset
    A72 core 1: Secondary core: Set Module reset
    Powering on Device number 0 Device Id d
    Powering on Device number 1 Device Id c7
    Powering on Device number 2 Device Id 4
    Primary core: Powering on A72 core 0
    Secondary core: Powering on A72 core 1
    Double checking Powering on Device number 0 Device Id d
    Double checking Powering on Device number 1 Device Id c7
    Double checking Powering on Device number 2 Device Id 4
    Primary core: Double checking Powering on A72 core 0
    Secondary core: Double checking Powering on A72 core 0
    Powering on PBIST 17

    Even i disable MSMC ,the bist test will stop running too.

    the last log:

     Data Abort exception falut_type:1 falut_addr:0x780c1000

    The seams like about MPU 

  • HI

    The mcu1_0 mpu config file is---》/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/overrides/j721e/mcu1_0/r5_mpu_freertos.c?

  • Hi,

    Could you provide details on how you are loading the boot application? Is this the standard build from the SDK 8.6 release? I am seeing a lot of code modifications in your source code with SPI and no boot files present.

    Data Abort exception falut_type:1 falut_addr:0x780c100

    This looks like you are trying to access this memory region from the MCU R5F. Could you provide details on why this memory is being accessed in your code?

    What is the ultimate goal here? Integration of BIST with the boot app? or is there any other customization that you are performing?

    Regards,

    Josiitaa

  • Hi,

    Due to the need for functional safety development, we have indeed made many modifications. Which specific files do you need to confirm? I will do my best to provide them.

    Can you try the BIST (Built-In Self-Test) in the native boot application of SDK 8.6? In the makefile located at psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/makefile, uncomment the line "BISTFUNC ?= enabled" and see if the test can pass.

    thank you

  • Hi,

    In the native code of/psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos/bist.c

       for (i = 0; i < NUM_BOOT_STAGES; i++)
        {
            pbist_stage_status[i] = 0x0;
            pbist_stage_neg_status[i] = 0x0;
            lbist_stage_status[i] = 0x0;
        }
    
        testResult = PBIST_commonInit();
    
        if (testResult != 0)
        {
            AppUtils_Printf(MSG_NORMAL,
                            "PBIST_commonInit ...FAILED \n");
        }
        else
        {
            time_pre_boot_stage_start = get_usec_timestamp();
    
            /* Run pre-boot-stage PBIST's.  The definitions of the pre-boot-stage PBIST's
             * are found in soc/<SOC Device>/bist_core_defs.c.*/
            for (i = 0; i < num_pbists_pre_boot; i++)
            {
            if(pbist_pre_boot_stage[i]==PBIST_INSTANCE_MAIN_INFRA){
            continue;}
                /* Run test on selected instance */
                testResult = PBIST_runTest(pbist_pre_boot_stage[i], true);
                /* Convert signed return value (with -1 = failure and 0 = pass) to become
                 * 0 = failure and 1 = pass */
                pbist_pre_boot_stage_neg_status[i] = testResult + 1;
                if ( testResult != 0)
                {
                    AppUtils_Printf(MSG_NORMAL,"PBIST negative test failed for %d\n",
                                    pbist_pre_boot_stage[i]);
                    break;
                }
            }
    

    if(pbist_pre_boot_stage[i]==PBIST_INSTANCE_MAIN_INFRA){
    continue;}  why PBIST_INSTANCE_MAIN_INFRA not test?

  • Hi,

    I understand your requirement for functional safety. We have currently not validated the MCUSW Boot Application with BIST enabled in the SDK 8.6. There is an internal marketing requirement raised to integrate BIST functionality with the Boot application, that you might see in the future releases. We understand that this is a critical issue and are working towards getting it functional as soon as possible.

    why PBIST_INSTANCE_MAIN_INFRA not test?

    The MAIN_INFRA modules has been tested as a part of the SDL standalone application, and can be included based on your custom requirement for testing.

    Thanks,

    Josiitaa

  • Hi,

    Thank you very much.

    I feel you.

    But in sdk 8.4 it was ok for enable BISTFUNC in MCUSW Boot Application and test bist ok (change the bist config file ).

    So could u please check the log to find something wrong ?

    There is no way to test bist in  MCUSW Boot Application?

  • Hi,

    Yes, the BISTFUNC was tested in 8.4 SDK. There were a few re configurations within various parts of the SDK, due to which we do not have MCUSW with BIST functional at the moment. We are working on getting that functional as soon as possible. Sorry for the inconvenience.

    Regards,

    Josiitaa

  • Hi,

    JoyThis is really bad news.

    Thank you for your support these days.

    Could u send mail when the BISTFUNC  is ok?

    Best Regards.

    liupt

  • Yes, I will keep you posted on the updates.

    Regards,

    Josiitaa