TDA4VM: How to expand the video memory used by GPU on TDA4VM

Part Number: TDA4VM

Tool/software:

Hello,

   Our project is using GPU to render pictures with sdk 0900, so we would like to ask a few questions:

1、We found that when the size of the render output is 2766x1022, the output image is black,

when the size is 0.75* (2766x1022), output image is normal. does not the GPU have enough video memory? If so, how to expand this memory?

2、

I saw the gpu has 64GB physical memory in function description, can this memory be modified? Which section belongs to?

Thanks

  • Hello,

    2、

    I saw the gpu has 64GB physical memory in function description, can this memory be modified? Which section belongs to?

    This has more to do with the integration in the SoC, and how much memory the GPU can address physically. It should not be of concern for rendering a texture, which would be limited by the software driver.

    1、We found that when the size of the render output is 2766x1022, the output image is black,

    Are there any errors in the console? We can render up to certain texture sizes, but this is well within the upper limit. So the driver has run into an issue while rendering the texture, and we need to investigate what that could be.

    Do you have a sample application that can show this error?

    Regards,

    Erick

  • Hello,

    It should not be of concern for rendering a texture, which would be limited by the software driver.

    I want to know exactly how much memory the GPU uses and how to know in different SOCs?

    Are there any errors in the console?

    The following PVR information is displayed when dequeue data.

    2022-01-01T00:00:53.821885+08:00 pecu platform: [ 54.301028] hi_app[720]: app_pipeline.cpp[440]:dequeue graph INPUT graph node index 0 object index 0
    2022-01-01T00:00:53.822526+08:00 pecu platform: [ 54.301646] hi_app[720]: app_pipeline.cpp[623]:start to record app perf msg,save_flag=[1],perf_time:s=1640966453,us=821992,ms=1640966453821
    2022-01-01T00:00:53.823336+08:00 pecu platform: [ 54.302461] hi_app[720]: app_pipeline.cpp[642]:perf log name=avp_perf_msg_0
    2022-01-01T00:00:53.834275+08:00 pecu kernel: [ 54.314277] PVR_K: 218: ------------[ PVR DBG: START (High) ]------------
    2022-01-01T00:00:53.834322+08:00 pecu kernel: [ 54.314298] PVR_K: 218: OS kernel info: Linux 6.1.33-gd2eb6ca0e5 #1 SMP PREEMPT Tue Apr 16 13:16:53 UTC 2024 aarch64
    2022-01-01T00:00:53.834328+08:00 pecu kernel: [ 54.314306] PVR_K: 218: DDK info: Rogue_DDK_Linux_WS rogueddk 23.1@6404501 (release) j721e_linux
    2022-01-01T00:00:53.834331+08:00 pecu kernel: [ 54.314312] PVR_K: 218: Time now: 54314311us
    2022-01-01T00:00:53.834333+08:00 pecu kernel: [ 54.314318] PVR_K: 218: Services State: OK
    2022-01-01T00:00:53.834335+08:00 pecu kernel: [ 54.314324] PVR_K: 218: Server Errors: 0
    2022-01-01T00:00:53.834337+08:00 pecu kernel: [ 54.314332] PVR_K: 218: Connections Device ID:0(128) P720-V720-T727-hi_app.out
    2022-01-01T00:00:53.834339+08:00 pecu kernel: [ 54.314337] PVR_K: 218: ------[ Driver Info ]------
    2022-01-01T00:00:53.834341+08:00 pecu kernel: [ 54.314343] PVR_K: 218: Comparison of UM/KM components: MATCHING
    2022-01-01T00:00:53.834345+08:00 pecu kernel: [ 54.314348] PVR_K: 218: KM Arch: 64 Bit
    2022-01-01T00:00:53.834348+08:00 pecu kernel: [ 54.314353] PVR_K: 218: UM Connected Clients: 64 Bit
    2022-01-01T00:00:53.834350+08:00 pecu kernel: [ 54.314359] PVR_K: 218: UM info: 23.1 @ 6404501 (release) build options: 0x80000810
    2022-01-01T00:00:53.834353+08:00 pecu kernel: [ 54.314365] PVR_K: 218: KM info: 23.1 @ 6404501 (release) build options: 0x00000810
    2022-01-01T00:00:53.834355+08:00 pecu kernel: [ 54.314371] PVR_K: 218: Window system: lws-generic
    2022-01-01T00:00:53.834358+08:00 pecu kernel: [ 54.314377] PVR_K: 218: ------[ Server Thread Summary ]------
    2022-01-01T00:00:53.834360+08:00 pecu kernel: [ 54.314382] PVR_K: 218: pvr_defer_free : Running
    2022-01-01T00:00:53.834363+08:00 pecu kernel: [ 54.314390] PVR_K: 218: Number of deferred cleanup items: QUEUED: 00000 CONNECTION : 00000 MMU : 00000 OSMEM : 00000 PMR : 00000
    2022-01-01T00:00:53.834365+08:00 pecu kernel: [ 54.314396] PVR_K: 218: Number of deferred cleanup items dropped after retry limit reached : 0
    2022-01-01T00:00:53.834370+08:00 pecu kernel: [ 54.314402] PVR_K: 218: pvr_device_wdg : Running
    2022-01-01T00:00:53.834373+08:00 pecu kernel: [ 54.314409] PVR_K: 218: ------[ RGX Device ID:0 Start ]------
    2022-01-01T00:00:53.834375+08:00 pecu kernel: [ 54.314414] PVR_K: 218: ------[ RGX Info ]------
    2022-01-01T00:00:53.834377+08:00 pecu kernel: [ 54.314420] PVR_K: 218: Device Node (Info): 000000002a743fce (00000000a17651a4)
    2022-01-01T00:00:53.834379+08:00 pecu kernel: [ 54.314426] PVR_K: 218: DevmemHistoryRecordStats - None
    2022-01-01T00:00:53.834381+08:00 pecu kernel: [ 54.314432] PVR_K: 218: RGX BVNC: 22.104.208.318 (rogue)
    2022-01-01T00:00:53.834383+08:00 pecu kernel: [ 54.314437] PVR_K: 218: RGX Device State: Active
    2022-01-01T00:00:53.834386+08:00 pecu kernel: [ 54.314477] PVR_K: 218: RGX Power State: ON
    2022-01-01T00:00:53.834388+08:00 pecu kernel: [ 54.314486] PVR_K: 218: FW info: 23.1 @ 6404501 (release) build options: 0x80000810
    2022-01-01T00:00:53.834391+08:00 pecu kernel: [ 54.314491] PVR_K: 218: TRP: HW support - No
    2022-01-01T00:00:53.834393+08:00 pecu kernel: [ 54.314496] PVR_K: 218: WGP: HW support - No
    2022-01-01T00:00:53.834395+08:00 pecu kernel: [ 54.314505] PVR_K: 218: BIF0 - OK
    2022-01-01T00:00:53.834397+08:00 pecu kernel: [ 54.314512] PVR_K: 218: RGX FW State: OK (HWRState 0x00000001: HWR OK;)
    2022-01-01T00:00:53.834400+08:00 pecu kernel: [ 54.314519] PVR_K: 218: RGX FW Power State: RGXFWIF_POW_ON (APM enabled: 14 ok, 0 denied, 0 non-idle, 0 retry, 0 other, 14 total. Latency: 100 ms)
    2022-01-01T00:00:53.834402+08:00 pecu kernel: [ 54.314528] PVR_K: 218: RGX DVFS: 0 frequency changes. Current frequency: 750.002 MHz (sampled at 54310054145 ns). FW frequency: 100.000 MHz.
    2022-01-01T00:00:53.834405+08:00 pecu kernel: [ 54.314535] PVR_K: 218: RGX FW OS 0 - State: active; Freelists: Ok; Priority: 0; Isolation group: 0; MTS on;
    2022-01-01T00:00:53.834409+08:00 pecu kernel: [ 54.314548] PVR_K: 218: Number of HWR: GP(0/0+0), 2D(0/0+0), TA(0/0+0), 3D(1/1+0), CDM(0/0+0), FALSE(0,0,0,0,0)
    2022-01-01T00:00:53.834412+08:00 pecu kernel: [ 54.314555] PVR_K: 218: DM 0 (GP)
    2022-01-01T00:00:53.834414+08:00 pecu kernel: [ 54.314561] PVR_K: 218: DM 1 (HWRflags 0x00000000: working;)
    2022-01-01T00:00:53.834417+08:00 pecu kernel: [ 54.314567] PVR_K: 218: DM 2 (HWRflags 0x00000000: working;)
    2022-01-01T00:00:53.834419+08:00 pecu kernel: [ 54.314572] PVR_K: 218: DM 3 (HWRflags 0x00000000: working;)
    2022-01-01T00:00:53.834421+08:00 pecu kernel: [ 54.314579] PVR_K: 218: Recovery 1: PID = 720 / hi_app.out, frame = 0, HWRTData = 0xC0028A80, EventStatus = 0x00000400, Guilty Lockup
    2022-01-01T00:00:53.834424+08:00 pecu kernel: [ 54.314586] PVR_K: 218: CRTimer = 0x00000000118B, OSTimer = 54.311540647, CyclesElapsed = 653312
    2022-01-01T00:00:53.834427+08:00 pecu kernel: [ 54.314592] PVR_K: 218: PreResetTimeInCycles = 37888, HWResetTimeInCycles = 18688, FreelistReconTimeInCycles = 148224, TotalRecoveryTimeInCycles = 204800
    2022-01-01T00:00:53.834430+08:00 pecu kernel: [ 54.314598] PVR_K: 218: BIF0 - FAULT:
    2022-01-01T00:00:53.834432+08:00 pecu kernel: [ 54.314604] PVR_K: 218: * MMU status (0x0000000000005001): PC = 5, Page Size = 0 (Page Table).
    2022-01-01T00:00:53.834435+08:00 pecu kernel: [ 54.314612] PVR_K: 218: * Request (0x000006803a081000): ISP (ZLS), Writing to 0x803A081000.
    2022-01-01T00:00:53.834437+08:00 pecu kernel: [ 54.314624] PVR_K: 218: PCE for index 512 = 0x08c6d231 and is valid
    2022-01-01T00:00:53.834440+08:00 pecu kernel: [ 54.314630] PVR_K: 218: PDE for index 464 = 0x000000008dabd001 and is valid
    2022-01-01T00:00:53.834442+08:00 pecu kernel: [ 54.314636] PVR_K: 218: PT index (129) out of bounds (0)
    2022-01-01T00:00:53.834445+08:00 pecu kernel: [ 54.314641] PVR_K: 218: DM 4 (HWRflags 0x00000000: working;)
    2022-01-01T00:00:53.834447+08:00 pecu kernel: [ 54.314647] PVR_K: 218: RGX Kernel CCB WO:0x51 RO:0x51
    2022-01-01T00:00:53.834449+08:00 pecu kernel: [ 54.314652] PVR_K: 218: RGX Firmware CCB WO:0x3 RO:0x3
    2022-01-01T00:00:53.834451+08:00 pecu kernel: [ 54.314658] PVR_K: 218: RGX Kernel CCB commands executed = 81
    2022-01-01T00:00:53.834454+08:00 pecu kernel: [ 54.314664] PVR_K: 218: RGX SLR: Forced UFO updates requested = 0
    2022-01-01T00:00:53.834456+08:00 pecu kernel: [ 54.314669] PVR_K: 218: RGX Errors: WGP:0, TRP:0
    2022-01-01T00:00:53.834459+08:00 pecu kernel: [ 54.314675] PVR_K: 218: Thread0: FW IRQ count = 61
    2022-01-01T00:00:53.834461+08:00 pecu kernel: [ 54.314680] PVR_K: 218: Last sampled IRQ count in LISR = 61
    2022-01-01T00:00:53.834464+08:00 pecu kernel: [ 54.314687] PVR_K: 218: FW System config flags = 0x00020000 (Ctx switch options: Medium CSW profile;)
    2022-01-01T00:00:53.834466+08:00 pecu kernel: [ 54.314694] PVR_K: 218: FW OS config flags = 0x0000000F (Ctx switch: TDM; GEOM; 3D; CDM;)
    2022-01-01T00:00:53.834469+08:00 pecu kernel: [ 54.314700] PVR_K: 218: ------[ RGX registers ]------
    2022-01-01T00:00:53.834471+08:00 pecu kernel: [ 54.314706] PVR_K: 218: RGX Register Base Address (Linear): 0x00000000868183a0
    2022-01-01T00:00:53.834473+08:00 pecu kernel: [ 54.314711] PVR_K: 218: RGX Register Base Address (Physical): 0x4E20000000
    2022-01-01T00:00:53.834475+08:00 pecu kernel: [ 54.314718] PVR_K: 218: CORE_ID__PBVNC : 0x0016006800D0013E
    2022-01-01T00:00:53.834478+08:00 pecu kernel: [ 54.314724] PVR_K: 218: DESIGNER_REV_FIELD1 : 0x00000000
    2022-01-01T00:00:53.834480+08:00 pecu kernel: [ 54.314730] PVR_K: 218: DESIGNER_REV_FIELD2 : 0x00000000
    2022-01-01T00:00:53.834483+08:00 pecu kernel: [ 54.314736] PVR_K: 218: CHANGESET_NUMBER : 0x0000000000000000
    2022-01-01T00:00:53.834485+08:00 pecu kernel: [ 54.314742] PVR_K: 218: CLK_CTRL : 0x0AAAAA002A2AAAAA
    2022-01-01T00:00:53.834487+08:00 pecu kernel: [ 54.314748] PVR_K: 218: CLK_STATUS : 0x0000000000600000
    2022-01-01T00:00:53.834491+08:00 pecu kernel: [ 54.314754] PVR_K: 218: CLK_CTRL2 : 0x0000000000000000
    2022-01-01T00:00:53.834493+08:00 pecu kernel: [ 54.314760] PVR_K: 218: CLK_STATUS2 : 0x0000000000000000
    2022-01-01T00:00:53.834495+08:00 pecu kernel: [ 54.314766] PVR_K: 218: EVENT_STATUS : 0x00000400
    2022-01-01T00:00:53.834498+08:00 pecu kernel: [ 54.314772] PVR_K: 218: TIMER : 0x0000000000001A99
    2022-01-01T00:00:53.834501+08:00 pecu kernel: [ 54.314778] PVR_K: 218: BIF_FAULT_BANK0_MMU_STATUS : 0x00000000
    2022-01-01T00:00:53.834503+08:00 pecu kernel: [ 54.314784] PVR_K: 218: BIF_FAULT_BANK0_REQ_STATUS : 0x0000000000000000
    2022-01-01T00:00:53.834506+08:00 pecu kernel: [ 54.314789] PVR_K: 218: BIF_FAULT_BANK1_MMU_STATUS : 0x00000000
    2022-01-01T00:00:53.834508+08:00 pecu kernel: [ 54.314795] PVR_K: 218: BIF_FAULT_BANK1_REQ_STATUS : 0x0000000000000000
    2022-01-01T00:00:53.834511+08:00 pecu kernel: [ 54.314801] PVR_K: 218: BIF_MMU_STATUS : 0x00000000
    2022-01-01T00:00:53.834513+08:00 pecu kernel: [ 54.314807] PVR_K: 218: BIF_MMU_ENTRY : 0x00000000
    2022-01-01T00:00:53.834515+08:00 pecu kernel: [ 54.314812] PVR_K: 218: BIF_MMU_ENTRY_STATUS : 0x0000000000000000
    2022-01-01T00:00:53.834518+08:00 pecu kernel: [ 54.314819] PVR_K: 218: BIF_STATUS_MMU : 0x00000000
    2022-01-01T00:00:53.834521+08:00 pecu kernel: [ 54.314824] PVR_K: 218: BIF_READS_EXT_STATUS : 0x00000000
    2022-01-01T00:00:53.834523+08:00 pecu kernel: [ 54.314830] PVR_K: 218: BIF_READS_INT_STATUS : 0x00000000
    2022-01-01T00:00:53.834525+08:00 pecu kernel: [ 54.314836] PVR_K: 218: BIFPM_STATUS_MMU : 0x00000000
    2022-01-01T00:00:53.834527+08:00 pecu kernel: [ 54.314841] PVR_K: 218: BIFPM_READS_EXT_STATUS : 0x00000000
    2022-01-01T00:00:53.834530+08:00 pecu kernel: [ 54.314847] PVR_K: 218: BIFPM_READS_INT_STATUS : 0x00000000
    2022-01-01T00:00:53.834532+08:00 pecu kernel: [ 54.314853] PVR_K: 218: BIF_CAT_BASE_INDEX : 0x0000000000000505
    2022-01-01T00:00:53.834535+08:00 pecu kernel: [ 54.314859] PVR_K: 218: BIF_CAT_BASE0 : 0x0000000000000000
    2022-01-01T00:00:53.834537+08:00 pecu kernel: [ 54.314865] PVR_K: 218: BIF_CAT_BASE1 : 0x0000000000000000
    2022-01-01T00:00:53.834540+08:00 pecu kernel: [ 54.314871] PVR_K: 218: BIF_CAT_BASE2 : 0x0000000000000000
    2022-01-01T00:00:53.834542+08:00 pecu kernel: [ 54.314877] PVR_K: 218: BIF_CAT_BASE3 : 0x0000000000000000
    2022-01-01T00:00:53.834545+08:00 pecu kernel: [ 54.314882] PVR_K: 218: BIF_CAT_BASE4 : 0x0000000000000000
    2022-01-01T00:00:53.834547+08:00 pecu kernel: [ 54.314888] PVR_K: 218: BIF_CAT_BASE5 : 0x00000008C6D10000
    2022-01-01T00:00:53.834549+08:00 pecu kernel: [ 54.314894] PVR_K: 218: BIF_CAT_BASE6 : 0x0000000000000000
    2022-01-01T00:00:53.834552+08:00 pecu kernel: [ 54.314900] PVR_K: 218: BIF_CAT_BASE7 : 0x0000000000000000
    2022-01-01T00:00:53.834554+08:00 pecu kernel: [ 54.314907] PVR_K: 218: BIF_CTRL_INVAL : 0x00000000
    2022-01-01T00:00:53.834556+08:00 pecu kernel: [ 54.314912] PVR_K: 218: BIF_CTRL : 0x000000C0
    2022-01-01T00:00:53.834559+08:00 pecu kernel: [ 54.314918] PVR_K: 218: BIF_PM_CAT_BASE_VCE0 : 0x0000000000000000
    2022-01-01T00:00:53.834561+08:00 pecu kernel: [ 54.314924] PVR_K: 218: BIF_PM_CAT_BASE_TE0 : 0x0000000000000000
    2022-01-01T00:00:53.834563+08:00 pecu kernel: [ 54.314930] PVR_K: 218: BIF_PM_CAT_BASE_ALIST0 : 0x0000000000000000
    2022-01-01T00:00:53.834566+08:00 pecu kernel: [ 54.314936] PVR_K: 218: BIF_PM_CAT_BASE_VCE1 : 0x0000000000000000
    2022-01-01T00:00:53.834568+08:00 pecu kernel: [ 54.314942] PVR_K: 218: BIF_PM_CAT_BASE_TE1 : 0x0000000000000000
    2022-01-01T00:00:53.834571+08:00 pecu kernel: [ 54.314948] PVR_K: 218: BIF_PM_CAT_BASE_ALIST1 : 0x0000000000000000
    2022-01-01T00:00:53.834668+08:00 pecu kernel: [ 54.314954] PVR_K: 218: PERF_TA_PHASE : 0x00000000
    2022-01-01T00:00:53.834672+08:00 pecu kernel: [ 54.314959] PVR_K: 218: PERF_TA_CYCLE : 0x00000000
    2022-01-01T00:00:53.834675+08:00 pecu kernel: [ 54.314965] PVR_K: 218: PERF_3D_PHASE : 0x00000000
    2022-01-01T00:00:53.834677+08:00 pecu kernel: [ 54.314970] PVR_K: 218: PERF_3D_CYCLE : 0x00000000
    2022-01-01T00:00:53.834680+08:00 pecu kernel: [ 54.314976] PVR_K: 218: PERF_TA_OR_3D_CYCLE : 0x00000000
    2022-01-01T00:00:53.834683+08:00 pecu kernel: [ 54.314981] PVR_K: 218: PERF_TA_AND_3D_CYCLE : 0x00000000
    2022-01-01T00:00:53.834685+08:00 pecu kernel: [ 54.314987] PVR_K: 218: PERF_COMPUTE_PHASE : 0x00000000
    2022-01-01T00:00:53.834688+08:00 pecu kernel: [ 54.314992] PVR_K: 218: PERF_COMPUTE_CYCLE : 0x00000000
    2022-01-01T00:00:53.834691+08:00 pecu kernel: [ 54.314998] PVR_K: 218: PM_PARTIAL_RENDER_ENABLE : 0x00000000
    2022-01-01T00:00:53.834693+08:00 pecu kernel: [ 54.315003] PVR_K: 218: ISP_RENDER : 0x00000000
    2022-01-01T00:00:53.834696+08:00 pecu kernel: [ 54.315009] PVR_K: 218: TLA_STATUS : 0x0000000000000000
    2022-01-01T00:00:53.834698+08:00 pecu kernel: [ 54.315015] PVR_K: 218: MCU_FENCE : 0x0000000000000000
    2022-01-01T00:00:53.834701+08:00 pecu kernel: [ 54.315020] PVR_K: 218: VDM_CONTEXT_STORE_STATUS : 0x00000001
    2022-01-01T00:00:53.834703+08:00 pecu kernel: [ 54.315027] PVR_K: 218: VDM_CONTEXT_STORE_TASK0 : 0x0000000000000000
    2022-01-01T00:00:53.834706+08:00 pecu kernel: [ 54.315033] PVR_K: 218: VDM_CONTEXT_STORE_TASK1 : 0x0000000000000000
    2022-01-01T00:00:53.834708+08:00 pecu kernel: [ 54.315039] PVR_K: 218: VDM_CONTEXT_STORE_TASK2 : 0x0000000000000000
    2022-01-01T00:00:53.834711+08:00 pecu kernel: [ 54.315045] PVR_K: 218: VDM_CONTEXT_RESUME_TASK0 : 0x0000000000000000
    2022-01-01T00:00:53.834713+08:00 pecu kernel: [ 54.315051] PVR_K: 218: VDM_CONTEXT_RESUME_TASK1 : 0x0000000000000000
    2022-01-01T00:00:53.834715+08:00 pecu kernel: [ 54.315057] PVR_K: 218: VDM_CONTEXT_RESUME_TASK2 : 0x0000000000000000
    2022-01-01T00:00:53.834718+08:00 pecu kernel: [ 54.315063] PVR_K: 218: ISP_CTL : 0x00000000
    2022-01-01T00:00:53.834720+08:00 pecu kernel: [ 54.315068] PVR_K: 218: ISP_STATUS : 0x00000000
    2022-01-01T00:00:53.834722+08:00 pecu kernel: [ 54.315074] PVR_K: 218: MTS_INTCTX : 0x00000000
    2022-01-01T00:00:53.834725+08:00 pecu kernel: [ 54.315080] PVR_K: 218: MTS_BGCTX : 0x00000000
    2022-01-01T00:00:53.834727+08:00 pecu kernel: [ 54.315085] PVR_K: 218: MTS_BGCTX_COUNTED_SCHEDULE : 0x00000000
    2022-01-01T00:00:53.834729+08:00 pecu kernel: [ 54.315091] PVR_K: 218: MTS_SCHEDULE : 0x00000000
    2022-01-01T00:00:53.834732+08:00 pecu kernel: [ 54.315096] PVR_K: 218: MTS_GPU_INT_STATUS : 0x00000400
    2022-01-01T00:00:53.834735+08:00 pecu kernel: [ 54.315102] PVR_K: 218: CDM_CONTEXT_STORE_STATUS : 0x00000000
    2022-01-01T00:00:53.834737+08:00 pecu kernel: [ 54.315107] PVR_K: 218: CDM_CONTEXT_PDS0 : 0x0000000000000000
    2022-01-01T00:00:53.834739+08:00 pecu kernel: [ 54.315113] PVR_K: 218: CDM_CONTEXT_PDS1 : 0x0000000000000000
    2022-01-01T00:00:53.834741+08:00 pecu kernel: [ 54.315119] PVR_K: 218: CDM_TERMINATE_PDS : 0x0000000000000000
    2022-01-01T00:00:53.834744+08:00 pecu kernel: [ 54.315125] PVR_K: 218: CDM_TERMINATE_PDS1 : 0x0000000000000000
    2022-01-01T00:00:53.834746+08:00 pecu kernel: [ 54.315130] PVR_K: 218: SIDEKICK_IDLE : 0x0000007E
    2022-01-01T00:00:53.834749+08:00 pecu kernel: [ 54.315136] PVR_K: 218: SLC_IDLE : 0x000000FF
    2022-01-01T00:00:53.834751+08:00 pecu kernel: [ 54.315142] PVR_K: 218: SLC_STATUS0 : 0x00000000
    2022-01-01T00:00:53.834754+08:00 pecu kernel: [ 54.315147] PVR_K: 218: SLC_STATUS1 : 0x0000000000000000
    2022-01-01T00:00:53.834757+08:00 pecu kernel: [ 54.315154] PVR_K: 218: SLC_STATUS2 : 0x0000000000000000
    2022-01-01T00:00:53.834759+08:00 pecu kernel: [ 54.315159] PVR_K: 218: SLC_CTRL_BYPASS : 0x01000000
    2022-01-01T00:00:53.834762+08:00 pecu kernel: [ 54.315165] PVR_K: 218: SLC_CTRL_MISC : 0x0000000000200003
    2022-01-01T00:00:53.834765+08:00 pecu kernel: [ 54.315172] PVR_K: 218: MIPS_ADDR_REMAP1_CONFIG1 : 0x1FC00001
    2022-01-01T00:00:53.834767+08:00 pecu kernel: [ 54.315178] PVR_K: 218: MIPS_ADDR_REMAP1_CONFIG2 : 0x00000008C6D8D00C
    2022-01-01T00:00:53.834770+08:00 pecu kernel: [ 54.315184] PVR_K: 218: MIPS_ADDR_REMAP2_CONFIG1 : 0x1FC01001
    2022-01-01T00:00:53.834772+08:00 pecu kernel: [ 54.315189] PVR_K: 218: MIPS_ADDR_REMAP2_CONFIG2 : 0x00000008C6D8600C
    2022-01-01T00:00:53.834774+08:00 pecu kernel: [ 54.315195] PVR_K: 218: MIPS_ADDR_REMAP3_CONFIG1 : 0x1FC02001
    2022-01-01T00:00:53.834778+08:00 pecu kernel: [ 54.315200] PVR_K: 218: MIPS_ADDR_REMAP3_CONFIG2 : 0x00000008AA83C00C
    2022-01-01T00:00:53.834780+08:00 pecu kernel: [ 54.315206] PVR_K: 218: MIPS_ADDR_REMAP4_CONFIG1 : 0x1FC00000
    2022-01-01T00:00:53.834782+08:00 pecu kernel: [ 54.315212] PVR_K: 218: MIPS_ADDR_REMAP4_CONFIG2 : 0x000000000000000C
    2022-01-01T00:00:53.834785+08:00 pecu kernel: [ 54.315217] PVR_K: 218: MIPS_ADDR_REMAP5_CONFIG1 : 0x00000001
    2022-01-01T00:00:53.834788+08:00 pecu kernel: [ 54.315223] PVR_K: 218: MIPS_ADDR_REMAP5_CONFIG2 : 0x00000008C6D8D00C
    2022-01-01T00:00:53.834790+08:00 pecu kernel: [ 54.315230] PVR_K: 218: MIPS_WRAPPER_CONFIG : 0x000000000001CF80
    2022-01-01T00:00:53.834793+08:00 pecu kernel: [ 54.315235] PVR_K: 218: MIPS_EXCEPTION_STATUS : 0x00000020
    2022-01-01T00:00:53.834795+08:00 pecu kernel: [ 54.315300] PVR_K: 218: ---- [ MIPS internal state ] ----
    2022-01-01T00:00:53.834798+08:00 pecu kernel: [ 54.315305] PVR_K: 218: PC : 0xC0016126
    2022-01-01T00:00:53.834800+08:00 pecu kernel: [ 54.315311] PVR_K: 218: STATUS_REGISTER : 0x00481C05
    2022-01-01T00:00:53.834804+08:00 pecu kernel: [ 54.315316] PVR_K: 218: CAUSE_REGISTER : 0x00800008
    2022-01-01T00:00:53.834806+08:00 pecu kernel: [ 54.315321] PVR_K: 218: BAD_REGISTER : 0xC001612A
    2022-01-01T00:00:53.834808+08:00 pecu kernel: [ 54.315326] PVR_K: 218: EPC : 0xC001612A
    2022-01-01T00:00:53.834811+08:00 pecu kernel: [ 54.315332] PVR_K: 218: SP : 0xCF600FE0
    2022-01-01T00:00:53.834813+08:00 pecu kernel: [ 54.315336] PVR_K: 218: BAD_INSTRUCTION : 0x00000000
    2022-01-01T00:00:53.834816+08:00 pecu kernel: [ 54.315344] PVR_K: 218: TLB :
    2022-01-01T00:00:53.834818+08:00 pecu kernel: [ 54.315351] PVR_K: 218: 0) VA 0xCF800000 ( 64k) -> PA0 0xe20000000 DVG , PA1 0x8a9b30000 DVG
    2022-01-01T00:00:53.834821+08:00 pecu kernel: [ 54.315358] PVR_K: 218: 1) VA 0xCF000000 ( 16k) -> PA0 0x8c42f8000 DVGC, PA1 0x8c42fc000 DVGC
    2022-01-01T00:00:53.834823+08:00 pecu kernel: [ 54.315365] PVR_K: 218: 2) VA 0xCF600000 ( 4k) -> PA0 0x8c6dfc000 DV C, PA1 0x00000000 C
    2022-01-01T00:00:53.834826+08:00 pecu kernel: [ 54.315371] PVR_K: 218: 3) VA 0xC0032000 ( 4k) -> PA0 0x8c6d89000 DVGC, PA1 0x8acc3b000 DVGC
    2022-01-01T00:00:53.834829+08:00 pecu kernel: [ 54.315377] PVR_K: 218: 4) VA 0xC0022000 ( 4k) -> PA0 0x8c6d54000 DVGC, PA1 0x8c6d73000 DVGC
    2022-01-01T00:00:53.834832+08:00 pecu kernel: [ 54.315383] PVR_K: 218: 5) VA 0xF000A000 ( 4k) -> PA0 0x00000000 C, PA1 0x00000000 C
    2022-01-01T00:00:53.834834+08:00 pecu kernel: [ 54.315389] PVR_K: 218: 6) VA 0xC0016000 ( 4k) -> PA0 0x8c6e02000 DVGC, PA1 0x8aa83c000 DVGC
    2022-01-01T00:00:53.834836+08:00 pecu kernel: [ 54.315395] PVR_K: 218: 7) VA 0xC0002000 ( 4k) -> PA0 0x8aa82c000 DVGC, PA1 0x8c6e68000 DVGC
    2022-01-01T00:00:53.834839+08:00 pecu kernel: [ 54.315401] PVR_K: 218: 8) VA 0xC001C000 ( 4k) -> PA0 0x8aaaaf000 VGC, PA1 0x8c6d96000 DVG
    2022-01-01T00:00:53.834841+08:00 pecu kernel: [ 54.315408] PVR_K: 218: 9) VA 0xF0012000 ( 4k) -> PA0 0x00000000 C, PA1 0x00000000 C
    2022-01-01T00:00:53.834844+08:00 pecu kernel: [ 54.315414] PVR_K: 218: 10) VA 0xC000A000 ( 4k) -> PA0 0x8c6e89000 DVGC, PA1 0x8c6cbc000 DVGC
    2022-01-01T00:00:53.834846+08:00 pecu kernel: [ 54.315420] PVR_K: 218: 11) VA 0xC0012000 ( 4k) -> PA0 0x8acc03000 DVGC, PA1 0x8b03dc000 DVGC
    2022-01-01T00:00:53.834849+08:00 pecu kernel: [ 54.315426] PVR_K: 218: 12) VA 0xF0018000 ( 4k) -> PA0 0x00000000 C, PA1 0x00000000 C
    2022-01-01T00:00:53.834852+08:00 pecu kernel: [ 54.315432] PVR_K: 218: 13) VA 0xC0018000 ( 4k) -> PA0 0x8c6d8d000 DVGC, PA1 0x8aaaad000 DVG
    2022-01-01T00:00:53.834854+08:00 pecu kernel: [ 54.315438] PVR_K: 218: 14) VA 0xC0008000 ( 4k) -> PA0 0x8c6e14000 DVGC, PA1 0x8c6ee5000 DVGC
    2022-01-01T00:00:53.834856+08:00 pecu kernel: [ 54.315444] PVR_K: 218: 15) VA 0xF001E000 ( 4k) -> PA0 0x00000000 C, PA1 0x00000000 C
    2022-01-01T00:00:53.834859+08:00 pecu kernel: [ 54.315452] PVR_K: 218: --------------------------------
    2022-01-01T00:00:53.834861+08:00 pecu kernel: [ 54.315457] PVR_K: 218: ------[ RGX FW Trace Info ]------
    2022-01-01T00:00:53.834864+08:00 pecu kernel: [ 54.315463] PVR_K: 218: Debug log type: none
    2022-01-01T00:00:53.834867+08:00 pecu kernel: [ 54.315468] PVR_K: 218: RGX FW thread 0: Trace buffer not yet allocated
    2022-01-01T00:00:53.834870+08:00 pecu kernel: [ 54.315473] PVR_K: 218: ------[ Full CCB Status ]------
    2022-01-01T00:00:53.834872+08:00 pecu kernel: [ 54.315483] PVR_K: 218: FWCtx 0xC0028300 (TQ_3D-P720-T727-hi_app.out)
    2022-01-01T00:00:53.834875+08:00 pecu kernel: [ 54.315488] PVR_K: 218: `--<Empty>
    2022-01-01T00:00:53.834877+08:00 pecu kernel: [ 54.315495] PVR_K: 218: FWCtx 0xC0028040 (TA-P720-T727-hi_app.out)
    2022-01-01T00:00:53.834880+08:00 pecu kernel: [ 54.315500] PVR_K: 218: `--<Empty>
    2022-01-01T00:00:53.834882+08:00 pecu kernel: [ 54.315506] PVR_K: 218: FWCtx 0xC00280F0 (3D-P720-T727-hi_app.out)
    2022-01-01T00:00:53.834885+08:00 pecu kernel: [ 54.315511] PVR_K: 218: `--<Empty>
    2022-01-01T00:00:53.834888+08:00 pecu kernel: [ 54.315516] PVR_K: 218: ------[ RGX Device ID:0 End ]------
    2022-01-01T00:00:53.834890+08:00 pecu kernel: [ 54.315524] PVR_K: 218: ------[ Device ID: 128 - Phys Heaps ]------
    2022-01-01T00:00:53.834893+08:00 pecu kernel: [ 54.315541] PVR_K: 218: 0x00000000dfafff68 -> PdMs: SYSMEM, Type: UMA, Usage Flags: 0x00000004 (, GPU_LOCAL), Refs: 11, Free Size: 391196672B, Total Size: 2274828288B
    2022-01-01T00:00:53.834896+08:00 pecu kernel: [ 54.315549] PVR_K: 218: ------[ System Summary Device ID:0 ]------
    2022-01-01T00:00:53.834898+08:00 pecu kernel: [ 54.315554] PVR_K: 218: Device System Power State: ON
    2022-01-01T00:00:53.834900+08:00 pecu kernel: [ 54.315560] PVR_K: 218: MaxHWTOut: 500000us, WtTryCt: 10000, WDGTOut(on,off): (10000ms,3600000ms)
    2022-01-01T00:00:53.834903+08:00 pecu kernel: [ 54.315567] PVR_K: 218: ------[ AppHint Settings ]------
    2022-01-01T00:00:53.834905+08:00 pecu kernel: [ 54.315573] PVR_K: 218: Build Vars
    2022-01-01T00:00:53.834908+08:00 pecu kernel: [ 54.315580] PVR_K: 218: EnableTrustedDeviceAceConfig: N
    2022-01-01T00:00:53.834910+08:00 pecu kernel: [ 54.315586] PVR_K: 218: CleanupThreadPriority: 0x00000005
    2022-01-01T00:00:53.834913+08:00 pecu kernel: [ 54.315591] PVR_K: 218: WatchdogThreadPriority: 0x00000000
    2022-01-01T00:00:53.834915+08:00 pecu kernel: [ 54.315597] PVR_K: 218: HWPerfClientBufferSize: 0x000c0000
    2022-01-01T00:00:53.834918+08:00 pecu kernel: [ 54.315603] PVR_K: 218: DevmemHistoryBufSizeLog2: 0x0000000b
    2022-01-01T00:00:53.834920+08:00 pecu kernel: [ 54.315608] PVR_K: 218: DevmemHistoryMaxEntries: 0x00002710
    2022-01-01T00:00:53.834923+08:00 pecu kernel: [ 54.315613] PVR_K: 218: Module Params
    2022-01-01T00:00:53.834948+08:00 pecu kernel: [ 54.315622] PVR_K: 218: none
    2022-01-01T00:00:53.834952+08:00 pecu kernel: [ 54.315627] PVR_K: 218: Debug Info Params
    2022-01-01T00:00:53.834954+08:00 pecu kernel: [ 54.315633] PVR_K: 218: none
    2022-01-01T00:00:53.834957+08:00 pecu kernel: [ 54.315638] PVR_K: 218: Debug Info Params Device ID: 0
    2022-01-01T00:00:53.834959+08:00 pecu kernel: [ 54.315648] PVR_K: 218: none
    2022-01-01T00:00:53.834961+08:00 pecu kernel: [ 54.315654] PVR_K: 218: ------[ HTB Log state: Off ]------
    2022-01-01T00:00:53.834964+08:00 pecu kernel: [ 54.315660] PVR_K: 218: ------[ Active Sync Checkpoints ]------
    2022-01-01T00:00:53.834966+08:00 pecu kernel: [ 54.315666] PVR_K: 218: (SyncCP Counts: InUse:2 Max:2)
    2022-01-01T00:00:53.834969+08:00 pecu kernel: [ 54.315674] sw: RM_SWTimeline-hi_app.out-720 @0 cur=0
    2022-01-01T00:00:53.834972+08:00 pecu kernel: [ 54.315680] ------[ Native Fence Sync: timelines ]------
    2022-01-01T00:00:53.834975+08:00 pecu kernel: [ 54.315688] foreign_sync: @0 ctx=1 refs=1
    2022-01-01T00:00:53.834977+08:00 pecu kernel: [ 54.315694] rogue-ta3d: @0 ctx=3 refs=1
    2022-01-01T00:00:53.834979+08:00 pecu kernel: [ 54.315700] rogue-tq3d: @0 ctx=4 refs=1
    2022-01-01T00:00:53.834982+08:00 pecu kernel: [ 54.315706] QE-hi_app.out-720: @19 ctx=5 refs=1
    2022-01-01T00:00:53.834984+08:00 pecu kernel: [ 54.315712] V3-hi_app.out-720: @1 ctx=6 refs=2
    2022-01-01T00:00:53.834987+08:00 pecu kernel: [ 54.315720] @0: (++) refs=1 fwaddr=0xc0026099 enqueue=1 status=Signalled 0-es3_DoKickTA_0
    2022-01-01T00:00:53.834989+08:00 pecu kernel: [ 54.315726] P3-hi_app.out-720: @1 ctx=7 refs=2
    2022-01-01T00:00:53.834992+08:00 pecu kernel: [ 54.315733] @0: (++) refs=1 fwaddr=0xc00260a1 enqueue=1 status=Signalled 0-es3_DoKick3D_0
    2022-01-01T00:00:53.834995+08:00 pecu kernel: [ 54.315739] PVR_K: 218: ------------[ PVR DBG: END ]------------

    Do you have a sample application that can show this error?

    Sorry, the application we are using is rather complicated, there is no simple application at present.

  • hello Erick,

        Has there any progress on this issue?

        I found that I could get 2776x1022 rendered images without using the Framebuffer. Once I used the Framebuffer, I had to reduce the output size. This is the log I got from using the framebuffer.

    pvrlogdump_2201010100.txt

        Thanks.

  • Hello,

    Sorry, the application we are using is rather complicated, there is no simple application at present.

    We will need a better understanding of your application in that case. What windowing system does it use? Or is it running using the OpenVX utilities.

        I found that I could get 2776x1022 rendered images without using the Framebuffer. Once I used the Framebuffer, I had to reduce the output size. This is the log I got from using the framebuffer.

    pvrlogdump_2201010100.txt

    I see the log shows some hardware recoveries. We can get these analyzed and get back to you with a suggestion.

    Thanks,

    Erick

  • What windowing system does it use? Or is it running using the OpenVX utilities.

    We should use opengles to run on linux+rtos platform.

    We can render up to certain texture sizes

    What max sizes does gpu render?

    Thanks.

  • We should use opengles to run on linux+rtos platform.

    Ok, with Linux + RTOS, where RTOS owns the display, we don't have the usual windowing system. Instead, we use EGL Images for receiving data from other OpenVX nodes and similarly to send out data output to other nodes. These are all backed by dma-buf memory allocations, so it makes it versatile. These are also treated as textures.

    There might be an alignment issue with your texture. Could you please try making the texture 2784*1024 and let me know if you still get error?

    What max sizes does gpu render?

    The GPU hardware has a maximum capability, but there is also the maximum capability of the API. Since you will most likely be using OpenGLES, there is a way to query the maximum supported texture size:

    https://registry.khronos.org/OpenGL-Refpages/es3/html/glGet.xhtml

    Search for GL_MAX_TEXTURE_SIZE.

    Regards,

    Erick

  • hello Erick,

    Could you please try making the texture 2784*1024

    The output for this size is still black.pvrlogdump_2201010009.txt

  • Hello,

    It would be very helpful to have a unit test application of the texture allocation you are trying to make so I can try on my side. If a unit test is not possible, at least need a description of how you are creating the texture.

    Can you please share the code difference you mean here:

        I found that I could get 2776x1022 rendered images without using the Framebuffer. Once I used the Framebuffer, I had to reduce the output size. This is the log I got from using the framebuffer.

    How are you allocating the framebuffer? And what does it mean to render the images without using the Framebuffer?

    Thank you,

    Erick

  • Hello Erick,

    It would be very helpful to have a unit test application of the texture allocation you are trying to make so I can try on my side. If a unit test is not possible, at least need a description of how you are creating the texture.

        When we used the demo application ( vx_app_srv_fileio.out ) in SDK 0900 RTOS for rendering tests, we found that 1920x1080 could be output normally, but 2637x970 or 2776x1022 could not be output normally.

    output image.pptx

      Our app and demo can not render image of 2776x1022 normally.Can you test it with TI demo( vx_app_srv_fileio.out) first?

        

  • hello Erick,

        Has there any progress on this issue?

    Thank you

  • Hello,

    Not yet, we are still working on testing this ourselves.

    Regards,

    Erick

  • hello Erick,

        Has there any progress on this issue?

    Thank you

  • hello Erick,

    Can you render 2776x1022 image with the demo app on TDA4VM 0900?

    Thanks.

  • hello Erick,

    The following are the changes I made when using demo for testing on TDA4VM sdk 0900.

    When the size is 2498x919, the image can be output normally.However, when the size is 2776x1022, the output is abnormal.

    app_srv_fileio.zip

    When the same modification is used in the demo of TDA4VM SDK 0804, the 2776x1022 and 2498x919 sizes can be output normally

    Thank you.

  • Hello,

    I suspect the changes in OpenVX are affecting the use of this feature in the GPU. I have a standalone test I can use to verify the size of the output, then we can narrow down if the issue is in OpenVX rather than the GPU driver.

    Regards,

    Erick

  • Erick, please support this issue on priority, as i understand from customer on site last day, the 2776x1022 resolution is specific display/view port requirement from car OEM and they have to confirm this feature ASAP prior to get award. thanks. 

  • hello Erick,

    I suspect the changes in OpenVX are affecting the use of this feature in the GPU. I have a standalone test I can use to verify the size of the output, then we can narrow down if the issue is in OpenVX rather than the GPU driver.

      Has there any progress on this test?

    Thanks.

  • Hello,

    Sorry, we have not tested this yet. Trying to find some time to test.

    Regards,

    Erick

  • hello Erick,

      Please help us test and solve this problem as soon as possible.

    Thanks.

  • hello Erick,

    Do you have the results of this test?

    Thanks.

  • Hi qing wang,

    Any further update on this issue? 

    Regards,

    Brijesh

  • Hello,

    No, we are still waiting for your help to analyze and solve this problem.

    Do you have any further test results on this problem?

    Thanks

  • Hello, 

    I am inheriting this thread from Erick. Please give me some time to update myself on the history and action items. Thanks for your patience.

    Regards,
    Sarabesh S.

  • Unlocking this thread.