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.

DRA756: IVAHD refuse to boot

Part Number: DRA756

dear expert:

we found sometimes the system failed. the video cannot be observed in the screen.

after add A LOT of log in the system:

static void ivahd_boot(void)

//#ifdef SYSTEM_DEBUG_IVA_PRCM
Vps_printf(" IVA_PRCM: IVA_PRCM: Booting IVAHD...Start!!!");
//#endif

//....

i = 0;
while(((CM_IVAHD_CLKSTCTRL) & 0x100) & ~0x100 ) {
if((i % 10000) == 0)
{
Vps_printf(" IVA_PRCM:CM_IVAHD_CLKSTCTRL=0x%x\n", CM_IVAHD_CLKSTCTRL);
}
i++;
}

//#ifdef SYSTEM_DEBUG_IVA_PRCM
Vps_printf(" IVA_PRCM:Booting IVAHD...Done!!!");
//#endif

somethings especial observed in the log:

[2020/05/27_22:24:32|346] [HOST] [IPU1-0] 0.862990 s: IVA_PRCM: IVA_PRCM: Booting IVAHD...Start!!!

then no father infomaction observed relate to IPU1-0, but the other cores are ok with log coming out.

after failed to connect the device IPU1_C0 with the jtag xds560, the error message observed as follow:

Cortex_M4_IPU1_C0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.1.0.00001)

and so did the IVA-HD:

ARM9_ICONT1: Error connecting to the target: (Error -2062 @ 0x34BC) Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.1.0.00001)

but i can connect to the IPU2 with out error.

we have checked that the bellow check the bellow pointer has 1.06V and 1.8V:

+1.06V_VDD_IVA->
VDD_IVA.1
VDD_IVA.2
VDD_IVA.3
VDD_IVA.4

+1.8V_Vdda_abe_per ->
VDDA_IVA
VDDA_GPU

any one can help me? Thanks a lot.

  • i have checked  device tree has vdd_core and vdd_iva configurtion:

    				smps7_reg: smps7 {
    					/* CORE_VDD */
    					regulator-name = "smps7";
    					regulator-min-microvolt = <850000>;
    					regulator-max-microvolt = <1150000>;
    					regulator-always-on;
    					regulator-boot-on;
    				};
    
    				smps8_reg: smps8 {
    					/* VDD_IVAHD */
    					regulator-name = "smps8";
    					regulator-min-microvolt = < 850000>;
    					regulator-max-microvolt = <1250000>;
    					regulator-always-on;
    					regulator-boot-on;
    				};

    if the system is configured as early boot, is it a problem that configure the ldo in kernel??

  • Hi Wen,

    Can you let us know which version of VisionSDK is used?

    Can you share the details of this command?

    omapconf show opp

    How often do you see the issue? 

    Thanks

    RamPrasad

  • hi, RamPrasad

    environment:

    the decode version is h264vdec_02_00_17_01_production

    vision sdk 3.2

    /sys/firmware/devicetree/base/ocp/i2c@48070000/tps659038@58/tps659038_pmic/regulators/smps7 # omapconf show opp
    OMAPCONF (rev v1.73-17-g578778b built Thu Dec 28 05:15:12 IST 2017)

    HW Platform:
    Generic DRA74X (Flattened Device Tree)
    DRA75X ES1.1 GP Device (STANDARD performance (1.5GHz))
    TPS659038 ES2.2

    SW Build Details
    Build:
    release_details_get(): could not open /etc/issue.net file?!
    Version: UNKNOWN
    Kernel:
    Version: 4.4.84+
    Author: wen_hao@ubuntu
    Toolchain: gcc version 5.3.1 20160113 (Linaro GCC 5.3-2016.02)
    Type: #4 SMP PREEMPT
    Date: Tue May 26 21:34:53 CST 2020


    |-----------------------------------------------------------------------------------|
    | | Temperature | Voltage | Frequency | OPerating Point |
    |-----------------------------------------------------------------------------------|
    | VDD_CORE / VDD_CORE0 | 68C / 154F | 1.060 V | | NOM |
    | L3 | | | 266 MHz | |
    | DMM | | | 266 MHz | |
    | EMIF1 | | | 266 MHz | |
    | EMIF2 | | | 266 MHz | |
    | LP-DDR2 | | | 532 MHz | |
    | L4 | | | 266 MHz | |
    | IPU1 | | | 425 MHz | |
    | Cortex-M4 Cores | | | 212 MHz | |
    | IPU2 | | | 425 MHz | |
    | Cortex-M4 Cores | | | 212 MHz | |
    | DSS | | | 192 MHz | |
    | BB2D | | | (2128 MHz) (1) | |
    | | | | | |
    | VDD_MPU / VDD_CORE1 | 68C / 154F | 1.070 V | | NOM |
    | MPU (CPU1 ON) | | | 1000 MHz | |
    | | | | | |
    | VDD_GPU / VDD_CORE2 | 68C / 154F | 1.060 V | | NOM |
    | GPU | | | 425 MHz | |
    | | | | | |
    | VDD_DSPEVE / VDD_CORE3 | 68C / 154F | 1.060 V | | OVERDRIVE |
    | DSP1 | | | 700 MHz | |
    | DSP2 | | | 700 MHz | |
    | EVE1 | | | (0 MHz) (1) | |
    | EVE2 | | | (0 MHz) (1) | |
    | | | | | |
    | VDD_IVA / VDD_CORE4 | 68C / 154F | 1.060 V | | NOM |
    | IVA | | | 388 MHz | |
    | | | | | |
    |-----------------------------------------------------------------------------------|

  • hi, RamPrasad

    one day a time, if we restart the system when the video is accessable.

    any update?

    regards wen.

  • hi, expert:

    any ideas????

    regards, wen

  • Hi Wen,

    h264vdec_02_00_17_01_production seems old decoder version. Latest available version is 02.00.22.01.

    Can you upgrade to this version and try?

    Are you using IVAHD decLink or IPUMM?

    Your opp information shows, the OPP are not at HIGH. Is this intentional?

    Thanks

    RamPrasad

  • deal RamPrasad,

    it seems closely related to patches of "early boot late attach", see

    we are applying the patches to kernel and re-runnig the test.

    regareds, wen.

  • hi, RamPrasad

    patches sloved my issue:

    ti_components/os_tools/linux/kernel/linux-kernel-addon/earlyboot-kernel-patches
    0001-dra7xx-Kernel-Optimizations-for-early-use-case-enabl.patch

    0003-arm-dts-infoadas-Late-attach-remoteprocs.patch

    0005-arm-dts-Disable-DSS-PRCM-for-M4-display.patch
    0002-arm-mach-omap2-Remove-edma-related-nodes-from-hwmod-.patch

    0004-config_fragments-Make-remoteproc-built-in-enable-use.patch

    regards, wen.