• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 441 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

5MP problem

umair khan
Expert 1195 points

Hi All,

I have posted this question 3 times before, but could't get any reply. I request to the IPNC expert to please (at least) let me know if this is possible or I am wasting my time for nothing. 

I wanna get 5MP resolution with DMVA2IPNC-mt5 (already got 3MP). I have reduced the linux memory to 26M to give the maximum memory to cmem. But still when I load 5MP resolution, I get following error:

CMEM Error: allocHeap: Failed to mmap buffer at physical address 0x84140000

CMEM Error:     Freeing phys buffer 0x84140000

I am using following insmod:

insmod cmemk.ko phys_start=0x81a00000 phys_end=0x88000000 allowOverlap=1 phys_start_1=0x00001000 phys_end_1=0x00008000 pools_1=1x28672

I have also tried to change the memory settings in mem_mng.h and mem_mng.c, but to no avail.

I just wanna know if this is possible or not?

Regards,

Khan

  • 0
    TI__Genius 9510 points

    Umair,

    You question has been brought to the attention of our IPNC experts.  We hope to have a answer soon.

     

  • 0 in reply to Marcus Cooksey
    TI__Expert 6335 points

    3 Mpix and 5 Mpix won't be officially supported in the GA release of the DMVA. These resolutions won't appear as selection in the GUI. 

    You can try to make it work yourself but there is no guarantee from TI that it will work as we have not tested these combinations.

    A few recommendations that I can give you is that in your bootargs, make sure you have mem=26M. This means that 26 Mbytes are allocated for the Linux kernel from address 0x80000000 to 0x81A00000. Note that the phys_start of the insmod command must be greater than the end of the linux kernel space which is 0x81A00000.

    You can try to reduce further mem to 24M and set phys_start to 0x81800000 and hence increase the heap but at one point the application will fail because the kernel doesn't have enough memory for itself.

     

  • 0 in reply to Victor Cheng
    Expert 1195 points

    Victor,

     

    I am using following bootargs:

    'console=ttyS 115200n8 noinitrd rw ip=$(ipaddr) root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=26M'

    For linux memory less than 26, the application doesn't work (loads) successfully. I have also tried to change the mem_mng.h and mem_mng.c by giving maximum cache and memory size to MJPEG (0xA00000) and reducing the memory and cache size to mp4 stream (almost zero). But in this case also, I get the same error. Can I increase the heap size by some way?

    Regards,

    Khan

  • 0 in reply to umair khan
    Expert 1195 points

    One more thing to clear. The default linux memory was 48M, for which the phys_start was set to 0x8300000. Since I reduced mem to 26, I decreased phys_start by the same amount (i.e., phys_start= 0x81a00000). I am booting using TFTP and NFS:

    setenv bootcmd 'tftpboot 0x80700000 uImage; bootm 0x80700000

    setenv bootargs 'console=ttyS 115200n8 noinitrd rw ip=$(ipaddr) root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=26M'

    I don't know if this configuration, 26M are really allocated to the linux kernel. Is the phys_start address correct?

    Regards