Part Number:TDA2PXEVM

Tool/software: Linux

hi all, 

  i design the follow link connect, i want dump the dispDistSrc link data through Null link, but the andriod system crash.

                                          Dup -> Gate_Null (A15) -> Null_vid1 (A15)

   DispDistSrc_Android -> Dup ->  Gate_Android -> Display_vid1

set the Null_vid1 parameter as following:

void chains_DemoDisplay_SetNullPrms(NullLink_CreateParams *pPrm)
{
    pPrm->dumpDataType = NULL_LINK_COPY_TYPE_FILE;
    strcpy((char*)pPrm->nameDataFile[0], "/data/vid1_raw_file_dump.dat");
}

crash log as following:

[   58.232770] Internal error: Oops: 2a05 [#1] PREEMPT SMP ARM
[   58.239898] Modules linked in: cmemk(O) memcache(O) pvrsrvkm(O) input_polldev ti_fpd3_serdes sd_mod usb_storage scsi_mod
[   58.250897] CPU: 0 PID: 1430 Comm: apps.out Tainted: G        W  O    4.4.117-gc33c12e #1
[   58.259109] Hardware name: Generic DRA74X (Flattened Device Tree)
[   58.265228] task: cf728e00 task.stack: cf6fe000
[   58.269784] PC is at v7_dma_inv_range+0x30/0x48 [memcache]
[   58.275296] LR is at DMA_devIoctl+0x248/0x288 [memcache]
[   58.280631] pc : [<bf02a074>]    lr : [<bf02a3cc>]    psr: 600f0013
[   58.280631] sp : cf6ffed0  ip : 00000014  fp : cf6fff04
[   58.292157] r10: 00000000  r9 : 00000004  r8 : 00000004
[   58.297402] r7 : cf636780  r6 : 9defa76c  r5 : 00000000  r4 : c120394c
[   58.303956] r3 : 0000003f  r2 : 00000040  r1 : 00000000  r0 : 00000000
[   58.310511] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[   58.317675] Control: 30c5387d  Table: 8f71a1c0  DAC: fffffffd
[   58.323444]
[   58.323444] SP: 0xcf6ffe50:
[   58.327729] fe50  00000002 dc8ba675 bf02a074 600f0013 ffffffff cf6ffeb4 00000004 00000004
[   58.336017] fe70  cf6fff04 cf6ffe80 c020d498 c0201278 00000000 00000000 00000040 0000003f
[   58.344300] fe90  c120394c 00000000 9defa76c cf636780 00000004 00000004 00000000 cf6fff04
[   58.352582] feb0  00000014 cf6ffed0 bf02a3cc bf02a074 600f0013 ffffffff c120394c bf02a390
[   58.360864] fed0  00000000 00000000 00000000 00000000 00000225 dc8ba675 d1253150 c120394c
[   58.369145] fef0  cf691798 0000fdfd cf6fff7c cf6fff08 c039a23c bf02a190 cf6fff1c dc8ba675
[   58.377426] ff10  ee36ef10 cfb31880 c120da08 0000000b cf6fff10 c02081a4 cf6fe000 dc8ba675
[   58.385706] ff30  c123d564 c123affc 9defa76c 0000da08 cf636780 00000004 cf6fff7c cf6fff58
[   58.393989]
[   58.393989] FP: 0xcf6ffe84:
[   58.398277] fe84  00000000 00000040 0000003f c120394c 00000000 9defa76c cf636780 00000004
[   58.406558] fea4  00000004 00000000 cf6fff04 00000014 cf6ffed0 bf02a3cc bf02a074 600f0013
[   58.414838] fec4  ffffffff c120394c bf02a390 00000000 00000000 00000000 00000000 00000225
[   58.423121] fee4  dc8ba675 d1253150 c120394c cf691798 0000fdfd cf6fff7c cf6fff08 c039a23c
[   58.431403] ff04  bf02a190 cf6fff1c dc8ba675 ee36ef10 cfb31880 c120da08 0000000b cf6fff10
[   58.439684] ff24  c02081a4 cf6fe000 dc8ba675 c123d564 c123affc 9defa76c 0000da08 cf636780
[   58.447967] ff44  00000004 cf6fff7c cf6fff58 c04eab28 dc8ba675 00000000 cf636781 cf636780
[   58.456249] ff64  9defa76c 0000da08 00000004 cf6fffa4 cf6fff80 c039a49c c0399e08 837be068
[   58.464532]
[   58.464532] R4: 0xc12038cc:
[   58.468818] 38cc  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   58.477102] 38ec  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   58.485384] 390c  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   58.493665] 392c  00000000 00000000 00000000 00000000 00000000 00000000 00000001 00000001
[   58.501945] 394c  dc8ba675 003fb0d6 00000000 00000009 c021aa00 c021aa20 c021b430 c021b434
[   58.510227] 396c  c0200044 c021b460 c021b46c c021b3e0 c021b3f8 00000024 c021b4b0 c021b4e0
[   58.518509] 398c  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   58.526790] 39ac  00000000 c021b364 c021b39c 90f00000 c021ad74 c021ad30 00000022 ffffffff
[   58.535073]
[   58.535073] R7: 0xcf636700:
[   58.539359] 6700  00000000 00000000 00000000 c0a027f8 00000000 00000000 00000000 00000048
[   58.547642] 6720  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   58.555923] 6740  00000000 00000000 00000000 00000000 00000000 00000000 00000000 ffff0000
[   58.564204] 6760  ffff0000 d0116448 d0116540 d0116400 d0116400 000002c0 00000001 00000000
[   58.572489] 6780  00000000 00000000 ee36ef10 cfb31880 cf691798 bf02a67c 00000000 00000003
[   58.580772] 67a0  00020002 0000001f 00000001 00000000 cf6367b0 cf6367b0 00000000 00000000
[   58.589051] 67c0  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   58.597335] 67e0  cf64b900 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   58.605618] Process apps.out (pid: 1430, stack limit = 0xcf6fe210)
[   58.611824] Stack: (0xcf6ffed0 to 0xcf700000)
[   58.616200] fec0:                                     00000000 00000000 00000000 00000000
[   58.624413] fee0: 00000225 dc8ba675 d1253150 c120394c cf691798 0000fdfd cf6fff7c cf6fff08
[   58.632627] ff00: c039a23c bf02a190 cf6fff1c dc8ba675 ee36ef10 cfb31880 c120da08 0000000b
[   58.640841] ff20: cf6fff10 c02081a4 cf6fe000 dc8ba675 c123d564 c123affc 9defa76c 0000da08
[   58.649054] ff40: cf636780 00000004 cf6fff7c cf6fff58 c04eab28 dc8ba675 00000000 cf636781
[   58.657269] ff60: cf636780 9defa76c 0000da08 00000004 cf6fffa4 cf6fff80 c039a49c c0399e08
[   58.665482] ff80: 837be068 837be068 9defa7a8 00000036 c02081a4 cf6fe000 00000000 cf6fffa8
[   58.673695] ffa0: c0207fe0 c039a434 837be068 837be068 00000004 0000da08 9defa76c 9defa764
[   58.681909] ffc0: 837be068 837be068 9defa7a8 00000036 837155d4 83717240 837829e8 837197b4
[   58.690122] ffe0: 00000000 9defa750 a70e2e3d a710e43c 600f0010 00000004 ff261011 ff250e12
[   58.698331] Backtrace:
[   58.700807] [<bf02a184>] (DMA_devIoctl [memcache]) from [<c039a23c>] (do_vfs_ioctl+0x440/0x62c)
[   58.709542]  r6:0000fdfd r5:cf691798 r4:c120394c
[   58.714209] [<c0399dfc>] (do_vfs_ioctl) from [<c039a49c>] (SyS_ioctl+0x74/0x84)
[   58.721548]  r9:00000004 r8:0000da08 r7:9defa76c r6:cf636780 r5:cf636781 r4:00000000
[   58.729374] [<c039a428>] (SyS_ioctl) from [<c0207fe0>] (ret_fast_syscall+0x0/0x40)
[   58.736974]  r9:cf6fe000 r8:c02081a4 r7:00000036 r6:9defa7a8 r5:837be068 r4:837be068
[   58.744797] Code: 1e070f3e e1110003 e1c11003 1e071f3e (ee070f36)
[   58.751016] ---[ end trace 1b9ea86ae3fcf40e ]---
[   58.755691] Kernel panic - not syncing: Fatal exception
[   58.760942] CPU1: stopping
[   58.763666] CPU: 1 PID: 146 Comm: logd.klogd Tainted: G      D W  O    4.4.117-gc33c12e #1
[   58.771965] Hardware name: Generic DRA74X (Flattened Device Tree)
[   58.778081] Backtrace:
[   58.780550] [<c020c80c>] (dump_backtrace) from [<c020ca08>] (show_stack+0x18/0x1c)
[   58.788149]  r6:60070193 r5:c1241e94 r4:00000000 r3:dc8ba675
[   58.793870] [<c020c9f0>] (show_stack) from [<c0b166b0>] (dump_stack+0x94/0xa8)
[   58.801126] [<c0b1661c>] (dump_stack) from [<c021052c>] (handle_IPI+0x320/0x33c)
[   58.808550]  r6:00000000 r5:c1085518 r4:00000005 r3:dc8ba675
[   58.814269] [<c021020c>] (handle_IPI) from [<c0201510>] (gic_handle_irq+0x78/0x7c)
[   58.821868]  r10:ab387830 r9:ab387747 r8:fa213000 r7:fa212000 r6:ed70bfb0 r5:fa21200c
[   58.829773]  r4:c12048c0 r3:00000005
[   58.833381] [<c0201498>] (gic_handle_irq) from [<c020d7e8>] (__irq_usr+0x48/0x60)
[   58.840893] Exception stack(0xed70bfb0 to 0xed70bff8)
[   58.845966] bfa0:                                     abcf3568 00000002 ab3876b0 becb9f9e
[   58.854180] bfc0: 00000041 abcf3568 00000002 00000054 7fffffff ab387747 ab387830 cccccccd
[   58.862391] bfe0: ab922000 ab38769c ab922034 abceade2 80070030 ffffffff
[   58.869030]  r8:30c5387d r7:30c5387d r6:ffffffff r5:80070030 r4:abceade2 r3:abcf3568
[   58.876852] Rebooting in 5 seconds..

could you help me find out the problem?

Tool/software: TI-RTOS

Hi,

we have a custom board with tda2px SoC.
LCD1 is working properly with minor changes. Now, I want to configure LCD3.
I found that the driver doesn't support pinmux settings for DPI2 and DPI3, so I added code to configure pinmux.
Also, I made the following changes in chains_common.c :

if(displayType == CHAINS_DISPLAY_TYPE_LCD_10_INCH)
    {
        pPrm->deviceId = DISPLAYCTRL_LINK_USE_LCD;
        pVInfo->vencId = SYSTEM_DCTRL_DSS_VENC_LCD3;
        pVInfo->outputPort = SYSTEM_DCTRL_DSS_DPI3_OUTPUT;

        if ((BSP_PLATFORM_SOC_ID_TDA2EX == Bsp_platformGetSocId()) &&
            (BSP_PLATFORM_PACKAGE_TYPE_17x17 == Bsp_platformGetPackageType()))
        {
            /* In case of TDA2EX and Package is 17 X 17, LCD is on DPI 3 */
            pVInfo->vencId = SYSTEM_DCTRL_DSS_VENC_LCD3;
            pVInfo->outputPort = SYSTEM_DCTRL_DSS_DPI3_OUTPUT;
        }

        pVInfo->vencOutputInfo.vsPolarity    =   SYSTEM_DCTRL_POLARITY_ACT_LOW;
        pVInfo->vencOutputInfo.hsPolarity    =   SYSTEM_DCTRL_POLARITY_ACT_LOW;

        /* Below are of dont care for EVM LCD */
        pVInfo->vencOutputInfo.fidPolarity      =   SYSTEM_DCTRL_POLARITY_ACT_HIGH;
        pVInfo->vencOutputInfo.actVidPolarity   =   SYSTEM_DCTRL_POLARITY_ACT_HIGH;

        pVInfo->mInfo.standard                  =   SYSTEM_STD_CUSTOM;
        pVInfo->mInfo.width                     =   displayWidth;
        pVInfo->mInfo.height                    =   displayHeight;
        pVInfo->mInfo.scanFormat                =   SYSTEM_SF_PROGRESSIVE;
        pVInfo->mInfo.fps                       =   60U;
        pVInfo->mInfo.hFrontPorch               =   48U;
        pVInfo->mInfo.vBackPorch                =   12U;
        pVInfo->mInfo.vFrontPorch               =   6U;
        pVInfo->vencDivisorInfo.divisorLCD      =   1;
    }

    /* Configure overlay params */
        ovlyPrms->vencId                        = SYSTEM_DCTRL_DSS_VENC_LCD3;

    pVInfo->mode = 0;
    pVInfo->isInputPipeConnected[0] =
                    TRUE;
    pVInfo->isInputPipeConnected[1] =
                    TRUE;
    if(Bsp_platformIsTda2xxFamilyBuild())
    {
        pVInfo->isInputPipeConnected[2] =
                    TRUE;
    }
    else
    {
        pVInfo->isInputPipeConnected[2] =
                    FALSE;
    }
    pVInfo->isInputPipeConnected[3] =
                    TRUE;
    pVInfo->writeBackEnabledFlag = FALSE;


    /* Setting other overlay parameters common to both Venc */

    ovlyPrms->deltaLinesPerPanel   = 0;
    ovlyPrms->alphaBlenderEnable   = 0;
    ovlyPrms->backGroundColor      = 0x0;
    ovlyPrms->colorKeyEnable       = 1;
    ovlyPrms->colorKeySel          = SYSTEM_DSS_DISPC_TRANS_COLOR_KEY_SRC;

    pVInfo->mode = 0;
    pVInfo->isInputPipeConnected[0] =
                    TRUE;
    pVInfo->isInputPipeConnected[1] =
                    TRUE;
    if(Bsp_platformIsTda2xxFamilyBuild())
    {
        pVInfo->isInputPipeConnected[2] =
                    TRUE;
    }
    else
    {
        pVInfo->isInputPipeConnected[2] =
                    FALSE;
    }
    pVInfo->isInputPipeConnected[3] =
                    TRUE;
    pVInfo->writeBackEnabledFlag = FALSE;


    /* Setting other overlay parameters common to both Venc */

    ovlyPrms->deltaLinesPerPanel   = 0;
    ovlyPrms->alphaBlenderEnable   = 0;
    ovlyPrms->backGroundColor      = 0x0;
    ovlyPrms->colorKeyEnable       = 1;
    ovlyPrms->colorKeySel          = SYSTEM_DSS_DISPC_TRANS_COLOR_KEY_SRC;
#ifdef ROBUST_RVC_INCLUDE
    ovlyPrms->ovlyOptimization     = SYSTEM_DSS_DISPC_OVLY_FETCH_OPTIMIZED;
#else
    ovlyPrms->ovlyOptimization     = SYSTEM_DSS_DISPC_OVLY_FETCH_ALLDATA;
#endif
    ovlyPrms->transColorKey        = DRAW2D_TRANSPARENT_COLOR;

    /* Setting overlay pipe parameters */

    pipeOvlyPrms[0].pipeLine = SYSTEM_DSS_DISPC_PIPE_VID1;
    pipeOvlyPrms[0].globalAlpha = 0xFF;
    pipeOvlyPrms[0].preMultiplyAlpha = 0;
    pipeOvlyPrms[0].zorderEnable = TRUE;
    pipeOvlyPrms[0].zorder = SYSTEM_DSS_DISPC_ZORDER0;

    pipeOvlyPrms[1].pipeLine = SYSTEM_DSS_DISPC_PIPE_VID2;
    pipeOvlyPrms[1].globalAlpha = 0xFF;
    pipeOvlyPrms[1].preMultiplyAlpha = 0;
    pipeOvlyPrms[1].zorderEnable = TRUE;
    pipeOvlyPrms[1].zorder = SYSTEM_DSS_DISPC_ZORDER1;

    if(Bsp_platformIsTda2xxFamilyBuild())
    {
        pipeOvlyPrms[2].pipeLine = SYSTEM_DSS_DISPC_PIPE_VID3;
        pipeOvlyPrms[2].globalAlpha = 0xFF;
        pipeOvlyPrms[2].preMultiplyAlpha = 0;
        pipeOvlyPrms[2].zorderEnable = TRUE;
        pipeOvlyPrms[2].zorder = SYSTEM_DSS_DISPC_ZORDER2;
    }

    pipeOvlyPrms[3].pipeLine = SYSTEM_DSS_DISPC_PIPE_GFX1;
    pipeOvlyPrms[3].globalAlpha = 0xFF;
    pipeOvlyPrms[3].preMultiplyAlpha = 0;
    pipeOvlyPrms[3].zorderEnable = TRUE;
    pipeOvlyPrms[3].zorder = SYSTEM_DSS_DISPC_ZORDER3;
    if(Bsp_platformIsTda3xxFamilyBuild())
    {
        pipeOvlyPrms[3].zorder = SYSTEM_DSS_DISPC_ZORDER2;
    }

Also, in file bsp_boardTda2pxDefault.h  VPS_DSS_DRV_INST_ID_TDA2PX_DEFAULT_LCD was defined as VPS_DSS_DISPC_OVLY_DPI1, so I changed it to VPS_DSS_DISPC_OVLY_DPI3.

And, in lcd.c changed  dpiPort = SYSTEM_DSS_DISPC_OVLY_DPI3;

Is there any problem with this configuration? What else should I change in order to enable LCD3?

Regards.

Nevena Stojanovic






 

Part Number:TDA2P-ACD

Tool/software: TI-RTOS

Dear All,

I am working on TDA2Px-EVM with Processor SDK 03.05. I have a requirement wherein my application requires a 2-digit number as an input from user over UART console. I found API's "Chains_readChar()" & "uartRead()" in Vision SDK but these API's accept only a single character from UART console. Is there any other API available in Vision SDK that I can use for taking multiple characters as input from console (for example: '77' or '34'). If no, then how can these be achieved ? Do I need to create my own API for this ?

Please suggest.

Thanks,

Abhay

Part Number:AM3359

Tool/software: TI C/C++ Compiler

I have an array "DNMSet". I want to observe member "Tick" wile program is running in debug mode. How do I do?

Thank you

Part Number:TDA2EVM5777

Tool/software: Linux

Hi,I want to display a JPG images,Which usecase do I use,I used nullsrc usecase,but I can't display the JPG image.

Tool/software: TI-RTOS

Hello,

I followed the links below to build the PDK.

http://processors.wiki.ti.com/index.php/PDK/PDK_FAQ 

But what resources do I need to download to build it.

Part Number:TCI6638K2K

Tool/software: TI-RTOS

Hi all,

I would like to know if the new PROCESSOR-SDK-RTOS-K2HK 05_02_00_10 is still compatible with syslib_3_00_9_00 for  LTE-based application or with this new Processor SDK the syslib is not needed anymore?

Thanks.

Best Regards,

Angelo

Part Number:OMAP-L138

Tool/software: Linux

Team,

I have seen that the PRU C compiler is included in the PROCESSOR-SDK-LINUX-OMAPL138 v5.02 (as it is listed in the SW manifest from Dec 2018).

1)Can you please confirm the below:
-The PRU compiler does support OMAP-L13x/C674x/AM1xxx PRU (where instruction set is slightly different compared to AM335x PRU-ICSS).
-The rpmsg/remoteproc ARM/PRU SW has been validated on OMAP-L13x/C674x/AM1xxx

2)What would be the level of difficulty to adapt the ARM/PRU SW of http://www.ti.com/tool/TIDA-01555 to make it work on an OMAP-L138 target?

Thanks in advance!

A.

Part Number:AM5728

Tool/software: Linux

Dear Sir/Madam

         I want to know the difference between DRA72 and AM57. And which is best for Linux kernel because I want run opencv. And which supports better for digital video processing

Part Number:66AK2H14

Tool/software: TI-RTOS

Hi,

I am using CCS v7.4 and SDK  ti-processor-sdk-rtos-k2hk-evm-04.03.00.05.

We have designed a customized board with 66AK2H14.We have SRIO switch (IDT_RXS2448) on board.

We are trying to communicate between FPGA board and processor board(66AK2H14).

Tool/software: TI-RTOS

Hi experts,

I am looking a simple ethernet communication example with TI-RTOS&NDK, for handle all
ethernet interfaces (4*1GE and almost 1*10GE) using a EVMK2H evaluation board
(ARM15 side) and soon on a custom board.
The first step is configure the couple of ethernet present on eval and next using RTM-BOC
and try to configure 4 1GE and the 10GE.

Installed itens:
CCS 8.2 (CCS8.2.0.00007_linux-x64.tar.gz)
GCC ARM Compiler GNU 7.2.1 (Linaro)
processor_sdk_rtos_k2hk-evm  5.01.00.11 (ti-processor-sdk-rtos-k2hk-evm-05.01.00.11-Linux-x86-Install.bin)
K2HK PDK v4.0.11
NDK 3.40.1.01
bios 6.73.00.12
xdctools 3.50.7.20_core

Best Regards,
Dario

Part Number:AM3356

Tool/software: TI-RTOS

Two projects of the same code,run on the same AM3356 hardware board.Why do DDR have different initial values after power on ?One is always 0x00 and the other is always  0xBE.

Does this have anything to do with the configuration in CCS Properties?

The PROFINET's protocol stack is compiled into lib file.But some variables are defined without an initial value. The program with DDR initial value of 0x00 runs normally.The program with DDR initial value of 0xBE runs error.

Part Number:AM5718

Hi,

1. If I configure (Hardware) USB1 in DRD mode (USB2.0) then can i use USB1 in DFU mode for loading MLO and Uboot to memory?? Is it mandatory that USB1 should be configured in Device mode??

2. If I choose sysboot[5:4] :0b10 and sysboot[3:0] : 0b0111 First Device : QSPI4 Second Device : SD Third Device: USB

then If i do not have SD card interface what should i do to avoid false triggering due to floating pins??

Part Number:TDA2PXEVM

Tool/software: TI-RTOS

Hi

I am currently using Vision SDK 3.05 . I have ported the Vision SDK 3.06 changes for capturing with CSI2_PHY2 on VSDK 3.05.I am working on captureIss PDK Demo application. I have added the decoder in capture options as shown below:

{"ISL79987 on 2 Lanes capture on PHY 1",
0U, TRUE,
FVID2_VIFM_SCH_CSI2,
FVID2_VIFW_2LANES, 4U, 0U, VPS_ISS_CAL_CSI2_YUV422_8B, FVID2_BPP_BITS16,
CAPT_APP_RUN_COUNT, 640U, 480U, (640U * 2U),
FVID2_VID_DECODER_ISL79987_DRV,
FVID2_STD_1080P_30, FVID2_DF_YUV422I_UYVY, FVID2_BPP_BITS16,
BSP_BOARD_MODE_DEFAULT, CAPT_APP_PHY_1},

4 CVBS cameras are used to  capture and  its output is decoded by the ISL79987 decoder and it sends the YUV422 data onto the 2 lanes of CSI2_PHY2.

Will the number of streams will be 4 as highlighted above.

I have two queries.

1) I am actually stuck at a function appCaptSetDrvCfg(). In this function each stream is assigned a csi2VirtualChannelNo. 

Is the number of streams is related to virtualChannel.

2) I have a query  regarding adding submodules of CAL inside the function appCaptDeriveCfg(). As seen from the code that sensors in the Surround view systems have been allocated 4 sub modules as shown below

if ((FVID2_VID_SENSOR_TIDA00262_APT_AR0140_DRV == pCfg->sensorDrvId) ||
(FVID2_VID_SENSOR_MULDES_OV1063X_DRV == pCfg->sensorDrvId) ||
(FVID2_VID_SENSOR_IMI_OV10640_DRV == pCfg->sensorDrvId))
{
appObj->issOpenPrms.subModules[1U] =
(
VPS_ISS_CAPT_CAL_SUB_PPI_ID_0 |
VPS_ISS_CAPT_CAL_SUB_CSI2_ID |
VPS_ISS_CAPT_CAL_SUB_CPORT_ID |
VPS_ISS_CAPT_CAL_SUB_DMA_WR_ID |
VPS_ISS_CAPT_CAL_SUB_PIX_EXTRACT_ID |
VPS_ISS_CAPT_CAL_SUB_DPCM_DEC_ID |
VPS_ISS_CAPT_CAL_SUB_DPCM_ENC_ID |
VPS_ISS_CAPT_CAL_SUB_PIX_PACK_ID);

appObj->issOpenPrms.subModules[2U] =
(
VPS_ISS_CAPT_CAL_SUB_PPI_ID_0 |
VPS_ISS_CAPT_CAL_SUB_CSI2_ID |
VPS_ISS_CAPT_CAL_SUB_CPORT_ID |
VPS_ISS_CAPT_CAL_SUB_DMA_WR_ID |
VPS_ISS_CAPT_CAL_SUB_PIX_EXTRACT_ID |
VPS_ISS_CAPT_CAL_SUB_DPCM_DEC_ID |
VPS_ISS_CAPT_CAL_SUB_DPCM_ENC_ID |
VPS_ISS_CAPT_CAL_SUB_PIX_PACK_ID);

appObj->issOpenPrms.subModules[3U] =
(
VPS_ISS_CAPT_CAL_SUB_PPI_ID_0 |
VPS_ISS_CAPT_CAL_SUB_CSI2_ID |
VPS_ISS_CAPT_CAL_SUB_CPORT_ID |
VPS_ISS_CAPT_CAL_SUB_DMA_WR_ID |
VPS_ISS_CAPT_CAL_SUB_PIX_EXTRACT_ID |
VPS_ISS_CAPT_CAL_SUB_DPCM_DEC_ID |
VPS_ISS_CAPT_CAL_SUB_DPCM_ENC_ID |
VPS_ISS_CAPT_CAL_SUB_PIX_PACK_ID);
}

Do I need to  do the same for the decoder?

Currently I do not have the decoder EVM to test. I am preparing the code for the same.

Regards,

Deepika

Part Number:TDA2PXEVM

Tool/software: TI-RTOS

Could you guide me with correct codec parameters to create mjpeg video for sending to networkrx->decode->display usecase?

Part Number:AM5728

Tool/software: TI-RTOS

Hi, Dear Ti exports:

I'm using GP evmAM572x to do some algorithms in my rtos project(A15_0). There are so many malloc(), free(), and calloc() in my algorithms so i created a heap using HeapBuf in my .cfg file as follows:

// Memory
var Memory = xdc.useModule('xdc.runtime.Memory');
// system heap manager.
var HeapMem = xdc.useModule('ti.sysbios.heaps.HeapMem');

/* Create a heap using HeapBuf */
var HeapBuf = xdc.useModule('ti.sysbios.heaps.HeapBuf');
var heapBufParams = new HeapBuf.Params;
heapBufParams.blockSize = 16;
heapBufParams.numBlocks = 0x01000000;//16M
heapBufParams.align = 8;
heapBufParams.sectionName = "myHeap";
Program.global.myHeap = HeapBuf.create(heapBufParams);
Program.sectMap["myHeap"] = "APP_DATA_HEAP";

Memory.defaultHeapInstance = Program.global.myHeap;

BIOS.heapSize        = 0x10000000;//16*16M=256MB
BIOS.heapSection 	= "myHeap";

but the generated .out file is too large(about 275MB), Is there any mistakes? my linker.cmd is posted bellow:

MEMORY
{
    SRAM (RWX) : org = 0x402f0000, len = 0x10000
    OCMC_RAM1 : org = 0x40300000, len = 0x80000
    OCMC_RAM2 : org = 0x40400000, len = 0x100000
    OCMC_RAM3 : org = 0x40500000, len = 0x100000
    APP_CODE (RWX) : org = 0x80100000, len = 0xf00000
    APP_DATA_IPC (RWX) : org = 0x81000000, len = 0xf600000
    VPS_FRAME_BUFFER (RWX) : org = 0x90600000, len = 0xf400000
    VPS_FIRMWARE (RWX) : org = 0xa0000000, len = 0x200000
    APP_DATA_STACK (RWX) : org = 0xa0200000, len = 0xe00000
    APP_DATA_HEAP (RWX) : org = 0xa1000000, len = 0x18000000
}

My go is to let malloc() and free() run fast in my algorithms, which will cost about 128MB in heap. My last version project used the HeapMem as the default and it runs so slowly.

So, my question is how to configure the heap to let malloc and free runs fast.

Part Number:AM5718

Tool/software: Linux

Hi all,

In one of our project, we want to implement a function which will test  DDR at location received from user.  I tried using mmap and am not able to access the DDR location. 

So can anyone suggest me regarding accessing DDR from Linux custom application.

Regards,

Noufal P

Part Number:AM3352

Hello, TI expert

If am335x boot from NAND, but NAND is not ready at the first boot time. Can am335x boot from NAND later? And if am335x can, how much time it needed when it misses the first boot time?

Best Regards

Yang

Part Number:TDA2

Hi,

Are there any limitations or guidelines to buffer transfer within a kernel, or in between different kernels? Is there any document which specifies this? I am facing issues in both inter-kernel transfers as well as within kernel buffer transfers.

Regards, 

Shruti

Part Number:TDA2

Hi,

I have created an application that should run on EVE. When I execute this application on EVE Simulator (ccs v5 Vayu simulator), it runs correctly and generates expected output. But when I try to run the same application on TDA2x board via emulator (ccs v7), it gets stuck at one point. I have some other applications, which run seamlessly through both simulator and emulator, so does not seem to be hardware issue.

What are the differences between simulator and emulator environment? Is there anything in the code that needs to be changed or configured? 

Regards,

Shruti