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.

DM365 IPNC got cmem error when input is YUV sensor

Hi, We connect our YUV16 camera sensor with DM365 IPNC-MT5 with Appro V2.6 software. It is a low resolution 320x240 sensor. We modified the code a little bit to make sure it supports YUV16 progressive and booted the IPNC. It caused CMEM error. CONFIGURING AVSERVER FOR DM365 ..... queue id:65538 CMEM Error: allocHeap: Failed to mmap buffer at physical address 0x8319d000 CMEM Error: Freeing phys buffer 0x8319d000 usb [success] isapnp isapnp [success] ide ide [success] input input [success] scsi scsi [success] done. I have not changed anything about memory layout. Bo Complete log is here: Starting the hotplug events dispatcher: udevd. Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated...done. 0 CSL: Module install successful, device major num = 253 CSL: Module version 0.10.00, built on Apr 5 2011 16:54:23 I2C: Module install successful, device major num = 252 DMA: Module install successful, device major num = 251 DRV: Module install successful DRV: Module built on Apr 5 2011 16:54:26 DRV: EDMACC.QUEPRI = 00000777 DRV: SYSTEM.MSTPRI0 = 00440022 DRV: SYSTEM.MSTPRI1 = 00000244 DRV: ISP.BCR = 00000002 DRV: SYSTEM.MISC = 00000391 CMEMK module: built on Apr 5 2011 at 16:53:57 Reference Linux version 2.6.18 File /home/byu/ipnc_26/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c allocated heap buffer 0xc4000000 of size 0x5000000 CMEM Range Overlaps Kernel Physical - allowing overlap CMEM phys_start (0x1000) overlaps kernel (0x80000000 -> 0x82e00000) cmemk initialized EDMAK module: built on Apr 5 2011 at 16:53:59 Reference Linux version 2.6.18 File /home/byu/ipnc_26/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/edma/src/module/edmak.c IRQK module: built on Apr 5 2011 at 16:54:00 Reference Linux version 2.6.18 File /home/byu/ipnc_26/dvsdk_2_10_01_18/linuxutils_2_24_03/packages/ti/sdo/linuxutils/irq/src/module/irqk.c irqk initialized ++++++++++++++++++++++++++++++++++++++++ open LS-G port ++++++++++++++++++++++++++++++++++++++++ Starting mounting local filesystems: mount none on /dev/shm type tmpfs (rw,size=5M) none on /var/run type tmpfs (rw) none on /tmp type tmpfs (rw,sync) Setting up networking .... Starting hotplug subsystem: pci pci [success] usb Creat queue id:0 queue id:0 FileMngThread created Creat queue id:32769 queue id:32769 AlramThread created Share memory init success IPNC_DM365_2.6.0 (byu@ubuntu) (gcc version 4.2.0 (MontaVista 4. Creat queue id:65538 queue id:65538 queue id:32769 queue id:65538 Creat queue id:98307 queue id:98307 CPU is DM365 DEMOCFG Value : 0 Videocodecmode : 10 Videocodecres : 0 Check_device_version : DEVICE VER = 1 !! ./av_server.out DM365 NTSC APPRO2A AEWB QVGA H264 5000000 VBR AUTO MJPEG 75 MENUOFF & ApproDrvInit: 7 Creat queue id:131076 queue id:131076 AVSERVER UI: Initializing. CLK Hz, ARM Hz = 270000000 DDR Hz = 270000000 VPSS Hz = 270000000 IMCOP Hz = 270000000 [OSA_FILE ] Reading file [/mnt/nand/IMG_Paramset.bin] ... ERROR IMAGE TUNE: Paramset File is not available..... Setting DEFAULT parameter CONFIGURING AVSERVER FOR DM365 ..... queue id:65538 CMEM Error: allocHeap: Failed to mmap buffer at physical address 0x8319d000 CMEM Error: Freeing phys buffer 0x8319d000 usb [success] isapnp isapnp [success] ide ide [success] input input [success] scsi scsi [success] done. Starting portmap daemon: portmap. Starting internet superserver: inetd. io scheduler deadline registered io scheduler cfq registered insmod: /opt/ipnc/modules/i2c-emac.ko: No such file or directory sbulla: unknown partition table Installing knfsd (copyright (C) 1996 okir@monad.swb.de). loop: loaded (max 8 devices) tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky CSLIP: code copyright 1989 Regents of the University of California insmod: /opt/ipnc/modules/netconsole.ko: No such file or directory PPP generic driver version 2.4.2 PPP Deflate Compression module registered insmod: /opt/ipnc/modules/davinci_emac.ko: No such file or directory insmod: /opt/ipnc/modules/mmc_core.ko: No such file or directory insmod: /opt/ipnc/modules/mmc_block.ko: No such file or directory insmod: /opt/ipnc/modules/davinci-mmc.ko: No such file or directory insmod: /opt/ipnc/modules/usbcore.ko: No such file or directory insmod: /opt/ipnc/modules/musb_hdrc.ko: No such file or directory insmod: /opt/ipnc/modules/usbmon.ko: No such file or directory Loading iSCSI transport class v1.1-646.iscsi: registered transport (tcp) sbulla: unknown partition table mkdosfs 3.0.6 (04 Oct 2009) unable to get drive geometry, using default 255/63 /dev/sbulla has 255 heads and 63 sectors per track, logical sector size is 512, using 0xf8 media descriptor, with 1024 sectors; file system has 2 12-bit FATs and 4 sectors per cluster. FAT size is 1 sector, and provides 247 clusters. Root directory contains 512 slots. Volume ID is aea8e670, no volume label. queue id:0 TimeOut occure in boot_proc. Program exit. ApproDrvInit: 3 queue id:131076 INIT: Entering runlevel: 3 MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774) 10.100.18.64 login: root Welcome to MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774).
  • Hi, We connect our YUV16 camera sensor with DM365 IPNC-MT5 with Appro V2.6 software. It is a low resolution 320x240 sensor. We modified the code a little bit to make sure it supports YUV16 progressive and booted the IPNC. It caused CMEM error. CONFIGURING AVSERVER FOR DM365 ..... queue id:65538 CMEM Error: allocHeap: Failed to mmap buffer at physical address 0x8319d000 CMEM Error: Freeing phys buffer 0x8319d000 usb [success] isapnp isapnp [success] ide ide [success] input input [success] scsi scsi [success] done. I have not changed anything about memory layout. Bo
  • Hi, How much memory (mem=?) are you setting through bootargs? Also how much memory are you allocating through cmem? what is the "phys_start" and "phys_end" ?
  • Have you added any more memory allocation in the application? Also as Keerti mentioned, can you provide the bootargs, bootup log and the CMEM intialization script inserting CMEM module?

     

    Regards,

    Anshuman

  • We found the problem. It is our incomplete imager sensor driver. We omitted the calling of DRV_imgsCalcFrameTime() and it turns out this function actually set a few important parameters.

    We did not modifiy the memory layout from Appro v2.6.

    thanks.